Comparison of modeling in different hierarchical structures
Characteristic Hierarchy | Hierarchical Structures in InfoCube Dimensions or DataStore Objects | Hierarchical Structures in Attributes Characteristics |
---|---|---|
As Posted view is not possible. Different views (such as version, key date) of the data are 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, because it is modeled in the master data. |
Changeable |
Not changeable, unless you reload the InfoProvider. |
Changeable (with master data changes or with the addition of attributes). |
Drill-down path is defined by the structure. |
Drill-down path is not defined by the structure. Levels can therefore be skipped. |
Drill-down path is not defined by the structure. Levels can therefore be skipped. |
Duplicate leaves are always displayed. |
Duplicate leaves are only possible in As Posted view. |
Duplicate leaves are not possible. |
Balanced and unbalanced hierarchies are possible. |
Hierarchy structures have to be balanced. |
Hierarchy structures have to be balanced. |
The following sections deal exclusively with the maintenance of characteristic hierarchies.
The following graphic shows a sales hierarchy as a typical example of a characteristic hierarchy in the BEx Analyzer.
The following graphic shows a hierarchical structure modeled in the dimensions of an InfoCube in the BEx Analyzer.
Using the Display as Hierarchy (Universal Display Hierarchy) function, you can also display the modeling as a tree in the query, like the characteristic hierarchy shown above (seeWorking with Hierarchies).