Continuing with our beginner’s guide to Oracle Hyperion Database Relationship Management (DRM), we can now start looking at the core of masterdata management: nodes and hierarchies.
We recently created and saved our sample version. In our home page, under “Browse”, we can now select the sample version and have a look at the hierarchy section. As our version is new, there are no hierarchies.
To create the first hierarchy., simply click on the “Hierarchies” menu, select “New” followed by “Hierarchy…”.
Hierarchy groups are folders which are used to organize your hierarchies. They are particularly useful when your design is more complex. You can either use the small menu or there is a short cut to create a new hierarchy on the right of the “Hierarchies” menu.
You will need to give your hierarchy a name, a description and a top node that will also need a description. The top node can be a new node as it is in this case, or a node that already exists. You can also allocate it to an existing group.
Once your hierarchy is created it will appear in the list of hierarchies.
By double clicking on a hierarchy, you can open it and start navigating around it.
Our hierarchy only contains the top node for the moment. On the right hand of the screen, you can see the properties associated to the highlighted node. There are also some other tabs such as “Relationships”, “Clipboard” and “Shortcuts” on the right and we will investigate these later.
Oracle Hyperion DRM prompts us for the following details:
- Is the new node a leaf? A leaf node is a node that cannot have any children. It is the lowest node of the hierarchy;
- The node name;
- The node description;
- If the node already exists, “Insert” the Node. Node names are unique therefore if you enter the name of a node that already exists in another hierarchy, Oracle Hyperion DRM will return an error message. If you select this property, it will insert the node as a shared node; and
- “Add As child” or “Sibling” – A child is a node in the level below the node you have selected. A sibling is a node on the same level in the hierarchy. In this case, we selected the top node, so the sibling option is disabled as every node in a hierarchy must be a descendant of the top node.
After adding some nodes here is how a hierarchy looks:
The glyphs (icons) above each represent different things:
represents a leaf node, which cannot have children; and
represents limb nodes, which can have children. As we will see at a later date, these glyphs can be configured.
Next week we will start looking at properties. As always do get in contact if you would like to explore this and Oracle Hyperion DRM’s abilities in more detail.