Pushing Data Between Strategic Modeling and Planning Using Data Maps

You can push data between Strategic Modeling and Planning using data maps. You can define data maps that push data:

  • From a Strategic Modeling model or consolidation to a Planning cube.
  • From a Planning cube to a Strategic Modeling model.

Advanced options let you define complex mappings to or from multiple dimensions to or from a single dimension and between members with different names. These advanced data map options are available only if Strategic Modeling is enabled and is a source or target in the data map.

Administrators have privileges to create, edit, and run data maps.

To create a data map:

  1. From the Home page, click Application Application icon, then Data Exchange Data Exchange icon, and then click Data Maps.
  2. Click Create.
  3. Enter a name and description for the data map.
  4. Under Source, select the source for the data. You can select:
    • A Planning input cube (Block Storage) from the available cubes for the current application.

      Note:

      Reporting cube (Aggregate Storage) is not supported as a source.

    • A Strategic Modeling model. You can select from any models in the selected application.
    • A Strategic Modeling consolidation. You can select from any consolidations in the current application. When the source is a consolidation, metadata is pulled from the root model of the consolidation.

    Note:

    If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize.

    You can perform synchronize action in two ways:

    1. In the initial data maps screen (step 1) by accessing it through Actions of a listed data map.
    2. During creation/modification of a data map, by using the Actions
    • Planning to Planning—Updates metadata changes in the target Strategic Modeling model.
    • Planning to Strategic Modeling—Updates metadata changes in the target Strategic Modeling model.
    • Strategic Modeling to Planning—Updates only metadata in the source Strategic Modeling model.
    • Strategic Modeling to Strategic Modeling—Updates the metadata changes for both the source and target models.
  5. Under Target, select:

    • A Planning input cube (Block Storage) or reporting cube (Aggregate Storage) from the available applications, if the source is a model or a consolidation.
    • A Strategic Modeling model if the source is a Planning input cube (Block Storage).

    If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize.

  6. Define how to map dimensions between source and target:.

    Under each mapped dimension, click Select, and then select the artifact or artifacts to use.

    These dimensions are automatically mapped:

    • Model in Strategic Modeling and Entity in Planning.

      You can select multiple models (from a list of all the models in the application) as a target. For example, you might have multiple entities in Planning that map to multiple models in Strategic Modeling. Multiple selections must have a one to one mapping between model and entity.

    • Scenario (or Business Case if the source is a consolidation) in Strategic Modeling to Scenario in Planning. Multiple selections must have a one to one mapping between Scenario in Strategic Modeling and Scenario in Planning.
    • Account in Strategic Modeling to Account in Planning. You can select multiple accounts.

      Tip:

      Account members with the same name are automatically mapped (based on the Description in Strategic Modeling and the Name in Planning.) Click Map in the Account row to see the mappings.

      Tip:

      If you know all of the member names, you can skip this step and enter the member names directly in Advanced Data Maps. See Defining Advanced Data Maps.
    • Dimensions with the same name.

    Other dimensions are in the Unmapped Dimensions list.

  7. Map any remaining dimensions from the Unmapped Dimensions list if required. Click the arrow next to a dimension in the Unmapped Dimension list to move it to the Mapping area. Select the dimension to map it to, and then click Select to select the members to map. For any unmapped dimensions, select a member.

  8. Map any custom dimensions.

    Map custom dimensions in the same way you map base dimensions. Members associated with a custom dimension are shown under the custom dimension rather than under the Account dimension.

    If the data map includes accounts that aren't part of the custom dimension, map the root of the custom dimension in Strategic Modeling to a specific member in Planning. Data for accounts that aren't part of the custom dimension are pushed to this member.

  9. If required, you can map to or from multiple dimensions to or from a single dimension:
    1. Click Actions Actions menu for Data Maps next to a mapping row and then select Add Source Mapping or Add Target Mapping.
    2. Select the additional dimension to map, and then select the members to map.

      For example, you might want to map the Time dimension in Strategic Modeling to the Years and Period dimensions in Planning.

      Or, you might want to map the Business Case in Strategic Modeling to Scenario and Version in Planning. Including the Version dimension allows runtime input when you run the consolidation.

  10. To exclude source members from the data map, click Actions Actions menu for Data Maps next to a mapping row and then select Add Exclusion. Define the member or members to exclude and then click OK. The excluded member or members are shown on the Data Maps page.

    Excluding members while moving data is useful if you don't want to overwrite certain data at the target location or if you want to avoid getting warnings if data at the target location is not present. Also, exclusions can ignore specific source member data while data is required for all other source members.

    When excluding members from a dimension, the member list for the dimension must contain at least one member that is not on the excluded member list in order for the data map to successfully save and run.

    To remove one or more excluded members from the exclusion list, click the members in the exclusion list, and remove the member or members from the list using the Member Selector.

    To remove the entire exclusion, click Actions Actions menu for Data Maps next to a mapping row and then select Remove Exclusion.

    Tip:

    If you set up Smart Push for a form, you can also exclude members from the Smart Push. See Configuring Smart Push for a Simple Form. When you define Smart Push for a Planning form to push data to Strategic Modeling, the members defined for the Smart Push must match the members defined in the data map.
  11. If the member names don't match in the source and target, or when mapping to or from multiple dimensions to or from a single dimension, you must define an advanced data map. See Defining Advanced Data Maps. You can also use advanced data maps to define mappings when you know all the member names.
  12. Click Save and Close at any time. If the data map definition is not yet complete, you will receive an error, but you can save the data map as a draft so you can continue to work on it at another time.
  13. Associate the data map with a model or consolidation:
  14. Optionally, specify options that define how to execute the data map. See Defining Data Map Options.

For information about running data maps, see Running a Data Map.

Videos

Your Goal Watch This Video

Learn about creating data maps to move data between Strategic Modeling and Planning.

video icon Creating Data Maps and Moving Data from Strategic Models After Consolidation

video icon Creating Data Maps to Move Data between Planning Cubes and Strategic Models