Derived Hierarchies with Explicit Caps (Master Data Services)
When the levels from an explicit hierarchy are used as the top levels of a derived hierarchy, this is called a derived hierarchy with an explicit cap.
The explicit hierarchy must be based on the same entity as the entity at the top of the derived hierarchy.
The following example shows a derived hierarchy to which you can add an explicit hierarchy.
.gif "Derived hierarchy with explicit cap")
You can add the following explicit hierarchy because it is based on Subcategory, which is the top level of the derived hierarchy.
.gif "Derived hierarchy")
The explicit hierarchy rolls up members first by the derived hierarchy members, then by the explicit hierarchy consolidated members.
.gif "Derived hierarchy with explicit cap")
In the Master Data Manager user interface (UI), you create this type of hierarchy by dragging an explicit hierarchy to the top of a derived hierarchy.
.gif "Derived hierarchy with explicit cap")
In this example, the members in the explicit hierarchy are from the Subcategory entity. In the derived hierarchy, the top-level members are also from the Subcategory entity.
.gif "Derived hierarchy with explicit cap sample")
By using the explicit hierarchy at the top of a derived hierarchy, the derived hierarchy becomes ragged.
Rules
You cannot have more than one explicit hierarchy in a derived hierarchy with explicit cap.
You can use the same explicit hierarchy as a cap for multiple derived hierarchies.
You cannot assign hierarchy member permissions to derived hierarchies with explicit caps. If you assign permissions to either the explicit hierarchy or the derived hierarchy individually, the permissions affect both hierarchies.