Oracle Hyperion DRM Basics | An Introduction & Glossary

With the increasing recognition of the potential for masterdata governance, and in particular Oracle Hyperion Data Relationship Manager (DRM), to resolve fundamental business issues we thought we would create an beginners guide to Oracle Hyperion DRM.

We make no apologies for starting at the very beginning with a glossary of the key terms you need to know.  This blog series will provide a basic set of “how to” guides to enable you to start understanding masterdata governance and particularly Oracle Hyperion DRM.

Please be aware that this glossary is not meant to be exhaustive, but will give you a good basis to understand the remainder of the blog series:

Node – A node is a record. It represents a business concept as defined by your requirements. Each node is defined by its name which must be unique within a version;

Hierarchy – A hierarchy is made up of nodes organised in a tree structure, sometimes referred to as a set of parent / child relationships;

Version – A version is a collection of hierarchies.  Each version can be live or can be a snapshot of the business master data at a certain time;

Properties – Properties are attributes that can be associated to a node, a hierarchy or a version. They can be configured to be defined by the user, read from a source system or calculated according to other properties;

Node Type – The node type is a method of controlling the properties, the validations and the glyph / icon, associated with each node;

Shared nodes – Shared nodes are nodes that are present more than once in a version. If the hierarchy allows it, a node can be present more than once in the same hierarchy. They are denoted by using a suffix, such as  “…:Shared-XXX” where XXX is a three digit number.  Shared nodes will share global properties such as the name and description, so if you change the description in one hierarchy, it will update the node in all hierarchies where it is present;

Export – An export is used to extract master data from DRM into flat files or a database. Exports can be set up to deliver the information in the format required by the target system;

Import – An import is a tool to import master data from flat files into DRM;

Blender – A blender will allow merging a version into another or two versions into a new version;

Script – A script (or automator in previous versions) is a tool to execute simple DRM actions stored as a list in a flat file. A script can be very useful to execute long series of simple actions;

Validation – A validation (or verification in previous versions) is a tool to enforce business rules. For example, a validation to enforce the fact that all nodes of the type account should have a length of 5 characters. Validations can be real time (they are executed each time a user adds or modifies a node) or in batch (a user can trigger the validation of a complete hierarchy or the validation can be executed automatically before a given export);

That is it for this week.  Next week we will give an overview of how to navigate in DRM. In the meantime if you have any questions then please do not hesitate to contact one of our team.

This entry was posted in Technical and tagged , , , , . Bookmark the permalink.

Comments are closed.