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. Optimal Configurations

Optimal Configurations

For more information see:

Multiple Aliases

The Oracle Hyperion Planning application template is configured with a single Alias property for each type. In some cases, multiple aliases may be necessary to maintain dimension member descriptions in different languages.

To support multiple aliases:

  1. Create a new custom global node Alias property for each additional description to be supported.

  2. Do one of the following:

    • Create a new custom MemberAliasLength validation for each additional custom Alias property.

    • Modify the existing MemberAliasLength validation to check the additional alias as well as the default alias.

  3. Assign the custom Alias properties and MemberAliasLength validations to the node types for the Oracle Hyperion Planning node types.

  4. Assign any new custom MemberAliasLength validations to versions and hierarchies where required.

  5. Modify Oracle Hyperion Planning type exports for dimensions where custom Aliases are required.

    1. Add new custom Alias properties to the columns of the export.

    2. Add the labels for the new Alias properties to the header record of the export.

    3. Assign new custom Alias validations.

Multiple UDAs

Multiple UDAs for a node in Oracle Data Relationship Management are supported by entering them in a comma-delimited format in the appropriate UDA property.

Attribute Dimensions

Oracle Hyperion Planning offers the ability to use custom Attribute dimensions. The Attribute dimension type is supported by the Oracle Hyperion Planning application template, however, some additional configuration is necessary in order to account for the user-defined aspects for supporting them.

