Loading Metadata Process Description

At a high level, this is how you load metadata from a file to a Planning application:
  1. Generate a metadata load file for each dimension to be loaded.

    A metadata load is only available to applications built on the Planning platform only.

    For information on how to construct a metadata load file, see Metadata Load File Considerations.

  2. In Target Application, register a target application for the class of dimension or dimension type.

    Data Management creates six-dimensions applications automatically: Account, Entity, Custom, Scenario, Version, and Smartlist.

    For more information on adding a dimension class or type as a target application, see Registering a Target Application for the Class of Dimension or Dimension Type.

    For more information on target applications, see Registering Target Applications.

  3. In Dimension Details, the system creates a record for each dimension property. Only the member name and parent are required fields.

    Image shows the Target Application screen

    To enable additional properties, add a row to the dimension metadata application. The name of the row is the property or attribute name used in the Planning application.

  4. Optional: To add a custom dimension (one designated as Generic in the Planning application), in the target application, select the property name and enable the Select Property field, and then map it to a Data Table Column Name value. Next create a separate import format for each generic dimension. Then, in the dimension's data rule, specify the dimension name (for example, Product, Movement) in the Dimension name of the data rule's target options.
  5. In Import Format, map the data from the metadata load file to the properties of the dimensions in the EPM application. This allows users to import dimension members from any file format. (The file must be "delimited - all data type" file type.)

    Image shows Import Format page

    For more information, see Defining Import Formats for File-Based Mappings.

  6. Define the location to specify where to load data.

    For more information, see Defining Locations.

  7. In data load mapping, map, transform, or assign values to properties of a dimension to the corresponding properties of the target application dimension member.

    Properties are added as "dimensions" of a dimension application. For example, the Two Pass Calculation property of Entity is added as a dimension and the flat file adds the "yes" or "no" property on the load.


    Checked dimensions in the dimension "application" are the ones loaded. If you do not map them, the load will fail. There is no default if a mapping is missing. To avoid loading a "field" such as alias, uncheck the check box in the target application. To supply a single value for all loaded rows, specify the value in the Expression field and map *to* for that dimension.

    For more information, see Creating Member Mappings.

  8. Define a data load rule to load the metadata.

    The data rule determines the data imported from the source system.

    For more information, see Defining Data Load Rule Details for a File-Based Source System.

    You check the box labeled "import from source" so that you can look at the data and the mapped results in the workbench prior to loading the data from the source system. After everything is confirmed, additional data imports can be loaded to the workbench and exported to the Oracle Enterprise Performance Management Cloud application in the same step.

  9. Execute the data load rule to define the options for running the data load rule.

    You can execute the data load rule for one or more periods. You then verify that the data was imported and transformed correctly, and then export the data to the target application.

    See the following data load rule topics:

  10. You can also create a batch for a metadata application and include rules from any of the metadata applications in the same batch. In this way, you can load all dimensions from a single batch and execute it in one step.

    For more information, see Working with Metadata Batch Definitions.