Hierarchy Management

You manage dimension hierarchies by adding new hierarchies, deleting existing hierarchies, and maintaining the hierarchy structure for a particular dimension.

You manage dimension hierarchies based on your business needs. For example, if your company opens a new office, the hierarchy of your Entity dimension should be updated to include this new office.

Features

A dimension can be defined to have a hierarchy or not. To enable a hierarchy for your dimension, use BW modeling tools. A hierarchy you maintain in the Business Planning and Consolidation HTML5 web client can also be verified and maintained in BW modeling tools.

Adding a New Hierarchy
You can add a new hierarchy to a dimension within an environment in the Administration screen. In the Modeling section, select Dimensions, choose a dimension, select Edit Hierarchy, then select Add.
Maintaining a Hierarchy Structure
By selecting a hierarchy name in the hierarchy list, you can maintain the hierarchy structure.

You can add new nodes to a hierarchy by selecting a parent node and selecting Add, then choosing dimension members from either the current dimension or external dimensions.

You can add text nodes or internal nodes, and you can sort and filter by member ID or property by selecting each column header of the grid.
Note
The External Dimension option is by default not displayed in this page if you did not choose an external dimension for the current hierarchy. To define external dimensions, enter Business Warehouse (BW) transaction RSA1, choose InfoObjects in Modeling, and enter the Hierarchy page of the current dimension. Then you can add external dimensions in the External Characteristics of Hierarchy view.
Time and Version Dependent Hierarchies

Time and version dependent hierarchies are supported in the Business Planning and Consolidation Web client. To define a time and version dependent hierarchy, use Business Warehouse (BW) transaction RSA1 and go to the Hierarchy tab of the related InfoObject to make the corresponding settings. After that, you can define hierarchies of different versions based on a different date range, as well as hierarchies in a different time range based on different versions in the hierarchy view of the dimension. The detailed settings are as follows:

  • Entire Hierarchy is Time Dependent

    All existing Time ranges display at the top of the right pane. You can select different time ranges to toggle.

    To create a new time range, select Create hierarchy date range from the time range drop-down. The hierarchy structure of the currently displayed time range will be used as the default hierarchy for the new time range.

  • Time-dependent Hierarchy Structure

    The time range of each hierarchy node displays for the node ID/Description when you move your mouse over the node. All newly added nodes have the default time range 1000.01.01-1999.12.31. To edit the time range, choose the pen icon.

  • Version-dependent Hierarchy

    All existing versions display at the top of the right pane. You can select different versions to toggle.

    To create a new version, select Create hierarchy version from the version drop-down.

Using Local Hierarchies

You can use local hierarchies by either creating them from scratch or by making a local copy of a hierarchy that has had its master data loaded into the system. To make a local copy after selecting a dimension and viewing its global hierarchies, choose a hierarchy and select Copy. Since local hierarchy does not support time or version dependent hierarchies, you need to enter a key date for time-dependent hierarchies or specify a time range if the entire hierarchy is time-dependent, which is the date on which or the date range during which you want to take a snapshot of the hierarchy to add locally. If the global hierarchy from which you copy a local hierarchy is version-dependent as well, you also need to select a version.. Then you can assign a new ID and description if desired and make other changes in the local hierarchy by adding, deleting, or moving items in it, if necessary. Note that you can have only internal nodes and text nodes in local hierarchies. External nodes are automatically converted to text nodes when the hierarchy is copied from global to local. After that, you can save and process your changes.

Reverse Sign for Nodes

To enable the reverse sign for nodes, use Business Warehouse (BW) transaction RSD1. Reversed displays for each node ID/Description when you move your mouse over the node. To change the sign, choose the pen icon.

Processing Required

You must process all changes made to a hierarchy before the hierarchy can be used in reporting and planning.