Create hierarchies to show how code values are related to other code values. First, define the hierarchy model, and then add code values to the hierarchy to define relationships between code values.
For example, you might create a location hierarchy. First, you define the hierarchy model. You define the Region code list as the top-level code list. Then you create a parent-child relationship from the Region code list to the Enterprise Country Codes code list. Based on this hierarchy model, in the hierarchy, you create a hierarchy relationship from the North America code value to the United States code value. You create a hierarchy relationship from the North America code value to the Canada code value.
You can extend a hierarchy model that contains data by adding nodes and relationships to the nodes of the hierarchy model. You can add multiple child nodes and a recursive relationship to any node. After you extend and save the hierarchy model, you cannot delete the nodes or relationships.
You can use the details panel to view the details of code values in hierarchies. The panel displays the summary, history, and relationships for a code value.
You can view the history of code values in hierarchies. Use the historical data to track the detailed changes made to a hierarchy.
You can view the code values that existed in a hierarchy at a point in time in the past. For example, you can view code values that existed in the Locations hierarchy on April 2023.
Note: Reference 360 displays the code values that are available in the database at a point in time in the past.
You can also export the code values in a hierarchy to a CSV file.
If you no longer need a hierarchy, you can delete the hierarchy.
Note: You must be assigned the Planner role to work with hierarchies. For more information, see Users, groups, and roles .