Ownership-based Hierarchy Requirements

This topic describes the hierarchy requirements for Statutory, Main, and Ownership models.

Use

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

Features

Requirements for the Statutory Model

In consolidation type models, you can combine an ownership-based 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.

The Groups hierarchy is controlled by the dimension property called PARENT_GROUP. 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 models Groups cannot be rolled up, since consolidation consists of both a complex aggregation as well as eliminations. A complex aggregation means that aggregation is also performed according to a Consolidation Method and a specific percent consolidation.

There is a split between the base-level members (the members of the Entity dimension) and the parent-level members (the members of the Group dimension). In some cases, parents in the Group dimension are actually base-level members to which entities are attached.

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.

Groups may have a corresponding Entity (as defined in the Entity property), since this member is used to store the aggregated amount of consolidated amounts. They are also used when creating reports.

Requirements for the Main Model

Required dimension-types: Account (A), Category (C), Time (T), Entity (E), Group (G) and Reporting Currency (R).

Note

You can also include the Intercompany (I) dimension in the ownership model in order to use the ownership calculation feature.

Requirements for the Ownership Model

The main model must link to a supporting Ownership-type model. It must contain the following dimension types, as no other dimension types are supported:

Dimension Type	Description
Account (A)	The Account-type dimension must contain an account (the default name is PGROUP) that 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 model parameter in the ownership model. This refers to SAP Business Planning and Consolidation, version for the Microsoft platform. 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 Ownership Manager is controlled by an ORG_ACCOUNTOWN model parameter. Note All required members, including POWN, POWNG, PCON, Method, and PGROUP, are listed in the O_Account dimension delivered with EnvironmentShell. Caution Renaming the Account dimension member in the ownership model could cause errors when executing the ownership calculations.
Category (C)	Must be the same Category dimension used in the main model.
Time (T)	Must be the same Time dimension used in the main model.
Entity (E)	Must be the same Entity dimension used in the main model.
Groups (G)	Referred to as Groups, defines the parent members used in the ownership-based 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 ownership-based hierarchy. For example: Group member ID G_E1 has the Entity property value E1. It corresponds to Entity dimension member E1. The property named STORE_ENTITY ( Y for Yes; N or empty for No) works in conjunction with the ENTITY property. It behaves as the triggering flag for aggregating the consolidated amounts to the ENTITY defined in the ENTITY property. The CURRENCY_TYPE property specifies whether the Group member is a consolidation scope (CURRENCY_TYPE=G) or the default member for that dimension ( CURRENCY_TYPE=N).
Intercompany (I)	Must be the same Intercompany dimension used in the main model.