About Data Maps and Custom Dimensions

Note the following when defining data maps when some of the Strategic Modeling accounts in the data map are associated with custom dimensions and some are not.

When creating a data map from Planning to Strategic Modeling, the data moves based on the following rules.

• When the root of the dimension in Strategic Modeling is part of the detailed mapping:

  • For accounts where this dimension is applicable, the root dimension mapping is ignored. (Data can’t be written to the root for valid accounts.)

  • For accounts where this dimension is not applicable, only the root dimension mapping is considered. (Data can’t be written to the nonexistent leaf members.)

  • For dimensions that have no members in Strategic Modeling, the data is always written to the root. (The root member is the only available member.)

• When the root of the dimension in Strategic Modeling is not part of the detailed mapping:

  • For accounts where this dimension is applicable, data movement occurs as defined in the data map definition. (Data can be written to all the members in the mappings.)

  • For accounts where this dimension is not applicable, each member in the target is replaced with the root dimension. The aggregated data for all the members is moved to the root of the Strategic Modeling dimension.

    If this is not the behavior you want, make sure you map the appropriate member in Planning to the root dimension in Strategic Modeling.

• When the dimension is part of the Unmapped Dimensions (for the Target):

  • For the accounts where this dimension is applicable, the data is pushed to the member defined in the target.

  • For the accounts where this dimension is not applicable, the data is pushed to the root.

When creating a data map from Strategic Modeling to Planning, the data moves based on the following rules.

When the root of the dimension in Strategic Modeling is part of the detailed mapping:

• When the custom dimension has multiple members selected, the custom dimension's root is applicable only for members whose custom dimension is not enabled.

• As part of data map validation, a check mandates mapping the custom dimension's root to avoid data duplication when custom dimensions are enabled. The root member is ignored if the section for the Custom dimension has multiple members in the mapping.

• Members assigned to the custom dimensions push the child members' values to Planning. If only the root member is defined in the data map, then the root member is pushed to Planning.