How to create Data Maps in PBCS

 

 

Data maps are maps between a source application and a reporting application. In PBCS this would typically be a Source Planning Application (BSO) and a Target Reporting Application (ASO). But could also be a Source Workforce Planning Application (BSO) and a Target Income Statement Application (BSO).

 

In the example below we will create a data map in the sample Vision Application from the Plan1 (BSO) database to the Vis1ASO (ASO) database.

 

If you want a detailed explanation on “What are Data Maps” click on the link.

 

Step 1: Log into PBCS and select the “Application” navigation flow.

 

 

Step 2: Under the “Application” navigation flow select “Data Maps”.

 

 

Step 3: The “Data Maps” page should now appear. Select “Create” in the top right corner.

 

 

Step 4: The Create mapping page should now appear. Enter a name for the mapping. The name I used was “MoveForecastData”. Enter a description too.

 

 

 

Step 5: Under the Source section select “Plan1”.

 

 

Step 6: Under the Target Section select “Via1ASO”.

 

 

Step 7: Select the Hyperlinked text “ILvl0Descendants(Account)” which is the default selection.

 

Step 8: Select AIIA->NI->0001->0002->GP. Select the function icon (fx) to the right and select “Level 0 Descendants”

 

 

 

Step 9: You should now see “ILvl0Descendants(GP)”. Also remove the default member “ILvl0Descendants(Account)”. Click on the settings icon to remove.

 

 

Step 10: You screen should now look similar to the screenshot below.

 

 

Step 11: You now need to set the correct members for Scenario, Version and Year.

 

Note: Channel, Entity, Period and Product will all be left as their respective default members.

 

 

 

Step 12: Select the default member for Scenario “ILvl0Descendants(Scenario)”. And then select the “Settings” icon, select “Remove”.

 

This will remove the default member.

 

 

 

 

 

Step 13: Select the “Forecast” member by clicking to the left of the member as shown in the screenshot below. It should now appear in the space where the default member was previously located.

 

 

Step 14: Repeat step 14 for Version and Year dimension. They should be set as below:

 

Scenario: Forecast

Version: Working

Year: FY14, FY15

 

Your settings should be similar to the screenshot below.

 

Next, select the “Options” button in the top right corner.

 

 

 

Step 15: You are not going to change any of the defaults in the options. Now just click “OK”

 

 

 

Step 16: In the Unmapped Dimensions it shows a dimension in the Source Application “HSP_View” that is not present in the reporting application. Therefore one member is selected “BaseData” to be used for that dimension in the mapping. Typically this member is a aggregation of all the data in the dimension.

 

Select the “Save and Close” button.

 

 

 

Step 17: Now you should see the new data map you created in the “Data Maps” screen.

 

Select the “Actions” icon (…) on the far right of the data map and then select “Push Data”.

 

 

 

Step 18: The “Push Data” window now appears. It asks “Do you want to clear the data before the push?”

 

It is asking if you want to clear the data on the target application before copying it over again.  Select “Yea”.

 

Typically it is best practice to clear the target area before you copy the data over.

 

 

 

 

Step 19: The “Information” message box should appear with the message “Push data was successful”.

 

 

Step 20: To check if there were any errors on the push select the “Jobs” button next to “Data Maps”

 

 

Step 21: Select the data map you just ran “MoveForecastData”.

 

 

Step 22: You will now see the details of the data map job and also you will any errors.

 

In this case there were no errors so nothing appears.

 

 

Step 23: We recommend to validate data in SmartView as well. We will normally setup a Source and Target worksheet and ensure that all the data is getting moved correctly.

 

 

If you have any questions please feel free to contact me at ggibney@gibneyconsulting.com