Hierarchically Structured Planning 

Use

Depending on particular modeling aspects, you can plan using various hierarchical structures with either a hierarchical or a non-hierarchical data model. This section explains modeling aspects, the option of planning with hierarchical structures, and the data models for manual planning.

Modeling Aspects

In terms of modeling, the following examples of hierarchical structuring are particularly frequent:

...

·        You have defined various characteristics as belonging together in a hierarchical relationship. 

·        Characteristic values of a single characteristic should be structured in a hierarchy.

However, as data in an InfoCube is stored in a flat structure, an InfoCube does not contain internal hierarchy nodes. 

According to the modeling aspects named, you have the following basic options for modeling hierarchies:

...

·        Determine hierarchical structures in InfoCube modeling

Add a characteristic of your own for each level of the hierarchy. For a two-level hierarchy, for example, insert product group and product. Using appropriate tools (such as characteristic relationships), the system ensures that only those characteristic values that are permitted by this hierarchical structure are stored in the InfoCube.

For more information on the modeling aspects of hierarchical structures, see Hierarchies and Options for Hierarchical Modeling.

·        Hierarchy definition for characteristics (BW characteristic hierarchies, “external hierarchies”)

A BW characteristic hierarchy is created for a characteristic. A hierarchy of this type cannot be seen in the InfoCube data but is stored in its own data table. When data is read from the InfoCube, the hierarchy is read too. The data is processed according to the hierarchy structure. Key figure values of hierarchy nodes are always calculated. (They are not in the InfoCube but can, where necessary, be stored redundantly in an aggregate).  In this sense, a BW characteristic hierarchy is an ’external hierarchy’.

As every postable node corresponds to a characteristic value from the hierarchy basic characteristic, key figure values for this characteristic value may also have to be stored in the InfoCube. To facilitate this, each postable node implicitly contains a leaf with the characteristic value of the node. This leaf contains the delta.

In hierarchies that do not have postable nodes, the key figure values for internal nodes only contain totals and cannot be changed.

For more information on BW characteristic hierarchies, see Hierarchy Nodes and Modeling Nodes and Leaves.

Planning with Hierarchical Structures

According to the modeling aspects named, you have the following basic options for planning using hierarchical structures:

...

·        Mapping hierarchically structured planning using appropriate planning levels

A hierarchical structure that is determined in InfoCube modeling can be visualized in a planning layout using subtotals. Use the characteristics – starting with the characteristic for the first hierarchy level – in the lead columns and use the Total as Hierarchy setting in the Layout Builder.

¡        If you want to plan just those values on the first level, only use the characteristic on the first level of the hierarchy in the planning level and the planning layout.

¡        If you also require data from lower levels you can distribute using a top-down planning function.

Note that a hierarchy that you map using characteristics in InfoCube modeling has to be balanced: Each path from the root to the leaf has to have the same number of hierarchy levels.

·        Mapping hierarchically structured planning with BW characteristic hierarchies

You can execute planning with both balanced and unbalanced BW characteristic hierarchies. As the hierarchy structure is not contained in the InfoCube data, BW characteristic hierarchies are more flexible when it comes to changing the hierarchy structure than hierarchical structures that are determined using characteristics in InfoCube modeling.  However, processing requires more effort, particularly when node values have to be changed.

Data Model for Manual Planning

For manual planning with hierarchical structures, the important question is whether it should be possible to change key figure values on hierarchy nodes (example: budgeting). If this is the case, the system has to ensure that the key figure values are determined and stored in the appropriate way in the InfoCube. The interpretation of the hierarchy structure is essential. For this reason the following cases are differentiated in the system:

Manual Planning

Data Model	What You Need to Know
Non-hierarchical data model	In this model, all hierarchy nodes only contain totals and cannot be changed. SAP differentiates the following cases: ·        You are not using hierarchies. ·        You are using hierarchical structures determined using characteristics in InfoCube modeling. ·        You are using BW characteristic hierarchies that do not contain postable nodes.
Hierarchical data model	In this model, hierarchy nodes should be ready for input. SAP differentiates the following cases: ·        If you want to use your own characteristics for the hierarchy levels, you can use BPS characteristic hierarchies. ·        If you want to structure the characteristic values of a characteristic hierarchically, use BW characteristic hierarchies that only contain postable (inner) nodes.

Hierarchical data models will now be explained further.

Hierarchical Data Model

If you are using a hierarchical data model as the basis of your manual planning, you can enter values on the nodes of the hierarchy. In order to use this functionality you have to use a hierarchy in the lead column in the planning layout.

You can select one of the following hierarchy types:

Hierarchy Types in Planning Layouts

