Dynamic Planning Writing Data from Dynamic Planning Back to Planful Structured Planning, Consolidation, and Reporting Applications

To enable write back capabilities from Dynamic Planning back into Planful Structured Planning, Consolidation, and Reporting applications, perform the following:

• Set up a Data Load Rule in Planful Structured Planning, Consolidation, and Reporting applications to load the data.

• Use this Data Load Rule in Planful Structured Planning, Consolidation, and Reporting applications in conjunction with a Map in Dynamic Planning to facilitate the movement of data.

• Specify settings required to enable Web Services in both Planful Structured Planning, Consolidation, and Reporting applications and Dynamic Planning.

The following sample configuration discusses the settings required to enable Web Services, setting up a Data Load Rule, Financial Model Setup, and a sample Map in Dynamic Planning.

Web Services Configuration

In Planful Structured Planning, Consolidation, and Reporting applications, access the Configuration Tasks page to enable the Web Services API, if it is not already enabled.

• Navigate to Maintenance, Configuration Tasks, Web Service Access.

• Select the Enable radio button for API.

• Copy the State free authentication URL for later reference. For example, https://demo06.planful.com/PlanfulAPI/PlanfulAPI_StateFree.asmx

New Data Load Rule

Create a new Data Load Rule to load the data from Dynamic Planning to Planful Structured Planning, Consolidation, and Reporting applications.

1. Navigate to Maintenance, Data Integration, Data Load Rules.

2. Click the New Data Load Rule tab.

3. Enter a rule name.

4. For Load Type, select Web Services.

5. For Load Item, select Data.

6. For Load Sub Item, select GL Data.

7. Click Next to access the Select Sample Input File page.

8. Enter the number of columns calculated as the number of segments in your Structured Planning, Consolidation, or Reporting application (not your model) plus three (Fiscal Year, Fiscal Month, and Amount).

9. Click Next to access the Define Overall Rule Settings page.

10. Select the following parameters:

    • Data Type = MTD / YTD (depending upon data being loaded)

    • Calculate Trial Balance = No

    • Scenario = {desired scenario}

    • Frequency = Month

    • Time Mapping = Down Rows

    • Automatic Cube Refresh = Yes

    • Change the rest of “Parameters” as needed.

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

11. Click Next to access the Manipulate Input File page. Nothing is required on this page.

12. Click Next again to access the Define Data Mappings page.

13. Map segments to the first columns in the alphabetical order. Map the last three columns as shown below (Fiscal Year, Fiscal Month, and Amount).

    

14. Click Finish.

Planful Financial Model Setup

Once you have configured your Web Services API and Data Load Rule in Planful Structured Planning, Consolidation, or Reporting applications, you will need to update some settings in Dynamic Planning to ensure your Planful Structured Planning, Consolidation, or Reporting applications Financial model is set up properly for write back. You will configure your CPM Settings as well as run a Metadata Download in Model Design.

CPM Setting Configuration

Add Horizon and SOAP Uri/Login/Password/Tenant details for use during write back.

1. In Dynamic Planning, select the Manage task and the Application Administration, Applications Settings subtask.

2. Enter the following information:

   1. Horizon Uri = https://demo06.planful.com (API server for each environment will be different, validate with Support to ensure proper Uri if you are encountering issues)

   2. Horizon Username = your user name for logging into HACPM Structured Planning, Consolidation, or Reporting applications

      • Example – jdoe@planful.com

   3. Horizon Password = your password for logging into HACPM Structured Planning, Consolidation, or Reporting applications

   4. Horizon Tenant Code = tenant code for your application that you are writing back to

      • Example = DWMAINKK6

   5. SOAP Uri = paste the State free authentication URL from Web Services Configuration section above

      • Example - https://demoha.planful.com/PlanfulAPI/PlanfulAPI_StateFree.asmx

   6. SOAP Username = your user name for logging into HACPM Structured Planning, Consolidation, or Reporting applications

      • Example = jdoe@planful.com

   7. SOAP Password = password created during Web Services Configuration

   8. Value Block Size = 1000 (there is no need to change this value)

3. Click Save.

Metadata Download

Download metadata from the Structured Planning, Consolidation, or Reporting application to Dynamic Planning. Perform the following actions:

1. In Dynamic Planning, select the Manage task and the Metadata Download subtask.

2. Click Run.

3. Once the download completes select the Model task and the Dimension subtask to validate the dimensionality.

   • Select a dimension that has been downloaded from Planful Structured Planning, Consolidation, or Reporting applications (such as Account) and validate the members are displayed as expected.

   • Any time you change metadata in Planful Structured Planning, Consolidation, or Reporting applications, execute the Metadata Download action to ensure that Dynamic Planning is in synch.

