1. Integrating Oracle Data Relationship Management Suite with Enterprise Performance Management
  2. Using Data Relationship Management with Oracle Hyperion Planning and EPM Cloud Planning
  3. Configuring Planning Metadata in Data Relationship Management
  4. Dimension to Hierarchy Organization

Dimension to Hierarchy Organization

Dimensions may map to hierarchies in Oracle Data Relationship Management on a one to one or many to one basis.

A common example of one to one is the currency dimension. A common example of many to one is the entity dimension where the Top Nodes of the entity dimension are separate views of the entity by different business needs, for example Legal, Managerial, and Geographic. Splitting these branches into individual hierarchies in Data Relationship Management reduces shared nodes, is more aligned to business usage, and allows for better validations (such as all leaf nodes in Managerial must be in Legal).

The Planning integration supports both of these models. The imports are initially setup for the one to one model but can be modified by using the nodes to ignore functionality to split the incoming dimension into multiple hierarchies. The exports use hierarchy groups and in doing so support both the one to one model as well as the one to many model without changes.

Splitting the Dimension into Multiple Hierarchies in Data Relationship Management

To split the Planning dimension into multiple hierarchies the following changes to the import profile need to be made.

  1. The Dimension Name needs to be added to the “Skip Nodes during Import” Section of the Filter portion of the Import Profile. For example add “Entity” to the “Skip Nodes During Import” Node list to split the entity dimension.

  2. If the Dimension has members at level 2 that have no children then the “Create Base Orphan Hierarchy” option on the Style portion of the import profile needs to be selected. The following information needs to be added:

    • Name: Hierarchy Name to contain the single dimension nodes; for example Entity-Misc

    • Description: Hierarchy Name to contain the singleton dimension nodes; for example Entity Miscellaneous Branches

    • Top Node Name: Name of the top node for the hierarchy; for example Entity-Misc

    • Top Node Description: Description of the top node for the hierarchy; for example Entity Miscellaneous Branches