Mapping Source Nodes to Target Nodes

You can map nodes from one or more dimensions in source applications to a nodes in a dimension in a target application. First, you create at least one source node type for each source dimension. Then, you create a map binding that includes the source and target node types, and mapping keys that define locations for each source node type. Creating a maintenance view with the source, target, and mapping viewpoints enables you to map source to target nodes by dragging and dropping nodes from the source and target viewpoints into the mapping viewpoints. When you have finished mapping nodes, you can export the mapping.

To map source nodes to target nodes:

1. Create source node types for the map binding. You must create at least one node type for each source dimension. You can create multiple node types for a source dimension if necessary.

   1. Create node types, using the target dimension, to hold the source nodes in the mapping viewpoint, see Creating a Node Type.

      Note:

      You must create new source node types because you cannot use the source node types from the source applications. Node types are specific to dimension and applications.

   2. Create node type converters to convert the node types from each source application to the node types you created in step 1a above. See Working with Node Type Converters.
   3. Optionally, add the Core.Change.Sign property to the source node types if you are mapping nodes which require a sign change when transferring numerical data across applications (for example, if you are mapping an asset to a liability).

2. Create the map binding. See Creating a Map Binding.

   A map binding enables you to map node types to one another for different source and target systems.

   Note:

   When you add node types to the map binding, add all of the target node types that you want to map to as well as the source node types that you created for the mapping viewpoint.

   When you create the map binding, the following data chain objects are also created:

   • A new hierarchy set is created, and the target node types that you identified when you created the map binding are added to the hierarchy set.
   • A new node set is created and pointed to the new hierarchy set.
   • A new mapping viewpoint is created in the default view for the target application, and it is set to use the new node set.
3. (Optional) Configure the mapping hierarchy set. See Creating Hierarchy Sets.

   The hierarchy set that gets created when you create the map binding contains all of the source and target node types that you specified when you created the map binding. You can edit this hierarchy set if necessary:

   • If you have added additional source node types after you created the map binding, add them to your hierarchy set so that they can be used when you define the mapping keys.
   • Add relevant rollup rules for the nodes in the hierarchy set. For example, the target node type can have source nodes and itself as children, but the source node types cannot have any children.

4. Define the mapping keys. See Defining Mapping Keys.

   Mapping keys enable you to set up locations, which are combinations of the source and target node types that you select, in order to export the mapping data.

   Note:

   When defining the mapping keys, select the mapping viewpoint that was created when you created the map binding.

5. Create a maintenance view containing the source, target, and mapping viewpoints

   Set up a maintenance view to contain the source viewpoint, target viewpoint and mapping viewpoint that was created when you created the map binding. This will enable you to drag and drop nodes from the source viewpoint and target viewpoint into the mapping viewpoint.

   1. Create a view, see Creating a View.
   2. Create a viewpoint containing the source dimension, see Creating a Viewpoint.
   3. Create a viewpoint containing the target dimension.
   4. Create the mapping viewpoint using the node set that was created with the map binding.

6. Map source nodes to target nodes

   1. Open the maintenance view and click the Side by Side button (or , depending on your theme) to work with the viewpoints.
   2. Display the mapping viewpoint on the right, and toggle between the target and source viewpoints on the left.
   3. Within the mapping viewpoint:
      1. Create a top node using the target node type. For example, name it Mapping Account, if you are mapping account nodes, see Making Changes Interactively.

         Note:

         Use this top node to group the mapped target and source nodes. This enables mappings to be organized and keeps the number of top nodes at a minimum.
      2. Drag and drop a node from the target application. In the mapping viewpoint this will be a parent node.
      3. Drag and drop a node from the source application. In the mapping viewpoint this will be a child node.

         Note:

         You can map bottom level source nodes to bottom level target nodes only.
   4. Optional: If you are mapping nodes which require a sign change when transferring numerical data across applications, set the Core.Change.Sign property on the source node type to True, which will flip the sign on the target node. Otherwise leave the property set to False.
   5. Repeat these steps to map as many nodes as desired.
   6. To create the mapping key and export mapping data you need a view that contains both the mapping viewpoint and a viewpoint bound to the target dimension. To set this up, you can use one of these views:
      • Use the application default view which has a viewpoint bound to the target dimension created during application registration. Add the mapping viewpoint using the mapping hierarchy node set to the default view. Now the default view can be used to export both mapping data and dimension data.
      • Use the maintenance view and bind the target viewpoint to the target dimension.

        Note:

        In the maintenance view, the target viewpoint was created outside of application registration and by default is not bound to the target dimension. To bind the target viewpoint, edit the target dimension's existing binding and change it to point to the target viewpoint. See Identifying Objects Bound to Dimensions.

7. Export the mapping data. See Exporting Mapping Data.

Optionally, you can import the mapping data to Planning or Financial Consolidation and Close, using Data Management.

Tip:

If you add source node types after you have already created the map binding, follow these steps to add them to your mapping viewpoint:

1. Add the new source node types to the hierarchy set that was created when you created the map binding.
2. Add rollup rules for the source node types in the hierarchy set.
3. Add the new source node types in your mapping keys.