...

The purpose of this document is to provide additional guidance as to how to set up and maintain hierarchies.  The key steps are:

1. Update the central config workbook and create a request Jira for each hierarchy (Responsibility: POD)
2. Create a hierarchy type (Responsibility: POD)
3. Create the hierarchy itself (Responsibility: POD)
4. Create CDS views that represent the hierarchy. These will be used in S/4 reporting and for extraction to Datasphere. (Responsibility: ABAP team based on Jira above)
5. Create extraction to Datasphere and include in analytic models (Responsibility: Reporting team based on Jira above)
6. Transport hierarchy to subsequent systems
   1. Hierarchy type - configuration transport (Responsibility: POD)
   2. CDS Views - workbench transport (Responsibility: ABAP Team)
   3. Hierarchy itself - download / upload  (Responsibility: POD)
   4. Datasphere developments - (Responsibility: Reporting Team)

Please find more detailed information about these steps below.

The ‘Manage Global Hierarchies’ app 

...

Before a hierarchy can be built a hierarchy type is needed. The hierarchy type defines the dimension (also known as characteristic and business entity) or combination of dimensions that  can be included in the hierarchy.  Multiple hierarchies can be built on each ‘hierarchy type’. 

Image Added

Hierarchies On Standard Hierarchy Types

...

E.g. a product hierarchy that is based on both material type and material group, or customer hierarchy based on sales org, distr channel, division

Image Added

Additional reading

...

Example of code to be used in CDS views for custom hierarchy types.  N.B. the standard documentation does NOT include the last where clause which is essential for the code to function.

Image Added

Image Added