Show TOC

Function documentationDynamic Hierarchy Requirements Locate this document in the navigation structure

 

To set up a general application for use with dynamic hierarchies, you need a main application that stores the entity information and contains links to a supporting Ownership-type application where the data is actually stored. For information about creating an Ownership application, see Consolidation Framework Setup.

Features

Requirements for the statutory application

In statutory applications, you can combine a dynamic hierarchy with a static, upper-level portion of the hierarchy representing Groups. You can use this portion of the hierarchy to generate statutory reporting or to identify a series of groups for consolidation.

Instead of being controlled by the OWNERSHIP application, the Groups hierarchy is controlled by the dimension property Org_ParentProperty. This property has no default value; the presence of the property enables the Groups hierarchy. The property is populated with hierarchy information (similar to the PARENTHn field), but does not generate a true OLAP hierarchy of members in the Group dimension. This is because in statutory applications the Group dimension exists in both the main and ownership applications.

There is a split between the base-level entities (the members of the Entity dimension) and the parent-level entities (the members of the Group dimension). In this case, parents in the Group dimension are actually base-level members. These members are used by the Business Rules engine which writes the contribution of each Entity to each Group (using the Entity/Group intersection). The consolidation of each upper-level Group begins with the base-level entities. In these cases, the Groups do not need to have a corresponding Entity (as defined in the Entity property), because it would be an unused member in the Entity dimension.

Requirements for the main application

Required dimension-types: Account (A), Category (C), Time (T), Entity (E), and Currency (R) (referred to as Groups). The system supports any additional dimensions in the application. You must define the ORG_OWNERSHIPCUBE application parameter value.

Requirements for the ownership application

The main application must link to a supporting Ownership-type application. It must contain the following dimension types (no other dimension types are supported):

Dimension Type

Description

Account (A)

The Account-type dimension must contain an account (the default name is PGROUP) which has a nonzero value for the valid intersections of the Entity and Group dimensions. You must enter the name of this member in the Org_AccountOwn application parameter in the ownership application.

It may also contain other accounts that can be used to store additional information relating to an Entity/Group intersection for a given Category and Time. The set of accounts to display in the Dynamic Hierarchy Editor is controlled by an ORG_ACCOUNTOWN application parameter.

Note Note

All required members, including POWN, POWNG, PCON, Method, and PGROUP, are listed in the Ownaccount dimension delivered with ApShell.

End of the note.

Category (C)

Must be the same Category dimension used in the main application.

Time (T)

Must be the same Time dimension used in the main application.

Entity (E)

Must be the same Entity dimension used in the main application.

Currency (R)

Referred to as Groups, defines the parent members used in the dynamic hierarchy. This dimension must have a property named Entity. The property values define the link between the Group dimension member and its corresponding Entity dimension member. These members are the parents that are used in the dynamic hierarchy. For example: Group member ID G_E1 has the Entity property value E1. It corresponds to Entity dimension member E1.

You must define the following application parameters:

  • ORG_ACCOUNTLIST - These are consolidation accounts used in the dynamic hierarchy. The following table lists the default values for each version of Planning and Consolidation:

    Microsoft Version

    NetWeaver Version

    Description

    METHOD

    Method

    Represents the consolidation method account

    POWN

    POWNDIR

    Represents the percent ownership account by direct share

    PCON

    POWNGROUP

    Represents the percent consolidation account

  • ORG_ACCOUNTOWN - The default is PGROUP. This value represents the name of the account that contains the hierarchy information.

  • ORG_INTCO - If an intercompany dimension is included in the ownership application, the ORG_INTCO application parameter must be defined. The intercompany dimension is not required for the definition of a dynamic hierarchy. It may, however, be used for other purposes in statutory applications. If using this dimension for other purposes, you must use a dummy member whose default ID is I_NONE. The name of this member (I_NONE) must be specified in the ORG_INTCO application parameter.

    Note Note

    The NONE group member GNONE should be set in the Group dimension.

    End of the note.

Example

To illustrate the Groups example table above, assume the Entity dimension of the Ownership-type application contains the members E1, E2, and E3. The Currency (Group) dimension contains member G_E1, with the Entity property value E1. You designate Entity member E1 as the parent of Entity member E3 (for the Category and Time member values Actual and Jan.09) by making the following entry in the Ownership application:

Category

Time

Entity

Group

Account

Value

ACTUAL

2009.JAN

E3

G_E1

PGROUP

1

Activities

From Administration, log on to the main application, and define the ORG_OWNERSHIPCUBE application parameter value. The value is the name of the supporting ownership application. (In ApShell, this value is Ownership.)