What are Dimensions?
This manual is in pilot operation.
|
Dimensions are collections of elements considered by the user to belong to the same concept. Elements of dimensions are called "Members". Within a dimension, members may form a tree structure.
| Examples of Dimensions | Examples of Members |
|---|---|
Accounts |
"Sales", "Operating Income", "Number of Employees" |
Departments |
"Sales Division", "Osaka Branch", "Accounting Department" |
Dimensions are used as slices of data 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. They include scenarios, fiscal years, relative periods, views, accounts, and changes. These provide the functions necessary for managing management accounting data, either individually or in combination. System dimensions are pre-labeled and named. These dimensions allow you to implement essential functionalities for management accounting data processing (Financial Awareness) without programming.
The six system dimensions are as follows:
| System Dimension (Label below) |
Content |
|---|---|
Relative Periods |
Holds "Relative Periods" as defined in the Period Table, along with their tree structure. |
Views |
A list of "Views" as defined in the Period Table. |
Scenarios |
A list of Scenarios. |
Fiscal Years |
A list of Fiscal Years. Fiscal years are arranged in order within the dimension. |
Accounts |
Holds Accounts along with their tree structure. Accounts specify the type of data (data type) and handling method for data stored in ledgers. |
Changes |
Used to hold the breakdown of increases and decreases for a given period for accounts specified as "Balance value" data type. |
Custom Dimensions
In addition to system dimensions, designers can freely 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 given a unique label and an arbitrary name within the application.
There are two types of custom dimensions:
- "General" Dimension
-
Provides only the basic functionality of aggregation along a member tree.
(fusion_place >= 12.2) For "General" dimensions, a virtual member "#TOTAL", which encompasses all leaf members as children, is automatically registered.
"#TOTAL" allows you to easily obtain the total of all leaf members by referring to it in forms or Excel-Link sheets.
| Item | Setting |
|---|---|
Label |
#TOTAL |
Name |
(JP) Total (EN) Total |
Property: Member Type |
System Reserved / RESERVED |
Property: Is Leaf |
Not a Leaf / FALSE |
Property: Active |
Inactive / FALSE |
"#TOTAL" does not appear in the Dimension > Member panel.
It can generally be specified in design objects (e.g., member selection in Form Designer) but not in management objects (e.g., additional keys in business process definitions).
The order of members follows their first appearance in the Member Tree Panel and the "Members not in trees" panel.
For example, it can be checked in the "Member Selection Screen" that appears when you click the "Select Member" button for the starting member in Dimension (Design) > Member List.
- "Note Item" Dimension
-
Complements the account dimension by allowing multiple data types of data to be held for a single account. Only one note item dimension can be used in a ledger.
Whether a custom dimension is one of the above is specified by the "Dimension Type" selected when creating a new dimension.
Dimension Types
Dimensions have "types". Each type has unique functionalities and may impose constraints. System dimensions belong to individual types. The type of a custom dimension is either "General Dimension" or "Note Item Dimension" as described above.
Maintenance of Dimension Members
From the perspective of member maintenance (adding or changing), dimensions can be divided into two types.
(1) Relative Periods, Views, Scenarios, Fiscal Years
The members and tree structures of these four dimensions reflect the content of other setting information. Therefore, changes to the underlying setting information are automatically reflected in these dimensions.
For example, the "Relative Periods" dimension reflects the content of the "Period Table". Changing the Period Table also changes the content of the Relative Periods dimension.
Therefore, for these four dimensions, neither designers nor administrators need to add or change members or member trees.
| Dimension | Underlying Setting Information | Maintenance Responsibility of Underlying Setting Information |
|---|---|---|
Relative Periods |
Designer |
|
Views |
||
Scenarios |
||
Fiscal Years |
Administrator |
(2) Accounts, Changes, and Custom Dimensions
The members and tree structures of these dimensions are maintained by both designers and administrators. For the division of responsibilities between the two, see Member Types.
In the Changes dimension, accounts representing the framework of the changes table, such as "Beginning Balance", "Change in Current Period", and "Ending Balance", are pre-registered. Among these, the lower member tree of "Change in Current Period" is maintained by both designers and administrators.
Deleting Members
Once a member is registered and the dimension is saved, that member cannot be deleted, but the following methods can be combined to achieve an effect equivalent to deletion:
-
Set the member’s "Active/#ACTIVE" value to "Inactive/FALSE." This will prohibit data entry for that member.
-
Remove the member from all Member Trees. This controls the display of that member in reports, making it invisible.
-
Change the label of the member. This allows the label to be reused.
Changing Member Labels
Labels of members in accounts, changes, or custom dimensions can be changed, except for System Reserved Members.
Changing member labels can be done individually by selecting each member on the screen, or in bulk using the Member Import Function (using the NEW_LABEL field).
The impacts of changing labels are as follows:
-
Ledger data is not affected by label changes. For example, if a member’s label is changed from A1 to A2, the ledger data originally associated with A1 will be carried over to A2.
-
In other design objects and management objects settings, if the old member was referenced before the change, they will refer to the member with the old member label. For example, if the label of member A1 is changed to A2, and then the old label A1 is assigned to another member, if member A1 was specified as a responsibility scope key for a business responsibility unit, it will be interpreted as referring to the member newly assigned the label A1. The same applies to the starting member in the Member List and members specified in the form’s member specification field.