Creating Maps

  To create a cube-to-cube map:

1. In the Model, go to the Object Details Graph tab, click the line between the cubes, and select Edit Mapping.

   A Cube Mapping Wizard is displayed, where you can edit information about the mapping.

2. Review Source and Target cube information.

3. Define the Cube Scope for the source and target cubes by selecting a scope type and entering a value for each dimension.

   The cube scope defines which members participate in the data flow from the source cube to the target cube.

   • All

   • Function—Define a custom function; which, when evaluated, returns a list of members that participate.

   • Level—Select a level in the dimension hierarchy. The members in that level are the members that participate.

   • Member—Explicitly specify the members that participate.

4. Review or edit Dimension Map information for the source and target cubes.

   To view detailed information for a dimension, click the dimension name. The information is displayed under Dimension Map Details. To change dimension map information, click Edit.

   • Dimension

   • Namespace—Name to uniquely identify dimension members

     When creating a dimension map, Integrated Operational Planning passes the name of the dimension and the value of the namespace to the mapping function to evaluate the target members.

     In the following example, when Integrated Operational Planning evaluates the mapping function, it uses the “ProductLine” argument as well as the namespace and dimension values to determine the target dimension members.

     dimension=”Product”
     namespace=”ESG”
     mapping=”oneToOneMap(ProductLine)”

     The namespace can be the same as the dimension name, but it need not be. See Dimension Namespaces for detailed information on namespaces.

   • Transformation—An optional function applied to the result of the mapping function

     Integrated Operational Planning first maps source members to target members using the mapping function (oneToOneMap(ProductLine) in the previous example). If the target members are unavailable after mapping is complete, the transformation information is used. Transformation information is applied in the context of the target dimension.

     See Member Functions.

     The following is a sample dimension map:

     dimension=”Manufacturing”
     namespace=”Manufacturing”
     mapping=”calendarmap(Fiscal)”
     transformation=”childMembers”

   • Mapping Type—Simple, Advanced, or Fixed Member

     • For Simple mappings, define the type of mapping and the dimension to which to map. See:

       • Member Name Mapping Functions:

         • exactMap

         • oneToOneMap

       • Time Dimension Mapping Functions:

         calendarMap

     • For Advanced mappings, click Add and select the mapping types. See:

       • Member Name Mapping Functions:

         • exactMap

         • oneToOneMap

       • Time Dimension Mapping Functions:

         calendarMap

       • Dimension Member Attribute Name Mapping Functions:

         • attributeMap

         • attributeReverseMap

       • Splicing and Splitting Mapping Functions

       • MDX Extensions:

         • RowSourceLookup(RowSourceColumn [, tuple])

         • RSQLGenerateSet(RSQLQuery [,dimHierarchy, NameColumn,NameSpaceColumn]+)

     • For Fixed Member mappings, select the member.

5. Click Save.

  To create a row source-to-cube map:

1. In the Model, go to the Object Details Graph tab, click the line between a row source and a cube, and select Edit Mapping.

2. In the Row Source Mapping Wizard, review Source and Target information.

   • Row Source—The source row source for which you are editing the mapping

   • Cube—The target cube for which you are editing the mapping

   • Custom Mapping—Whether to use custom mapping for each specific measure. Select True to use a Java class for the mapping; otherwise, select False.

   • Partial Map—Select True if all of the cube dimensions are not mapped to row source key columns; otherwise, select False.

     Note:

     If the row source is time-varying, and all the dimensions except time are mapped, select False.

   • Summarized Value—Select True to aggregate multiple values from a row source to single value in a cube. Select False for one-to-one mapping.

3. Define Default Map information.

   For each cube dimension in the measure:

   • Select a row source column.

   • Optional: Select Fixed Member to add a member name.

   • Select an attribute name.

     If no attributes are assigned to the cube dimension, none is the only option for Attribute Name. You assign attributes to dimensions in step 5 in the Dimension Wizard.

     See Creating a Dimension.

   • Enter a namespace, or select Use Row Source Column as Namespace and select a row source column from the menu.

     If you defined custom mapping as true on the Source and Target wizard page, enter the following additional information:

   • Custom Mapper Class—Class to generate the mapping from row source row to cube cell

   • Key Generator Class—Class to generate the row source keys given a cube cell

4. Define Measure Specific Maps.

   If you defined custom mapping as false on the Source and Target wizard page, to define measure-specific maps, click Add Measure Map and select a measure.

   If you defined custom mapping as true on the Source and Target wizard page, you cannot define measure-specific maps.

5. Define Filter information.

   Click Create and enter the following filter details:

   • Measure—Select a measure or leave at All Measures to include all measures in the filter.

   • Column—Select a column.

   • Value—Enter a measure value.

   • Dimension—Select a dimension.

   • Operator—Select an operator.

   • Format—Optional Format for the filter value. You can leave the Format blank.

     To edit a filter, click Edit.