Name	What You Need to Know
BW characteristic hierarchy with postable nodes	Hierarchy created for a hierarchy basis characteristic with (inner) nodes that correspond to a characteristic value of the hierarchy basic characteristic. BW characteristic hierarchies are stored on the database and can be used outside of planning in aggregates and reporting. The postable nodes are ready for input in manual planning.  At runtime, a leaf with the same characteristic value is always generated for a postable node. This leaf contains the not yet distributed values. (This corresponds to the dummy leaves in BPS characteristic hierarchies).
BPS characteristic hierarchy	Virtual hierarchy that is defined when you structure a planning layout and is not stored on the database. You can build BPS characteristic hierarchies completely freely using the characteristics available in a planning level. At runtime, the system generates a characteristic hierarchy from the sequence of characteristics in the lead column. Each characteristic corresponds to one level of the hierarchy. If you want to prevent a characteristic becoming a part of the hierarchy, you must either move it to the header area or to a data column of the layout, or remove the characteristic from the planning level entirely. For more information, see BPS Characteristic Hierarchies.

You cannot combine both hierarchy types within one planning layout. You can use either BW characteristic hierarchies or BPS characteristic hierarchies.

Advantages and Disadvantages of Hierarchy Types

Name	What You Need to Know
BW characteristic hierarchy with postable nodes	Advantages: ·        Both balanced and unbalanced hierarchies are possible. ·        Greater flexibility with changing hierarchies. Disadvantages: ·        As the values on the nodes of the hierarchies can only be calculated at runtime, SAP recommends that you only work with small hierarchies or subtrees (less than 1000 nodes) in manual planning. ·        The system can only ever work with a whole subtree for a hierarchy.
BPS characteristic hierarchy	Advantage: ·        No restrictions in terms of hierarchy size. Disadvantages: ·        Only balanced hierarchies are possible. ·        Greater effort involved in changing hierarchies. As the connection between the hierarchy levels is dependent exclusively on the order in the planning layout, SAP recommends that you do not change the order of the characteristics after they have been posted the first time.

Functions

You open the Hierarchy in Lead Column dialog box by clicking on  Hierarchy on the screen for determining the basic settings of the planning layout (see Determining Basic Settings).  You then make the following settings:

Choice of Data Model

·        Non-hierarchical data model

¡        Calculate Data Locally

If you want to use the local SAP functions for Microsoft Excel, activate this setting. See also, Local Functions.

·        Hierarchical data model

If you have chosen a hierarchical data model, the system makes the following settings eligible for selection or ready for input:

Hierarchy Type

·        BW hierarchy with postable nodes

·        BPS characteristic hierarchies. For more information, see BPS Characteristic Hierarchies.

Summation Logic

·        top-down

When the value of a node is changed, the change is deducted from the leaf of the higher-level node that contains the not yet distributed value.

·        bottom-up

When the value of a leaf is changed, the values of the leaves are simply summarized. The value of the leaf with the not yet distributed value does not change. However, if the value of a node with lower-level elements is changed, the system updates the change to the leaf with the not yet distributed value that belongs to the node.

Check Entries

If you switch on the validation function, the system checks if the sum of the values entered in the hierarchy branches is smaller than or equal to the value of the higher-level node. If the sum is greater than the node value, then the data cannot be posted.

Activities

You can execute the following activities on the screen for determining the basic settings of the planning layout:

...

       1.      If you want to structure your planning layout hierarchically, the following conditions have to be fulfilled:

·         In order to use BPS characteristic hierarchies, you need to include at least one characteristic in the lead column of the planning layout.

·         In order to use BW characteristic hierarchies, you can include a maximum of one characteristic in the lead column of the planning layout. A hierarchy must have been defined in SAP BW for this characteristic and you must have assigned one of these hierarchies in the planning level or package to the characteristic as a selection.

       2.      You open the Hierarchy in Lead Column dialog box by clicking on  Hierarchy. Make the required settings.

       3.      Under Additional Settings → Characteristic Combinations, decide which characteristic values are to be displayed in the lead column. For more information, see Characteristic Combinations

Further Notes

A BW characteristic hierarchy is displayed in the planning layout using the Microsoft Excel outline function. Therefore, you can also use this function when displaying and changing plan data (certain areas of the hierarchy can be expanded and collapsed individually).

The outline function is only available in the display or change mode of the executed layout. However, when processing the layout, only some sample values are displayed in order to give you an impression of the executed layout.

In order to actually display a BW characteristic hierarchy in a planning layout as a hierarchical structure, choose  Lead Column Settings in step 3 of the layout definition, and set the Hierarchy indicator. Otherwise the characteristic values contained in the hierarchy are output in the layout as a single-level list.

Entering plan data in a planning layout for BPS characteristic hierarchies is only slightly different from entering plan data in a planning layout without hierarchies. For more information, see Entering Plan Data.