1. Administering and Working with Oracle Enterprise Data Management Cloud
  2. Administration
  3. Integrating Data
  4. Exporting Mapping Data

Exporting Mapping Data

Exporting mapping data is designed to work with Data Management for Enterprise Performance Management systems, such as:

  • Planning, Planning Modules, and FreeForm target dimensions
  • Financial Consolidation and Close target dimensions
  • Enterprise Profitability and Cost Management target dimensions

You can also export mapping data for Universal target dimensions.

Videos

Your Goal Watch This Video

Learn about mapping data across applications.

video icon Mapping Data Across Applications

Before you begin:

  • Ensure that you have the Data Manager permission on the dimension that you are exporting from.
  • Ensure that the dimension that you are exporting from has an Active status.
  • Ensure one or more mapping keys are defined for your source and target nodes in the mapping hierarchy. You will need the location name from the mapping key, see Defining Mapping Keys.
  • If you are using a Universal application you can export the mapping data to a file only.
  • If you are using Planning, Planning Modules, FreeForm, or Financial Consolidation and Close you can export the mapping data to:
    • A file
    • The Data Management inbox, using the external application connection.

      You can view connection settings by inspecting the application. From Applications, scroll to your application, click ellipsis button, then select Inspect, and then select Connection.

      After the export, you can use Data Management , within your external application, to import the mapping data, see Importing Member Mappings in Administering Data Management for Oracle Enterprise Performance Management Cloud

You can export mapping data for one or more mapping keys. For example, if you mapped two source applications to one target application and defined two mapping keys, export the mapping data twice using the two mapping key location names. To export mapping data:

  1. From Applications, find your application, click select ellipsis, and then select Export Mapping.

  2. From Location, select a location name defined in your mapping keys for the selected dimension.

    You need to have already set up mapping keys for the dimension, see Defining Mapping Keys.

  3. Select the target dimension.

  4. From Export Target, select File or Connection, and then do one of the following:

    • If you selected Connection, select a connection to export to, and specify an export file name.

    • If you selected File, a file name is generated. The default file name is Application Name_Dimension Name_Date_Location Name.csv, for example Planning_Account_20200123_loc1.csv, and can be edited before running the export.

  5. Click Export.

You can also export dimensions using EPM Automate (see exportDimensionMapping in Working with EPM Automate for Oracle Enterprise Performance Management Cloud), a REST API (see Export Dimension Mappings in REST API for Oracle Enterprise Data Management Cloud Service), or Task Manager (see Automation Integrations for EPM Cloud in Administering Financial Consolidation and Close).

Mapping Data File Formats

The exported data file from a Universal application dimension is a .csv file with these columns:

  • Source node name
  • Target node name
  • A column that contains True or False taken from the Core.Change.Sign property in the source node type. If the Core.Change.Sign property is not used, this column defaults to False.

The exported data file from a Planning application dimension is a .csv file with these columns:

  • Source—Name of source node
  • Target—Name of target node

    Note:

    If the source node has the Core.Change.Sign property, it is applied to the target node. For example, if Core.Change.Sign is True, a negative sign is applied to the target node.
  • Rule Name—Blank
  • Rule Description—Blank
  • Load Rule—Blank

For example, if these nodes are in your Planning mapping viewpoint and

The source node is: CC11100

The Core.Change.Sign property on the source node is set to True

The target node is: 100

The mapping export row will be: CC111000,-100 , , , the columns are separated by commas.

After the export, navigate to your external application and import the mapping data. Within your external application, open the Data Management module and import the mapping data. During the load the negative sign is applied to values in the target node for the selected mapping key which is the location in Data Management.