Initializing Data Relationship Management with Planning Dimensions

Exporting Dimension Members from Oracle Hyperion Planning

To populate Oracle Data Relationship Management from an existing Oracle Hyperion Planning application the dimensions can be exported using the Web interface or the Outline Load Utility formatted dimension file (one per dimension) so that they can be imported into Data Relationship Management.

See “Loading Data and Metadata” in the Oracle Hyperion Planning Administrator's Guide for more information on using the Outline Load Utility for Planning.

See Importing Planning Dimensions into Data Relationship Management for details on the import process into Data Relationship Management.

Planning Outline Load Utility Command Line

To process the outline load utility dimension files into Data Relationship Management:

  1. Create the Outline Load Utility files for each dimension from the Oracle Hyperion Planning application.

  2. Deliver the dimension files to a location that can be accessed by Data Relationship Management.

  3. Run the import profiles in Data Relationship Management for each dimension.

To export the dimensions using the Outline Load Utility command line, run the OutlineLoad command for each dimension with the following options:

  • [/M] - Headers

  • Specify the dimension by one of the following:

    • [/D:loadDimensionName]–Dimension to Process

    • [/DU:userDefinedLoadDimensionName]–User Defined Dimension to Process

    • [/DA:attributeLoadDimensionName:baseDimensionName]–Attribute/Base Dimension to Process

    • [/DAT:attributeLoadDimensionName:baseDimensionName]–Text Attribute/Base Dimension to Process

    • [/DAN:attributeLoadDimensionName:baseDimensionName]–Numeric Attribute/ Base Dimension to Process

    • [/DAB:attributeLoadDimensionName:baseDimensionName]–Boolean Attribute/Base Dimension to Process

    • [/DAD:attributeLoadDimensionName:baseDimensionName]–Date Attribute/Base Dimension to Process

    • [/DS:HSP_SMARTLISTS]–Smart Lists Dimension to Process

  • [/E:outputFileName]–Output Filename

  • [/8]–Use UTF8 File (Default)

For example: OutlineLoad -f:D:\Files\PswdFile.txt /A:Forecast /U:admin /M / D:Entity /E:D:\Files\Extracts\EntityMbrs.txt /L:D:\Logs\EntityMbrs.log / X:D:\Logs\EntityMbrs_Excptns.log

Exporting Dimension Members from EPM Cloud Planning

To populate Data Relationship Management from an existing Oracle Enterprise Performance Management Cloud Planning application the dimensions can be exported using the Web interface or the EPM Automate Utility which provides the ability to remotely perform the export tasks.

For more information, see "Using the EPM Automate Utility" in “Using Oracle Planning and Budgeting Cloud Service” and “Importing and Exporting into a Planning Application” in “Administering Planning for Oracle Planning and Budgeting Cloud Service”.

See "Exporting Metadata" in “Administering Oracle Planning and Budgeting Cloud Service Using the Simplified Interface”.

Note:

EPM Cloud Planning jobs must be configured for each of the tasks that are to be performed with the EPM Automate Utility. For the Data Relationship Management integration this includes any metadata import and export tasks that are to be run with EPM Automate. See "Scheduling Jobs" in “Administering Oracle Planning and Budgeting Cloud Service Using the Simplified Interface”.

To export metadata from EPM Cloud Planning using EPM Automate:

  1. Login to EPM Cloud Planning.

    Syntax: epmautomate login username password url identitydomain

  2. Execute the EPM Cloud Planning export metadata job (can include one or more dimensions).

    Syntax: epmautomate exportmetadata jobname filename

  3. Download the metadata file. It will be in a zipped format.

    Syntax: epmautomate downloadfile filename

  4. Log out of EPM Cloud Planning.

    Syntax: epmautomate logout

Importing Planning Dimensions into Data Relationship Management

After Data Relationship Management has been configured to match the Planning systems (Aliases, Plan Types, Weeks Distribution, Attribute Dimensions, and Generic/Custom Dimensions) then the data from the Planning systems can be imported into Data Relationship Management. This is designed to allow initial population of the Data Relationship Management hierarchies from existing Planning applications. It is not intended to be used as an ongoing process.

Note:

You do not need to do the import if the dimensions already exist or will be created in Data Relationship Management.

The imports are setup to do the following:

  • Process files in UTF-8 encoding

  • Assign hierarchy-level validations

  • Set the dimension property

  • Define the sort order property based on the record order

  • Determine leafs at the end of the import process

  • Warn on shared nodes (not error)

After running the imports the dimensions will be in separate versions. The Blender functionality can be used to combine the dimensions into a single version.

To import Planning dimensions into Data Relationship Management:

  1. Unzip the files to a location accessible to Data Relationship Management for import.

  2. You can use the Data Relationship Management Web Client or Batch Client to import Planning dimensions and blend them.

    1. Run the Data Relationship Management import for each Dimension file.

    2. Run a Data Relationship Management Blender to combine the dimensions into the production version.