Company-Internal Hierarchies 
Product Hierarchies
You can extract a company-internal product hierarchy from SAP ECC to the hierarchy of InfoObject Material (0MATERIAL) with standard extractors and DataSources. As InfoObject 0MATERIAL is an attribute of the InfoObject /DDF/GPID and /DDF/GPID is an attribute of the InfoObject /DDF/PRODUCT, you can implement the hierarchy of InfoObject 0MATERIAL for reporting on global products and internal products. This is done, for example, in sales analysis using CompositeProvider /DSR/CP10. As a prerequisite, 0MATERIAL must be assigned to the global object in data harmonization. Additionally, you can extract the company-internal product hierarchy to the hierarchy of Global Product (/DDF/GPID) and Product (/DDF/PRODREF) with the transformations provided by SAP Demand Signal Management. These transformations evaluate the relationship between of Material, Global Product, Internal Product, and Product. The resulting hierarchies ofr Global Product and Product look exactly like the hierarchy of the InfoObject Material, the only difference being that the material nodes are replaced by global products or products.
Example
You can extract a material hierarchy (table T179) with three levels using DataSource 0MATERIAL_LPRH_HIER to extract the BW hierarchy PRDHA of InfoObject Material (0MATERIAL). The external characteristics Product Hierarchy Level 1 (0PRODH1), Product Hierarchy Level 2 (0PRODH2), and Product Hierarchy Level 3 (0PRODH3) provide the three levels. If you add these characteristics to the InfoObjects Global Product (/DDF/GPID) and Product (/DDF/PRODREF) as external characteristics, you can build a hierarchy equivalent to the BW hierarchy PRDHA with products as leaves (hierarchy of /DDF/PRODREF) or global products as leaves (hierarchy of /DDF/GPID).
Account Hierarchies
You can extract account hierarchies from SAP ECC to the hierarchy of InfoObject Customer (0CUSTOMER) with standard extractors and DataSources. If you assign the InfoObject Customer to the Global Location (/DDF/GLID) in data harmonization, you can use the account hierarchy for reporting. The double join in the CompositeProvider is based on the following relation: InfoObject 0CUSTOMER is an attribute of /DDF/GLID, and /DDF/GLID is an attribute of /DDF/LOCATION.
Example
You can extract the customer hierarchy of the class system (class type 011) from SAP ECC using DataSource 0CUSTOMER_LKLS_HIER. Additionally, you can extract this account hierarchy to the hierarchy of Global Location (/DDF/GLID) and Location (/DDF/LOCREF) with the transformations provided by SAP Demand Signal Management. These transformations evaluate the relationship between Customer, Global Location, Internal Location, and Location. If the InfoObject Internal Location (/DDF/LOCATION) provides a delivery location (distribution center), the relationship is taken into account in the transformation and the delivery locations are assigned to the hierarchy. The locations (stores) are then assigned to the delivery locations as child nodes.