Writing Back Data

Power user access is required for these steps.

Now that you have copied metadata and data from Structured Planning, Consolidation, and Reporting applications to the Dynamic Planning application, you have the option to use your new model read-only or read-write. There is not a live link between Structured Planning, Consolidation, and Reporting applications and the Target model, so any changes you make in the Dynamic Planning model remain only in that model unless you explicitly write them back to Structured Planning, Consolidation, and Reporting applications.

To set up your environment for write-back:

• Structured Planning, Consolidation, and Reporting applications: set up access to the Web Service

• Structured Planning, Consolidation, and Reporting applications: set up a Data Load Rule that will accept incoming data from Dynamic Planning

• Dynamic Planning: set up the URL address pointing back to Structured Planning, Consolidation, and Reporting applications

• Dynamic Planning: set up a Data Map to map dimensions and members back to Structured Planning, Consolidation, and Reporting applications

• Dynamic Planning: set up a Calculation to run the Data Map

• Structured Planning, Consolidation, and Reporting applications: run a report to validate that data has been changed

With this setup, you will be able to run the Calculation whenever you want to write data back to Structured Planning, Consolidation, and Reporting applications.

Structured Planning, Consolidation, and Reporting Applications: Configure Access to Web Services

In Structured Planning, Consolidation, and Reporting applications, login and select the Application that will receive data updates from Dynamic Planning.

In Practice: Maintenance > Configuration Tasks

1. Select Web Service Access.

2. On the Web Service Access page:

3. Under API, select Enable.

4. Look at the State Free Authentication URL and copy/paste it into Notepad or another document for safekeeping.

5. In the Available Users box, specify the username that will have access to both the Structured Planning, Consolidation, and Reporting applications and the Dynamic Planning application. Then use the right arrow to move the username into the Email User(s) list so that you will receive an email at the conclusion of each write-back.

   

6. Click Save and Complete.

Structured Planning, Consolidation, and Reporting Applications: Configure a Data Load Rule to Accept Data from Dynamic Planning

Be sure that you are still logged in. Now you will create a data load rule that will accept incoming data from Dynamic Planning.

In Practice: Maintenance > Data Load Rules

1. Click New Data Load Rule. Then specify:

   • Rule name

   • Load Type: Web Services

   • Load Item: Data

   • Load Sub Item: GL Data

     

2. Then click Next or Select Sample Input File.

   Specify the following items:

   • Row Containing Header: 0

   • Number of Rows to Skip: 0

   • Number of Source Fields: the number of segments in your Structured Planning, Consolidation, or Reporting applications (not your model) plus three (Fiscal Year, Fiscal Month, and Amount)

   • Do not change the other fields on this page.

     

3. Click Next or Define Overall Rule Settings.

   Specify the following items:

   • Reporting: Common Currency

   • Credit/Debit: No for negative numbers, Yes for positive numbers

   • Data Type: MTD or YTD (whichever you chose in your initial download Map)

   • Calculate Trial Balance: No

   • Currency Conversion: either Yes or No

   • Scenario Type: All

   • Scenario: select the Scenario containing the changes that are to be written back

   • Frequency: Month

   • Time Mapping: Down Rows

   • Automatic Cube Refresh: Yes

   • Roll Annual Balances: No

   Here is an example:

   

   Do not change the “Defaults” and “Clear Data Combination” sections.

4. Click Next or Manipulate Input File.

   No changes on this page.

5. Click Next or Define Data Mappings.

   From the list boxes, select the segments that correspond to the dimensions in your Map, in alphabetical order. You do not need to map Scenario, Reporting, Time, or Measures. The last 3 columns must be Fiscal Year, Fiscal Month, and Amount.

   

6. Click Next or Load Data.

   Select the Scenario you chose in your Map or that data has been changed in.

7. Click Finish.

Dynamic Planning: Set Up the Address Back to the Structured Planning, Consolidation, and Reporting Applications

In Dynamic Planning, login and select the Application that will send data updates to Structured Planning, Consolidation, and Reporting applications.

Manage > Application Settings

In the Soap Uri box, paste the State Free URL that you previously copied in “Maintenance > Configuration Tasks .” Be sure the Username and Password information is up-to-date. (If you have previously entered the username and password, the password field will be blank.) Click Save.

Dynamic Planning: Mapping Data Back to Structured Planning, Consolidation, and Reporting Applications
When you brought data into Dynamic Planning from Structured Planning, Consolidation, and Reporting applications, you specified how the data which had been downloaded into HACPM_Financial should map to the Dynamic Planning target model (called Integration):

• HACPM_Financial was the Source.

• Integration was the Target.

Here is the map used in Model > Map before downloading the data.

Now you need to map data from Dynamic Planning to Structured Planning, Consolidation, and Reporting applications so Source and Target are reversed.

• Integration is now the Source.

• HACPM_Financial is now the Target.

In Practice: Model > Map

1. The Target Model is HACPM_Financial.

2. The Name lets you give this mapping a name so you can re-use it.

3. Type must be set to Data for Write-back.

4. The Source is the name of the model that contains the changes you want to write back to Structured Planning, Consolidation, and Reporting applications.

5. Transfer must be set to Leaf.

6. The Write Back Id is the name of the Data Load Rule that you created in “Maintenance > Data Load Rules .” The Data Load Rule name is case-sensitive.

7. Leave Access Token blank.

   

Source to Target Map Table

Here you must list essentially the opposite of the map of you created prior to data download. The three columns that were on the left will now be on the right, and vice versa. The best practice, however, is to be specific in your map which data items you want to write back using Fixed Member, not to write back all members in all dimensions.

In the example below, instead of writing back all members of Account, Company, Department, Product, and Project, the map specifies only those members which have changed and that you want written back to Structured Planning, Consolidation, and Reporting applications. This way, you can control the flow of data between Structured Planning, Consolidation, and Reporting applications and Dynamic Planning.

Remember that HACPM_Financial has two dimensions, Intercompany and Reporting, that were filtered out prior to data download, and you need to specify the member that data will be written back to. The member specified must be a leaf member. In the example above, Intercompany: Default and Reporting: G/L Data (CC) are leaf members.

For all months in 2014, data for product D006341, account 4010, company 2100, department SLSCA, and Actuals will be written back. Here is a View that shows these member intersections.