Member Trees
This manual is in pilot operation.
|
What are Member Trees?
Within a dimension, members can form member trees. It is possible to include several trees within a single dimension (with certain restrictions as detailed in "Who Establishes Member Trees"). For instance, within a Department Dimension, there could be trees categorized by geographic region or by business area.
A single member may belong to multiple trees. For example, "Osaka Branch Corporate Sales Department" might fall under "Osaka Branch" in the region-based tree and under "Corporate Business Division" in the business area-based tree.
There’s no limit on the depth of a member tree. Furthermore, the number of levels need not be uniform within a single member tree.
Who Establishes Member Trees?
Deciding the number of trees within a dimension is a task for designers. The number of root members (the highest-level members) created by designers determines the number of member trees. However, there are exceptions:
-
Member trees for dimensions like Scenario, Relative Periods, Views, and Fiscal Year are automatically created. Designers have no capability to add to these.
-
For the Change Dimension, root members are predefined by system specifications. Therefore, designers cannot add new member trees.
-
Designers may leave decisions about tree structures to administrators. If a dimension’s design is completed without any root members, administrators can then register any root members at their discretion.
Applications of Member Trees
Member trees serve two primary functions:
-
Aggregative calculations
-
Grouping members
(2) Grouping of Members
In dimensions whose members have a "Data type" property — namely the Accounts, Note Items, and General dimensions — you can create a parent member simply to group several members together rather than to aggregate their values. In that case, set the parent member’s data type to "None." No aggregation will then be performed for that parent member.
Rules for Member Trees
Setting up member trees requires adherence to certain rules. Trees that do not comply with these rules cannot be established.
-
There must be no loops in the parent-child relationships of members.
-
Leaf members cannot have child members (A "Leaf member" refers to members for which the "Is Leaf" property is set to "False").
-
In principle, the same member cannot be placed in more than one location under a single member. However, in dimensions whose members have a "Data type" property — namely the Accounts, Note Items, and General dimensions — if a member’s data type is "None," the same member can be placed in multiple locations beneath it (because members with the data type "None" are used solely for grouping purposes).
-
The combinations of parent and child member types must satisfy certain criteria. Specifically:
-
If the parent and child member types differ, their combination must respect the hierarchy of member types, which is: System Reserved > Template > User-Defined.
-
If multiple child members are directly under the same parent member, all those child members must be of the same member type.
-
(This ensures that within a member tree, system reserved members, template members, and user-defined members are organized in orderly layers from top to bottom, clarifying the demarcation of responsibilities between designers and administrators.)
In dimensions whose members have a "Data type" property — namely the Accounts, Note Item, and General dimensions — the following constraints apply in addition to those described above:
-
As a rule, a parent member and its child members must have the same data type. As an exception, if the parent member’s data type is "None," its child members may have any data type.