Import Scenario Case 1: Importing Data when Member Names Match

This example walks you through the steps to importing data into a Planning application when the member names in the source system match the member names in Planning.

See Review the Import Format.

Review the Import Format

When you create a Planning application, a default import format is automatically created, with the name appname_1. You use this import format to map a source data file to the Planning application. This import format assumes that the order of dimensions in the CSV file are: Account, Entity, Amount, and then any custom dimensions in alphabetical order. If you want to use a different file format, you adjust the format.

  Review the default Import Format:

  1. Select Navigate, then Administer, and then Data Management.

  2. Select the Setup tab, and then click Import Format.

  3. On Import Format, confirm the settings.

    Note:

    • The File Delimiter drop-down list specifies the character that separates values in the file.

    • The Field Number column specifies the order of fields in the load file. The import format assumes the order of dimensions are Account, Entity, Amount, and then any user defined dimensions. All dimensions must be in alphabetical order.

  4. Click Save.

See Review the Default Location.

Review the Default Location

The Location is used as a container to load data from Data Management. When you create a Planning application, a default Location is automatically created with the name appname_1.

  To review the default location:

  1. On the Setup tab, click Location.

  2. Review the Location settings. For example:

    Screenshot of Data Management Location window

    You can update the location as needed to include different selections for such aspects as the check rule. For more information, see Administering Data Management for Oracle Planning and Budgeting Cloud Service.

  3. Click Save.

See Create the Data Load Mapping.

Create the Data Load Mapping

Data load mappings define relationships between source dimension member values and target dimension members in one dimension. The mappings are used to derive the target members for each dimension based on the source value. The Data Management component uses the data load mappings during the data load to dimensionalize the data that is loaded to the target dimension. You must create a data load mapping for each target dimension.

  To create the data load mapping:

  1. Select the Workflow tab, and then click Data Load Mapping.

  2. From the Dimensions drop-down list, select and then define the relationship between the Source Value and the Target Value for each dimension.

    You must specify the dimensional intersection for every data value that you want to import.

    For example:

    Screenshot of Data Load Mapping in Data Management component

    1. Because the source and target member names match in this example, on the Like tab, enter * in the Source and Target text boxes.

    2. Under Rule Name, enter the name of the rule.

    3. Click Save.

See Create and Execute the Data Load Rule.

Create and Execute the Data Load Rule

After creating a data load mapping, you define a data load rule. Data load rules are defined within locations.

  On the Workflow tab, click Data Load Rule.

  1. Click Add.

  2. Under Details on the Data Load Rule window, you define the rule.

  3. In this example, you will browse to a file:

    1. Name and describe the rule.

    2. For Category, select the Planning scenario.

      When you create a Planning application, a default Category mapping is created to map to the Planning Scenario dimension and a default Period mapping is created based on the Planning Period dimension.

    3. Select the Plan Type for which you want to load data.

    4. Click Select to browse to the data load file.

    5. Click Save.

  4. To run the data load rule, using the mapping that you created, click Execute.