Once the modification work is completed, the data of the Shared Workspace Edition can be published. By "publishing", the content of the Public Edition is replaced with the content of the Shared Workspace Edition at that moment. The publishing process can be executed based on scenarios (it is also possible to publish multiple scenarios together).

If you wish to redo the modification work, you can also clear the data of the Shared Workspace Edition. "Clearing" completely replaces the content of the Shared Workspace Edition with the content of the Public Edition at that moment, which is the exact opposite of "publishing".

Similar to labels, Ledger edition keys starting with a sharp sign are reserved and cannot be assigned by administrators. Note that the Public Edition and Shared Workspace Edition are pre-assigned Ledger edition keys "PUBLIC" and "WORKSPACE". Though these do not start with a sharp sign, they are still reserved and cannot be freely assigned by administrators.

Ledger edition keys are used to specify the target Ledger edition when accessing ledger data via [Browser] or [Excel-Link].

Unreserved Ledger edition keys can be deleted or changed. If a Ledger edition key is deleted, that Ledger edition becomes inaccessible from [Browser] or [Excel-Link] (it becomes accessible again if a key is reassigned).

If a Ledger edition key is deleted from one Ledger edition and assigned to another, from then on, specifying that Ledger edition key in [Browser] or [Excel-Link] will access the newly assigned Ledger edition.

The uses of "Other Editions" can vary, but here are two examples:

Data of Ledger editions that serve as the source for other editions becomes read-only (data writing is not allowed). This restriction is in place because updating the data of such editions could unintentionally affect all editions derived from it (since derived editions only hold differences from the source, updating the source’s data would appear to users as if the derived editions' data were also updated). If you wish to update the data of a Ledger edition that serves as a source for others, create a new edition derived from that edition and update its data.

Just like the Shared Workspace Edition, the contents of "Other Editions" can be published (reflected in the Public Edition). The ability to specify target scenarios for publication is the same. When publishing an edition other than the Shared Workspace Edition, the content of the Shared Workspace Edition is cleared, and after publication, the content of the Public Edition (i.e., the published edition’s content) becomes the same, so please be cautious.

Repeatedly deriving editions can gradually increase the size of the edition tree and also increase the number of unnecessary editions. In such cases, by deleting the Ledger edition keys of unnecessary editions and compressing the series of editions, it is possible to compress the edition series (tree). Editions meeting the following two conditions can be deleted through series compression:

The data of editions deleted through compression is integrated into the data of editions directly derived from them if such derivative editions existed at the time of compression (if no derivative editions exist, they are deleted).

"Submission Packages" generated by the business process management feature are treated as pseudo Ledger editions, and a Ledger edition key is assigned. By specifying the cell holding this Ledger edition key during the link area setting of [Excel-Link], it is possible to inquire the content of the Submission Package.

The Ledger edition key for Submission Packages is in the format of prefix “#P” followed by the business process definition label, fiscal year label, relative period label, Participant label, Submission Package definition label, and submission sequence number, connected by periods.

Example: #P.BUDGETING.FY2018.H1.A.SALES.2

The Ledger Edition for Submission Packages can only be inquired through [Excel-Link]. It cannot be inquired through fusion_place [Browser] (it does not appear in the selection options for Ledger Editions).

The Ledger Edition for Submission Packages is read-only. Furthermore, only the Participant that submitted the package and the Participant that accepted or can accept the package can refer to the data of the Submission Package’s Ledger Edition. Others follow the normal ledger access control.

The Ledger Edition for Submission Packages includes only the submitted data (※).

Even if data can be derived through dimension aggregation calculations based on the submitted data, if it itself is not included in the submitted data, it will not be included in the Ledger Edition for Submission Packages. For example, if the account dimension member tree registers various expense accounts as children of the total expenses, the total expenses can be derived from the amounts of each expense account. However, if the Submission Package form includes only the individual expense accounts and not the total expenses, then the total expenses will not be included in the Ledger Edition for Submission Packages. Note that rows and columns set to be hidden in the form settings are considered visible for the purposes of this determination. Therefore, that data is included in the Submission Package.

※ The submitted data refers to the data for each key displayed on the Submission Package form, excluding the relative period and display format keys, combined with all relative periods and all display formats. For example, if the submitted data includes "Sales for June", it also includes "Cumulative Sales up to May" of the same fiscal year.

The Ledger Edition Key for the Hidden Ledger Edition is in the format of prefix "#S" followed by the scenario label, connected by a period.
Example: If the actual scenario (label "ACTUAL") is excluded from Ledger Edition management
#S.ACTUAL

Hidden Ledger Editions can be used (selected or specified) in the following screens/functions that operate on the Ledger Edition itself regardless of its data content.

Since there is no need to perform operations such as changing Ledger Edition Keys, creating derivative editions, or publishing for Hidden Ledger Editions, they are not displayed in the following screens.

Also, in the following screens/functions that access the data content of Ledger Editions, they cannot be used (selected or specified).