Administrator Steps

As an administrator, set up a view with the source, target and mapping viewpoint for the user to work on as they map data.

Administrator Prerequisites

You must have the Application - Create role to register the applications. After you register the applications, you are assigned the Owner permission to the application and default view. You must also have the Views - Create role to create a maintenance view and viewpoints.

Administrator Process

1. Register and import the source and target applications.
2. Create a map binding. This also creates a hierarchy set, node set, and mapping viewpoint.
3. Create a maintenance view with viewpoints containing the source dimension, target dimension, and mapping viewpoint.
4. Define a mapping key.
5. Grant the Data Manager permission to the target application, and give the user the mapping key location name.

Administrator Detailed Steps

Register and import applications and dimensions

To register and import applications and dimensions:

1. Register the general ledger application, and import the general ledger account dimension, which is the source dimension, see Working with Universal Applications.

   Note:

   A default view, viewpoint, node set, hierarchy set, and node type are created with the name GL Account. The GL Account viewpoint, node set, hierarchy set, and node type are bound to the GL Account dimension.
2. Register the Planning application and import the planning account dimension, which is the target dimension, see Working with Planning and FreeForm Applications.

   Note:

   A default view, viewpoint, node set, hierarchy set, and node type are created with the name Planning Account. The Planning Account viewpoint, node set, hierarchy set, and node type are bound to the Planning Account dimension.

Create source node types for the map binding.

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.

1. Create node types, using the target dimension, to hold the source nodes in the mapping viewpoint, see Creating a Node Type.
2. Create node type converters to convert the node types from each source application to the node types you created in step 1 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).

Create a map binding

Create the map binding to bind source nodes to target nodes. See Creating a Map Binding.

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.

Set up a maintenance view

Set up a maintenance view to contain the source and target viewpoints.

1. Create the maintenance view, see Creating a View.
2. Add the source viewpoint with the GL Account node set.
3. Add the target viewpoint with the Planning Account node set.

   Note:

   See Creating a Viewpoint
4. Add the mapping viewpoint that was created when you created the map binding.
5. Create a top node for the mapping viewpoint using the target node type.

   This keeps the number of top nodes at a minimum. For example name it Account Mappings, then you can drag and drop target accounts under it.

   This image shows the mapping viewpoint with the top mode Account Mappings.
   
   

Bind the target viewpoint to the target dimension

Before you can create the mapping key and export mapping data using the maintenance view, it needs to contain both the mapping viewpoint and a viewpoint bound to the target dimension. 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.

Create the mapping key

The mapping key defines which source nodes types are mapped to target node types. To define the mapping key:

1. Create a Mapping Key, to define which nodes types are mapped to each other. Within the mapping viewpoint specify the source node type: Acquired GL Account and the target node type: Planning Account, see Defining Mapping Keys.

2. Set the Location Name to MapGLtoPlanning.

Give Information to Your User

Give the following information to your user:

• The name of the maintenance view to work in.
• Participant(Write) permission to the target application, see Assigning Application Permissions.
• The mapping key location name, MapGLtoPlanning, to use when exporting.

  Note:

  For user steps, see User Steps.