6. Click Save.

  To create a data source-to-row source map:

1. From the Model tab, select the Object Details Graph tab, then click the line between a data source and a row source, and then select Edit Mapping.

2. In the Data Source Mapping Wizard, review Source and Target information.

   • Name—Name used to identify the map (Assigned by Integrated Operational Planning)

   • Data Source—Source data source for which you are editing the mapping

   • Row Source—Target row source for which you are editing the mapping

   • Groups—Used to combine the related set of row sources. Integrated Operational Planning defines all the stagemaps with a group name of Bootstrap-RowSource-Stagemaps. Using this model group, you can create without entering commands for each stagemap.

3. Define Column Maps.

   For each target column, perform an action:

   • Select a source column.

   • Select Advanced, and then click Add to add source columns.

4. Define Filters.

   Click Create, select a filter type, and then enter filter details:

   • Simple Filter

     • Data Source Field—Field on which to filter the information

     • Filter Operator—Operator to use in the filter

     • Filter Value—Value for the filter. To include columns in the filter value, click Add and select a column.

     • Non-matching are Errors—Whether to log data values that do not match filter values in the error log file. Select True or False. (The default is False; data values that do not match filter values are not entered in the log file.)

   • Row Source Filter

     • Data Source Field—Field on which to filter the information

     • Row Source—Row Source to use in the filter

     • Row Source Column—Row Source column to use in the filter

     • Match—Select True to allow only matching records in the filter. Select False to allow only nonmatching records in the filter.

     • Non-matching are Errors—Whether to log data values that do not match with filter values in the error log file. Select True or False. (The default is False; data values that do not match filter values are not entered in the log file.)

   • Dimension Filter

     • Data Source Field—Field on which to filter the information

     • Dimension—Dimension to use in the filter

     • Filter On—Select Namespace or Hierarchy. If you select Namespace, enter a value. (If you leave the Namespace value blank, the default hierarchy is used.) If you select Hierarchy, select a hierarchy and a hierarchy level.

       See Dimension Namespaces and Dimension Hierarchies.

     • Allow Members—Select True to include only the records that exactly match the dimension member names. Select False to include only the records that do not match dimension member names.

     • Non-matching are Errors—Whether to log data values that do not match filter values in the error log file. Select True or False. (The default is False; data values that do not match filter values are not entered in the log file.)

   • Distinct Filter

     • Filter Value—Value for the filter. To include columns in the filter value, click Add and select a column.

     • Distinct—Whether data should have distinct values across the data set. Select True or False.

     • Non-matching are Errors—Whether to log data values that do not match filter values in the error log file. Select True or False. (The default is False; data values that do not match filter values are not entered in the log file.)

   • Custom Filter

     • Class Name—Java class name that contains the custom filter logic

     • Parameters—Parameters passed to the Java class

5. Define Custom Processing information.

   • Custom Pre-processing

     To define custom pre-processing details, click Create and enter:

     • Class Name—Java class containing preprocessing logic before staging starts for this stage map

     • Parameters—Parameters passed to the preprocessing Java class

       To define parameters, click Add and enter a value, type, and format for the parameter.

   • Custom Post-processing

     To define custom postprocessing details, click Create and enter:

     • Class Name—Java class containing postprocessing logic after staging ends for this stage map

     • Parameters—Parameters passed to postprocessing Java class

       To define parameters, click Add and enter a value, type, and format for the parameter.

6. Click Save.

  To create data source-to-dimension maps:

1. From the Model tab, select the Object Details Graph tab, then click the line between a data source and a dimension, and then select Edit Mapping.

2. In the Data Source Mapping Wizard, review Source and Target information.

   • Name—Name used to identify the map (Assigned by Integrated Operational Planning.)

   • Data Source—The source data source for which you are editing the mapping.

   • Dimension—The target dimension for which you are editing the mapping

   • Groups—Used to combine the related set of row sources. Integrated Operational Planning defines all the stagemaps with a group name of Bootstrap-Row Source-Stagemaps. Using this model group, you can create without entering commands for each stagemap.

3. Define Hierarchy Level Maps.

   The hierarchies defined as part of dimensions are displayed here. Use hierarchy level maps to:

   • Define how to map the data source to members in different levels of the hierarchy.

   • Map the dimension member attributes.

   • Define the mapping for the attributes defined in the dimension.

     To view details about a hierarchy level, click a hierarchy and review its details under Hierarchy-Level Map Details.

     To edit a hierarchy level, select a hierarchy, click Edit, and define mapping information by either selecting a column or entering value for each of the following:

     • Parent—Parent level in the hierarchy

       As an example of entering a value, assume that you have a parent level of family_name. Assume further that you want to combine two columns (family_name and capacity) and change the parent name. In this case, you would enter ${family_name}#${capacity} as the value.

     • Namespace—Name to uniquely identify dimension members

       See Dimension Namespaces.

     • Name Column—Data source column that indicates the member name or an expression that combines data source columns

     • Display Name Column—Data source column that indicates the display name or an expression that combines data source columns

     • Description Column—Data source column that indicates the description or an expression that combines data source columns

     • realName Attribute—Attributes defined in the dimension

