Local and Group Account structure

Default element

LOCAL_ACCOUNT

Hierarchy structure

  • Local Account Structure: Always published. You can use different Local Chart of Accounts underneath and address as default element in Perspectives for GLDACCOUNT.
  • Group Account Structure: Published if group accounts are configured. You can use it for Enterprise_Perspective. Accounts mapped to group accounts appear as children in the group structure.

Example structure

This is an example of the Local and Group Account structure:

Group Accounts:
A1
 A2
 A3
Local Accounts:
A3
 A2 (mapped to A2)
 A1 (mapped to A2)

Based on the mapping of the base Local Accounts into the base Group Account structure (Group Account property in Business Modeling), this hierarchy in GROUP_STRUCTURE is used:

 $G_A1
  $G_A2
   G_A2
   A2
   A1
  $G_A3
   G_A3
LOCAL_ACCOUNT
 A3
  A2
  A1
N.A.

The parent element always use the $G_ prefix. The structure is similar to the Group Account configuration in Business Modeling.

The first parent (as in the example the $G_A2 element) which the local accounts are assigned to, is set up in Financial Reporting with the prefix and placed underneath the same A2 Group Account with the G_ prefix (for example G_A2) and next to it are assigned the A2 and A1 local accounts.

This ensures that group data in the Group Account structure are stored in the GLCMAIN cube and local accounts can be separated from group accounts.

Configuring local and group accounts

To configure local and group accounts, perform these actions:

  1. In Business Modeling, configure Accounts and Group Accounts business objects.

    Use the Group Account property in the business object account to set up both structures and to map base local accounts to group accounts.

  2. Publish the GLDACCOUNT dimension.

    The local account structure is always included. If group accounts are configured, the group account structure is also included. Accounts that are mapped to group accounts are displayed as children under the relevant group account.

  3. Review the account attributes.

    Each account or group account displays its attributes. Custom properties in the Account business object are included in local accounts. Custom properties in the Group Account business are not published.

Note: Parent mappings retain their weight value. The mapping relation weight is always 1.