To configure Attribute dimensions in Data Relationship Management:

  1. Create a new custom global node property for each Attribute dimension that will manage the association of a base dimension member to a custom attribute dimension member.

  2. Create a new custom version property of data type ListGroup to use for association of base dimension members to members of the Attribute dimension. This property will identify the valid hierarchies from which an attribute member can be selected. Go to the Version and set up the list of allowed hierarchies for the attribute dimension.

  3. Create a new custom formula validation for each Attribute dimension to enforce dimension associations between it and base dimension members that use the Attribute dimension. Compare the selected values in the custom version ListGroup property for the Attribute dimension to the value of the Core.References property for the Attribute dimension member being referenced.

    For example, the Global node attribute property is Custom.Attribute and the version-level attribute hierarchies property is Custom.AttributeHiers. Invalid attribute member validation formula:

    Or(IsBlank(PropValue(Custom.Attribute)),GreaterThanOrEqual(ArrayCoun t(Intersection(NodePropValue(PropValue(Custom.Attribute),Custom.Attr ibuteHiers,NodePropValue(PropValue(Custom.Attribute),Core.References),[comma]),[comma]),1))

  4. Assign the custom global node Attribute properties and validations to the appropriate node types for the dimensions to be supported.

  5. Assign any new custom Attribute validations to versions and hierarchies where required.

  6. Modify Oracle Hyperion Planning exports for the attribute dimension and for the base dimension mapped to it.

    1. Create the export profile for the new attribute dimension. Copy the predefined attribute dimension for a start and customize as needed for the Oracle Hyperion Planning configuration (Aliases, Plan Types and so on).

    2. Assign new custom Attribute validations to the base dimension export.

    3. Add custom Attribute properties as exports columns to the base dimension export and update the export header to match.

  7. Add the new Attribute Dimensions to the Attribute Hierarchy Group and set the Hierarchy Dimension Property to Attribute.

For more information on customizing the new attribute dimensions, see Defining and Configuring Planning Dimensions and Configuring Planning Dimension Types.

Generic and Custom Dimensions

Oracle Hyperion Planning supports additional Generic dimensions. Many clients use them for dimensions like Product. The Oracle Hyperion Planning application template supports the Generic Dimensions.

To configure a new generic dimensions in Data Relationship Management:

  1. Create the new hierarchies for the Generic dimension.

  2. Create the export profile for the new generic dimension. Copy the predefined generic dimension for a start and customize as needed for the Oracle Hyperion Planning configuration (Aliases, Plan Types, and so on).

  3. Add the new Generic hierarchies to the Generic Hierarchy Group and set the Hierarchy Dimension Property to Generic.

For more information on customizing the new attribute dimensions, see Defining and Configuring Planning Dimensions and Configuring Planning Dimension Types.

Supporting Multiple Planning Applications

Supporting Production and Testing Instances of Oracle Hyperion Planning

There are no additional configuration steps required in Data Relationship Management to support testing and production Oracle Hyperion Planning applications. The same exports can be used to generate the outline load utility files that can be loaded into a test application and then later a production application.

Supporting Multiple Different Oracle Hyperion Planning Applications

There are two methods that can be used to support multiple different Oracle Hyperion Planning applications.

  1. Separate Data Relationship Management Versions

    • Each Oracle Hyperion Planning instance has its dimensional data in a different version.

    • Additional properties are not required.

    • Hierarchies cannot be shared across versions so each would be independent of the other.

    • Exports may need to be made specific to each Oracle Hyperion Planning instance if there are differences in Oracle Hyperion Planning configurations that require a different column set (Plan Types, Aliases, Weeks Distribution setup, Attribute & Generic Dimensions).

  2. Custom Data Relationship Management Properties and Exports

    • Each additional instance of an Oracle Hyperion Planning application requires separate custom Dimension and Dimension Type properties if the application instances have different dimensions.

    • Each additional instance of an application requires separate custom Membership, Member, and Parent properties if different dimension members are required for each application instance.

    • Each additional instance of an application requires separate Oracle Hyperion Planning properties if these need to be different by the application instance (For example UDA, Data Storage and so on).

    • Each additional instance of an application requires separate custom Oracle Hyperion Planning dimension exports if there are differences in Oracle Hyperion Planning configurations that require a different column set (Plan Types, Aliases, Weeks Distribution setup, Attribute, and Generic Dimensions) or if there are different Planning properties being used.

Plan Types

Initial Predefined Plan Types

The Planning application integration is designed with the initial three default Plan Types defined in the properties and in the export and import profiles:

  • Plan1

  • Plan2

  • Plan3

Additional Predefined Plan Types

The following additional Plan Types are predefined for ease of use and have the properties needed to support them but are not included in the default import and export profiles:

  • Capex

  • Hcp

  • Project

  • WorkForce

Plan Type Properties

For each Plan Type (Plan1, Plan2, Plan3, Capex, Hcp, Project, and Workforce) the following properties are defined:

  • Aggregation – Plan Specific Aggregation

    Local Node Defined String Property with Allowed Values (Default: Add)

  • Aggregation Code – Plan Specific Aggregation Code

    Local Node Lookup String Property using Aggregation as the lookup

  • Data Storage – Plan Specific Data Storage

    Local Node Formula Derived String Property, Overridable– Returns the non plan-specific Data Storage (HP.DataStorage) unless overridden.

  • Formula – Plan Specific Formula

    Global Node Formula Derived Formatted Memo Property, Overridable–Returns the non plan specific Formula (HP.Formula) unless overridden.

  • Valid For Plan – Indicates if the member is valid for the plan.

    Local Node Defined Boolean Property (Default: TRUE)

Enabling Additional Predefined Plan Types

The additional plan types for Capex, Hcp, and Workforce can be enabled by adding the properties to the import and export profiles. For the import profiles the properties for the plan type need to be added to the appropriate location in the columns of the relationship section of the import. For the export profiles the properties need to be added to the export columns and the export header must be modified to add the labels needed for the Outline Load Utility.

Adding New Plan Types

When a new plan type is to be added to the Planning system it must also be configured in Data Relationship Management. Custom properties need to be added for the new plan type and can be modeled after the properties for the predefined plan types:

  • Aggregation – Plan Specific Aggregation

  • Aggregation Code – Plan Specific Aggregation Code

  • Data Storage – Plan Specific Data Storage

  • Formula – Plan Specific Formula

  • Valid For Plan – Indicates if the member is valid for the plan.

In addition, the import and export profiles must be modified to add the new properties to the column sections as discussed in Enabling Additional Predefined Plan Types. New plan types must be added to the HP.SourcePlanType list of allowed values.

Plan Types Differing by Dimension

Some dimensions can be set up in Planning to only be in specific plan types. The import and export profiles must be modified to either add the plan types to the appropriate import and export profiles or to remove them from the appropriate import and export profiles to match the Planning system.

Weekly Distribution Setup

The Planning application template provides the support for the Weeks Distribution functionality. If the Weeks Distribution capability of Planning is being used, then you need to perform the following set up on the Data Relationship Management application:

  • Set the HP.WeeksDistributionApp property to the appropriate value for the Planning application.

  • Set the HP.WeeksDistribution property to True on the nodes that will use the Weeks Distribution.

  • Include the HP.WeeksDistribution property in columns for the appropriate dimension exports and modify the header record for the export to include the label for the column as required by the outline load utility.

Note:

The export header record label can always be “Use 445” even if other weekly distributions are being used.