Hierarchies (Master Data Services)
In Master Data Services, a hierarchy is a tree structure that you can use to:
Group similar members for organizational purposes.
Consolidate and summarize members for reporting and analysis.
What Hierarchies Contain
Each hierarchy contains members from one or more entities. When a member is added, changed, or deleted, all hierarchies are updated. This ensures that the data is accurate in all hierarchies. Hierarchies also help ensure that each member is counted once and only once.
If you want to create a grouping of a subset of members, consider using a collection. For more information, see Collections (Master Data Services).
Kinds of Hierarchies
You can create multiple hierarchies to view and organize your members in different ways. You can create:
Ragged hierarchies from a single entity, which are called explicit hierarchies. For more information, see Explicit Hierarchies (Master Data Services).
Level-based hierarchies from multiple entities, based on the existing relationships between entities and their attributes, which are called derived hierarchies. For more information, see Derived Hierarchies (Master Data Services).
All members in a hierarchy must be within the same model.
Hierarchies Are Not Taxonomies
A hierarchy is different from a taxonomy. A taxonomy organizes members by multiple attributes at the same time, while a hierarchy organizes members by one attribute at a time. A taxonomy can include the same member multiple times, while a hierarchy includes a member only once.
For example, the same bike can be included in a taxonomy twice: once because it's red, and once because it's a size 38. In a hierarchy, the bike is included only once, so you must decide whether to show it in relation to its color or its size.
In the following example, product members are grouped by subcategory members.
Enable an entity for explicit hierarchies and collections.
Create a explicit hierarchy.
Create a derived hierarchy.
Hide or delete levels in an existing derived hierarchy.