Write Back Process in Dynamic Planning

There are two steps that need to be performed to complete the write back process.

1. Create a valid Map from Dynamic Planning to Planful Structured Planning, Consolidation, or Reporting applications.

2. Create a Calculation to execute the Map.

Valid Map

Create a map from your source model to the Structured Planning, Consolidation, or Reporting application's Financial model to complete the write back process.

1. In Dynamic Planning, select the Model task and the Map subtask.

2. Configure the map with the following properties:

   • Target Model = HACPM_Financial

   • Type = Data

   • Source Model = <model where data is originating from>

   • Transfer = Leaf or All

   • Write Back Id = name of Data Load Rule created in Planful PCR Applications

3. Click Save.

Best Practices

• Ensure that the metadata for HACPM_Financial has been downloaded from your Planful Structured Planning, Consolidation, or Reporting applications so that the mapping is valid (for example, all members in the source model exist in the target model).

• Map all segments identified in your Planful Structured Planning, Consolidation, or Reporting applications.

• Ensure that the members for which you are mapping are consistent between HACPM_Financial and your Source model. For example, if you have 2 members (Office Supplies and Rent) under a parent called “Expenses” you will need to have the same two members in both the Source and the Target. See sample map below.Sample map definition in Dynamic Planning. Write Back Id is the name of the Data Load Rule defined in Structured Planning, Consolidation, or Reporting applications (such as Sample Rule).

  

Support for Translations in Write Back from Dynamic Planning to PCR

You can create a Model with Source Segments, map them to the Financial Model and write back to PCR (Structured Planning, Consolidation, Reporting) using a Translations Data Load Rule. The write back map allows you to include Source dimensions as shown in the following example.

• Source Dimension must be a dimension from the source model.

• Attributes are not supported.

• You must select AllMembers, MemberAndBelow, LeafMembers or FixedMember as the value Source Filter.

• The values for Target Dimension, Target Filter, and Target Value must be None.

Additionally, it is not required to map all the PCR dimensions in the Target Dimension column. You can skip them by selecting the No Translation for Unmapped Target Segment s check box in the Data Load Rule Write Back ID In this example (image above) the Data Load Rule type is Translations and Account and subAccount are the source dimensions in the MasterModelForWriteback for which the Translations are setup within PCR (shown in the image below). You can map Source dimensions using Translation Setup.

For more information on DLR and Translation Setup, refer to the Data Integration Admin Guide and Translations Setup.

The image below displays the Transaction lines for the segments. In this example, two Source Dimensions are merged and mapped to the target; Account and subAccount Source Dimensions are mapped to Account. When you load data for the 28 DYN Income account Source dimension and 28 DYNIncomeSubAcc subAccount for the WritebackDLRTranslations model and running write back, the Account DNY_Account1 in PCR gets updated automatically.

The following scenarios provide a few examples where you can use Translations:

• Mapping two source Segments to one Target Segment - In the above example, the Account and subAccount source segment are mapped to Account.

• Mapping one Source Segment to one Target Segment - The subAccount Source segment is mapped to Account as shown in the image below. In the second image, the transaction lines for the segments are shown.

  

  

• Mapping two Source Segments to two Target Segments - The Account and subAccount source segments are mapped to Account and Company as shown in the image below. In the second image, the transaction lines for the segments are shown.

  

  

• Mapping one Source Segment to two Target Segment - The subAccount source segment is mapped to two dimensions as shown in the image below. In the second image, the transaction lines for the segments are shown.

  

  

Translation Requirements:

• Source Segment names must match dimension names in the source Writeback Model.

• Source Segment names must be unique across all Translations used by DLR.

• “Source Column X” must be unique across all Translations used by DLR.

Consistency between DLR and Write Back Map:

• The Measure in the map must be identical to the DLR Data Type.

Calculation

Once you have created the map for the write back operation that includes the Write Back Id for the Data Load Rule, you will need to add this map to a calculation. Perform the following steps:

1. In Dynamic Planning, select the Model task and the Calculation subtask.

2. Create a new Calculation for the model you are writing back data from (for example, Finance model).

3. Add the map to the calculation.

   • Type = Map

   • Name = Write back map name (not the write back Id but rather the map created in the step prior)

4. Save the calculation.

5. Run the calculation. Note that you CANNOT add this calculation on save for either a View or Report at this time.