Options for Hierarchical Modeling (SAP Library

Options for Hierarchical Modeling

Comparison of modeling hierarchical structures

Characteristic hierarchy	Hierarchical structures in the InfoCube dimensions or in an ODS object	Hierarchical structures in the attributes for a characteristic
As-posted view is not possible Different views (such as version, key date) on the data possible	As-posted view is possible	As-posted view is not possible Different data views are not possible. Exception: The view for the key date is possible if the characteristic or respective attributes are time-dependent.
Cross-InfoProvider	Only valid for an InfoProvider	Cross-InfoProvider, since modeled in the master data
Changeable	Not changeable, except if you reload the InfoProvider	Changeable (with master data changes or with the addition of attributes)
Drill-down path defined by the structure	Drill-down path not defined by the structure. Levels can therefore be skipped.	Drill-down path not defined by the structure. Levels can therefore be skipped.
Duplicate leaves always displayed	Duplicate leaves only possible in As-posted view	Duplicate leaves not possible
Balanced and unbalanced hierarchies are possible	Hierarchy structures have to be balanced	Hierarchy structures have to be balanced

The subject of the following sections is exclusively the maintenance of characteristic hierarchies.

Example

The following graphic shows a sales hierarchy as a typical example of a characteristic hierarchy in the BEx Analyzer.

This graphic is explained in the accompanying text

The following graphic shows a hierarchical structure modeled in the dimensions of an InfoCube in the BEx Analyzer.

This graphic is explained in the accompanying text

Using the function Display as Hierarchy (Universal Display Hierarchy), you can also display the modeling like the characteristic hierarchy shown above as a tree in the query (see Structure link Working with Hierarchies).