What are Dimensions?
This manual is in pilot operation.
|
Dimensions are collections of arbitrary elements that are considered to belong to the same concept by the user. The elements of dimensions are called "members." Within a dimension, members can form a tree structure.
| Examples of Dimensions | Examples of Members |
|---|---|
Accounts |
"Sales", "Operating Profit", "Number of Employees" |
Departments |
"Sales Headquarters", "Osaka Branch", "Accounting Department" |
Dimensions are used as data perspectives in ledgers.
System Dimensions and Custom Dimensions
There are two types of dimensions: system dimensions and custom dimensions.
System Dimensions
System dimensions are mandatory for all ledgers. System dimensions include scenarios, fiscal years, relative periods, views, accounts, and changes. Each of these provides the necessary functions for managing management data either individually or in conjunction. Each system dimension is pre-labeled and named. By utilizing these dimensions, you can implement the essential functions for management-oriented data processing (financial awareness) without programming.
There are six system dimensions:
| System Dimensions (Labels) |
Descriptions |
|---|---|
Relative Periods |
Retain the "relative periods" defined in the period table along with their tree structure. |
Views |
A list of "views" defined in the period table. |
Scenarios |
A list of scenarios. |
Fiscal Years |
A list of fiscal years. Within the dimension, fiscal years are arranged in their order. |
Accounts |
Retain accounts along with their tree structure. Accounts specify the type (data type) and handling method of the data saved in the ledger. |
Changes |
Used to retain the breakdown of changes in balance-type accounts by factor for any period. |
Custom Dimensions
In addition to system dimensions, designers can create dimensions as needed. Dimensions created by designers are called "custom dimensions." Designers can decide whether or not to use individual custom dimensions for each ledger.
Custom dimensions must be assigned a unique label within the application and a name of choice.
There are two types of custom dimensions:
- " General " Dimensions
-
Provide only the basic functionality of aggregation along the member tree.
・ Virtual Member "#TOTAL" in the "General" Dimensions
(fusion_place >= 12.2) The "General" dimensions automatically register a virtual member "#TOTAL" that includes all leaf members.
By referencing "#TOTAL" in forms and Excel-Link sheets, you can easily obtain the total of all leaf members.
| Item | Configuration |
|---|---|
Label |
#TOTAL |
Name |
(JP) Total (EN) Total |
Property: Member Type |
System Reserved / RESERVED |
Property: Is Leaf |
Not a Leaf / FALSE |
Property: Is Active |
In Use / TRUE (fusion_place >= 13.0) |
"#TOTAL" is not displayed in the Dimension > Member Panel.
It can basically be specified in design objects (such as member selection in form designer) but not in management objects (such as additional keys in Process Definition).
The order of members is determined by their first appearance in the Member Tree Panel and the "Members Not Included in the Tree" panel.
For example, you can check this in the "Member Selection Screen" displayed by clicking the "Member Selection" button for the starting member in Dimension (Design) > Member List.
- " Note Item " Dimensions
-
These dimensions complement the accounts dimension to retain multiple data types for a single account. Only one note item dimension can be used in a single ledger.
Which of the above custom dimensions to use is specified by the "dimension type" selected when creating a new dimension.
Dimension Types
Dimensions have "types." Each type is granted unique functions and may also impose constraints. Each system dimension belongs to its own type. Custom dimension types are either "General Dimensions" or "Note Item Dimensions" as mentioned above.
Maintenance of Dimension Members
From the perspective of member maintenance (addition/change), dimensions are divided into two types.
(1) Relative Periods, Views, Scenarios, Fiscal Years
The members and tree structure of these four dimensions reflect the contents of other setting information. Therefore, when the original setting information is changed, the changes are automatically reflected in these dimensions.
For example, the "Relative Periods" dimension reflects the contents of the "period table." Changing the contents of the period table will also change the contents of the relative periods dimension.
Therefore, neither designers nor administrators need to add or change members or member trees for these four dimensions.
| Dimensions | Original Setting Information | Responsible for Maintenance of Original Setting Information |
|---|---|---|
Relative Periods |
Designer |
|
Views |
||
Scenarios |
||
Fiscal Years |
Administrator |
(2) Accounts, Changes, and Custom Dimensions
The members and tree structure of these dimensions are maintained by designers and administrators in a shared responsibility. For details on the division of responsibilities, please refer to the description of member types.
In the changes dimension, items representing the framework of the change table, such as "Beginning Balance," "Changes during the Period," and "Ending Balance," are pre-registered. Among these, the member tree under "Changes during the Period" is maintained by designers and administrators.
Deleting Members
Once a member is registered and the dimension is saved, the member cannot be deleted, but you can achieve an effect equivalent to deletion by combining the following methods:
-
Change the value of the member’s "Is Active/#ACTIVE" to "Not in Use/FALSE." This prohibits data entry for the member.
-
Remove the member from all member trees. This controls the member’s display on reports.
-
Change the member’s label. This allows you to reuse the label.
Changing Member Labels
For members of accounts, changes, or custom dimensions, you can change the label. However, system reserved members are excluded.
You can change member labels individually by selecting each member on the screen, but you can also change the labels of multiple members at once using the member import function (using the NEW_LABEL field).
The impact of changing labels is as follows:
-
The data in the ledger is not affected by the label change. For example, if you change the member label from A1 to A2, the ledger data originally associated with A1 will be inherited by A2.
-
In other design objects or management objects settings, if the member before the change is referenced, they will refer to the member with the old label. For example, if you change the member label A1 to A2 and then assign the old label A1 to another member, responsibilities specified by the Participant Authority that referred to member A1 will refer to the newly labeled member A1. This also applies to starting members specified in the member list or members specified in the member selection field of forms.