1. Administering and Working with Oracle Enterprise Data Management Cloud
  2. Administration
  3. Working with Data Objects and the Data Chain
  4. Understanding Bindings and Bound Data Objects
  5. Creating Bindings
  6. Creating a Map Binding
  7. Defining Mapping Keys

Defining Mapping Keys

You create mapping keys to specify the source node types mapped to target node types and to define a location name to export the mapping data. These are considerations:

  • Mapping keys are used for mapping exports for Enterprise Performance Management applications only. See Exporting Mapping Data.

  • Define one mapping key, one for each source node type mapped to a target node type. For example, if you map two source applications to one target application, define two mapping keys defining the mapping relationship from each source node type to the target node type. A source node type can be mapped to one target node type only.

  • Each mapping key is identified by the unique location name you enter. The location name is used to export the mapping data and by the consuming or external application to import the mapping data. For example, use the location name in Data Management to import mappings in Planning.

Before you define the mapping key, set up the maintenance view for mapping. See Creating Mapping Viewpoints.

To define a mapping key:

  1. From Applications, find the application containing the target dimension.
  2. In the application's Action column, click Ellipses button
  3. Click Inspect, and from the Dimensions tab, select the target dimension.

    The dimension's inspector dialog displays.

  4. On the Bindings tab, select the mapping binding or click Create Map Binding to create one.

    Note:

    The Create Map Binding button is not visible if a mapping binding already exists.

  5. In the binding inspector, click Mapping, and then click Edit.

    The Mapping tab displays all mapping viewpoints that meet this criteria:

    • The viewpoint is active.
    • The viewpoint uses the same dimension and application you are inspecting.
    • The viewpoint is not bound to the target dimension.
    • The viewpoint is in the same view as the viewpoint bound to the target dimension.
  6. Select the mapping viewpoint.
  7. Click Create, and then enter:
    • Location name to be used when exporting mappings to an external application.

      Note:

      For Planning and Financial Consolidation and Close applications, use the Location name to import the mapping data using Data Management.
    • Source node type (can be Normal, Lookup, or Legacy GL class)
    • Target node type (can be Normal, Lookup, or Legacy GL class)

Note:

You do not need to set the Default check box; it is not used at this time.