Show TOC

Tab Page: Hierarchy SelectionLocate this document in the navigation structure

Tab Page: Hierarchy Selection


Use this tab page to select the hierarchy that you want to load and make hierarchy-specific settings for the load process.


The hierarchies for the DataSource of your InfoPackage are in the selection table.

There are three options to store a loaded hierarchy in BW.

  • Full Update

The hierarchy is stored under the selected or determined technical name in the BW. A hierarchy with the same technical name in BW is overwritten if necessary.

  • Storing the Hierarchy as a Subtree of a Target Hierarchy

The loaded hierarchy is added to a tree that already exists in BW, the target hierarchy, as a subtree. The target hierarchy node, to which the root nodes of the subtree hierarchy correspond, are called interface nodes. It is the node that refers to the same InfoObject in the target and subtree hierarchies. It also has the same technical name.

There are two options to store subtree hierarchies in BW:

  • Subtree Insert

The hierarchy is inserted in an existing hierarchy as a subtree, without nodes being deleted from the target hierarchy.

If a sub-tree is inserted for a second time, there are two sets of each sub-tree hierarchy node amongst the interface nodes. The results in termination of the load process.

  • Subtree Update

The hierarchy is inserted in an existing hierarchy as a subtree, and the old subtree is replaced by the new one if required.

If a subtree update is executed again, all target hierarchy nodes that are found amongst the interface nodes are deleted, before the new subtree is inserted amongst the interface nodes.

You can find further information about inserting and updating subtrees in theLoading Subtree Hierarchies. section.


  1. You can select whether a hierarchy is to be loaded or whether it is to be automatically activated or flagged for activation after being successfully loaded.

If the selected hierarchy is used in an aggregate, it cannot be activated directly after being loaded. It is flagged for activation and activated when a hierarchy or attribute is next changed.

An inactive hierarchy cannot be used in queries.

When using the InfoPackage in a process chain, the indicator for automatic activation or flagged activation is hidden. This is because the setting is represented by the corresponding process type Save Hierarchy in process chain maintenance.

  1. To avoid overwriting an existing BW query when you load a new hierarchy which has the same name but which comes from a different source system, indicate Rename Hierarchy After Loading and enter a new technical name. The hierarchy is stored under this new technical name and the original technical name from the source system is not used.

Loading an SAP cost center hierarchy with the same name from different source systems.

  1. When you want to load a hierarchy from an external system from a file by using BAPI , you firstly need to create a hierarchy header. This is because the file or the external system only delivers the structure of the hierarchy. You cannot select the hierarchy for the load process until the hierarchy header has been created.

See also:

Uploading Hierarchies from Flat Files

  1. When you create an InfoPackage for a hierarchy from the OLTP, the system displays hierarchies made available by the DataSource in the OLTP for selection. The system saves these entries and makes them available in the selection table again when you want to select hierarchies in this InfoPackage once more. To display the latest OLTP hierarchy entries for the DataSource, refresh the table using the Available Hierarchies In OLTP pushbutton.