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. Managing Planning Dimension Members in Data Relationship Management
  4. Managing Planning Dimension Membership

Managing Planning Dimension Membership

Membership properties are used to flag nodes in Oracle Data Relationship Management that should be managed and exported as Planning dimension members. The membership property can be used to include only a subset of nodes in a Data Relationship Management hierarchy as members of a Planning dimension.

For hierarchies to be included in a Planning dimension, the top-level node or nodes must be updated to define the Planning membership (HP.Membership). By default, this resolves to Not Applicable. All nodes that have a membership of Not Applicable are filtered from the exports that produce the outline load utility files to feed the Planning systems.

The Membership property has the following allowed values:

  • Not Applicable

  • Dimension

  • Parent Member

  • Base Member

For hierarchies that have a top node that is the same as the dimension, the top node membership property should be set to Dimension. For hierarchies where the top node or nodes are dimension members, set the membership to Parent Member.

In addition, if the Sort Order is desired then the Hierarchy Sort Order Property for the Hierarchy needs to be configured to point to the Sort Order property.

It is best practice to make a copy of the predefined import profiles and use the copy to modify so that you have easy access back to the original if needed. If the original is lost or deleted, it can be reloaded from the application template.

To assign Planning dimension membership:

  1. Open a hierarchy that has been assigned to a Planning dimension.

  2. Select a node in the hierarchy, and from Category, select Planning.

  3. Select the Planning Membership property.

  4. Do one of the following:

    • To mark the node and its descendants as members of the Planning dimension, set the Membership property value to Parent Member.

    • To mark a node with children as a bottom-level member of the Planning dimension, set the Membership property value to Base Member.

    Note:

    Setting node membership to Base Member causes the nodes below it to become Not Applicable. This allows you to filter out the bottom section of a branch from a Planning application.

Automatic Membership to Planning Dimensions

If you want all imported or newly created hierarchies to automatically have membership to a Planning dimension, then the following formula for HP.Membership can be used.

If(Equals(String,PropValue(HP.Dimension),),Not Applicable,If(Equals(Integer,PropValue(Core.Level), 1),If(Equals(String,PropValue(HP.Dimension),PropValue(Core.PrimaryName_ MDM)),Dimension,Parent Member),If(Or(Equals(String,PropValue(HP.ParentMembership),Dimension),E quals(String,PropValue(HP.ParentMembership),Parent Member)),If(PropValue(Core.Leaf),Base Member,Parent Member),Not Applicable)))