Mapping ensures nodes and their relationships are represented accurately across applications. Mappings are used to define relationships between nodes in dimensions of different applications that share information with each other. In some cases, the dimensionality of source data does not match the target application, and mappings must be defined to determine how the shared data will be transformed in order to be consumed by the target application.

For an example, see Mapping Source Dimensions to Target Dimensions.

These are common scenarios for mapping:

• Map bottom level nodes from one application to a different application.

  For example, suppose your corporation acquires a subsidiary company and you want to map the subsidiary local accounts to your corporate accounts. You can use a mapping hierarchy to perform the mapping. This places the bottom level nodes in the mapping hierarchy instead of your corporate account dimension, keeping the corporate account dimension intact and less cluttered.

• Map general ledger transaction accounts to financial summarized accounts used for planning purposes.

  Note:

  In all scenarios, a mapping hierarchy set holds the mapping relationships separate from the hierarchy relationships in the dimension.

Considerations:

• Mapping is not supported for Oracle Financials Cloud General Ledger applications.
• For all other applications:
  • You can map bottom level source nodes to bottom level target nodes only.
  • You can map one or more source node types to one target node type only.
  • To export mapping data:
    • Use a view containing both the mapping viewpoint and a viewpoint bound to the target dimension.

    • For Planning and Financial Consolidation and Close applications, you can export the mapping data to a file or the inbox of an external application.

    • For Universal applications, you can export the mapping data to a file only.

  • Optionally, use the Core.Change.Sign property if you are mapping nodes of different types and need to reverse the sign on the target nodes. For example if you are mapping assets to liabilities add the Core.Change.Sign property and set it to True . When you export the mapping data:

    • If the target nodes are in a Planning or Financial Consolidation and Close application, a negative sign is added to the target node.

    • If the target nodes are in a Universal application, a column containing the negative sign is exported.

    When an external application imports the mapping data, it applies the change sign to the target nodes. For example, if your target is a Planning application and you are mapping asset nodes to liability nodes add the Core.Change.Sign on the source node type and set it to True. On export the change sign is added to the target node. Within Planning the Data Management module imports the data and applies the change sign to the target nodes.