4. Define Filters.

   Click Create, select a filter type, and enter filter details:

   • Simple Filter

     • Hierarchy Level—Hierarchy level on which to filter the information

     • Data Source Field—Field on which to filter the information

     • Filter Operator—Operator to use in the filter

     • Filter Value—Value for the filter. To include columns in the filter value, click Add and select a column.

     • Non-matching are Errors—Whether to log data values that do not match filter values in the error log file. Select True or False. (The default is False, data values that do not match filter values are not entered in the log file.)

   • Row Source Filter

     • Hierarchy Level—Hierarchy level on which to filter the information

     • Data Source Field—Field on which to filter the information

     • Row Source—Row source to use in the filter

     • Row Source Column—Row source column to use in the filter

     • Match—Select True to allow only matching records in the filter. Select False to allow only non-matching records in the filter.

     • Non-matching are Errors—Whether to log data values that do not match with filter values in the error log file. Select True or False. (The default is False, data values that do not match filter values are not entered in the log file.)

   • Dimension Filter

     • Hierarchy Level—Hierarchy level on which to filter the information

     • Data Source Field—Field on which to filter information

     • Dimension—Dimension to use in the filter

     • Filter On—Select Namespace or Hierarchy. If you select Namespace, enter a value. (If you leave the Namespace value blank, the default hierarchy is used.) If you select Hierarchy, select a hierarchy and a hierarchy level.

       See Dimension Namespaces and Dimension Hierarchies.

     • Allow Members—Select True to include only the records that exactly match the dimension member names. Select False to include only the records that do not match dimension member names.

     • Non-matching are Errors—Whether to log data values that do not match with filter values in the error log file. Select True or False. (The default is False, data values that do not match filter values are not entered in the log file.)

   • Distinct Filter

     • Hierarchy Level—Hierarchy level on which to filter information

     • Filter Value—Value for the filter. To include columns in the filter value, click Add and select a column.

     • Distinct—Whether data should have distinct values across the data set. Select True or False.

     • Non-matching are Errors—Whether to log data values that do not match filter values in the error log file. Select True or False. (The default is False, data values that do not match filter values are not entered in the log file.)

   • Custom Filter

     • Hierarchy Level—Hierarchy level on which to filter information

     • Class Name—Java class name that contains the custom filter logic

     • Parameters—Parameters passed to the Java class

5. Define Custom Processing information.

   • Custom Pre-processing

     To define custom preprocessing details, click Create and enter:

     • Class Name—Java class containing pre-processing logic before staging starts for this stage map

     • Parameters—Parameters passed to the pre-processing Java class

       To define parameters, click Add and enter a value, type, and format for the parameter.

   • Custom Post-processing

     To define custom pre-processing details, click Create and enter:

     • Class Name—Java class containing postprocessing logic after staging ends for this stage map

     • Parameters—Parameters passed to postprocessing Java class

       To define parameters, click Add, and enter a value, type, and format for the parameter.

6. Click Save

  To create and edit allocation maps:

1. On the Object Browser View menu, select Cubes and select a cube, and then click Actions and select Edit.

2. Click Allocation maps.

3. To create an allocation map, click Create. To edit a map, click an allocation map and click Edit.

4. Enter Properties information.

   • Name

   • Source Dimension

5. Define the Allocation Scope.

   In the Source Scope and in the Target Scope, for each dimension, enter or review:

   • Scope Type—For example: not mapped, all, level, levels, nonLeaves

   • Value—For example, if you selected levels for the Scope Type, then you could select Summary, Plant, Department or Critical Resource.

   The functions for the Source Scope Members and Target Scope Members are shown on the Cube Wizard, under Allocation map details:

   Source Scope Members example:

   [level(ProductLine.ProductLine."Product Line")] [levels(Resource.Resource.Summary, Resource.Resource.Plant, Resource.Resource.Department)]

   Target Scope Members example:

   [level(ProductLine.ProductLine."Product Line")] [levels(Resource.Resource.Plant, Resource.Resource.Department, Resource.Resource."Critical Resource")]

6. Enter or review Dimension Map information for the source and target dimension.

   To view detailed information for a dimension, select the dimension name. Information is displayed under Dimension Map Details. To change dimension map information, click Edit.

   • Dimension

   • Namespace—Name to uniquely identify dimension members

     See Dimension Namespaces.

   • Mapping Type—Select Simple or Fixed Member

     For Simple mappings, define the type of mapping and the dimension to which to map.

     See Mapping Functions.

     For Fixed Member mappings, select the member.

7. Click Save .