Dynamic Planning Converting a Master Model into a Direct Access to PCR Model
  • 4 Minutes to read
  • Dark
    Light
  • PDF

Dynamic Planning Converting a Master Model into a Direct Access to PCR Model

  • Dark
    Light
  • PDF

Article summary

Overview

Power users can convert an existing Master model into a Direct Access to PCR model using Backup and Restore. If the existing Master model was set up with the traditional integration method of connecting to the financial reporting area of PCR, it is possible to switch it over to the newer Direct Access integration method, which has less maintenance. This is accomplished by backing up the Master model with no data and then Restoring it as a Direct Access model.

This functionality is available for all customers.

Note:
The Restore As, Direct Access to PCR option is available only in Spotlight, Model Manager (web).

The traditional method of integration is described here: Dynamic Planning: Integration Admin Guide.

The Direct Access method of integration is described here: Dynamic Planning: Using Direct Access to PCR Financial Reporting.

Advantages and Disadvantages of Converting

Using Direct Access to PCR has several benefits:

  • No need to manage the data and metadata synchronization between PCR and Dynamic Planning. It happens automatically.

  • No need to run calculations to move data and metadata.

  • Instant access to PCR data and metadata in Dynamic Planning.

  • The data and metadata reside and are maintained in only one place within PCR.

Using Direct Access to PCR also has some limitations:

  • You cannot write back data from within Dynamic Planning.

  • Views and reports cannot use Save Data or Breakback options.

Pre-Requisites to Converting to a Direct Access to PCR Model

Before a Master model can be converted to a Direct Access to PCR (DAP) model, it must meet the following criteria:

  1. All of the data and metadata in the Master model must have been sourced from PCR. In the map that created the Master model, the Source model must be HACPM_Financial.

  2. The Master model should have been designed for reporting purposes only (no saving data and no write back to PCR). If there are any views or reports for the Master model, if they had Enable Save, this functionality will not work once the model is converted to a DAP model. It is recommended to turn off Enable Save on views and reports before the conversion.

  3. In the map that was used to create the Master model, lookups cannot be used.

  4. All the dimensions in the Master model should be sourced from HACPM_Financial. The Master model cannot have dimensions that are not found in HACPM_Financial (the map must not contain target dimension filters).

  5. Dimension names must match those in HACPM_Financial.

  6. The Master model cannot have a BudgetEntity dimension.

  7. The Master model should not have dimensions mapped to HACPM_Financial attributes. While we support the notion of creating attributes as dimensions when sourcing the data from PCR, if the Master model uses this type of mapping, then it cannot be converted into a Direct Access to PCR model.

Basic Method to Convert a Master Model to a Direct Access to PCR Model

The basic method to convert a Master model into a Direct Access model is as follows. Always test the process first in a sandbox or staging environment.

  1. Login to Spotlight (web).

  2. Backup the existing Master model, with no data.

  3. Delete or rename the existing Master model.

  4. Use Restore As to restore the model with the original name and set the flag for Direct Access to PCR.

Detailed Steps to Convert a Master Model to a Direct Access to PCR Model

  1. Refresh the application into ModelSBX (customer sandbox) or ModelSTG (staging).

  2. Select the Master model to convert to a DAP model.

  3. If the Master model has a map with type Metadata or Both, save this map again to validate it. Sometimes, such maps reference deleted dimension members and clicking Save will point out the problems.

  4. Verify that the Master model can be converted into a DAP model. See the Pre-Requisites above.

  5. Backup the Master model with no data. This creates a local ZIP file.

    Note:
    It is not a bad idea to backup the Master model with leaf-level data as well, so you have an archive of your previous implementation.

    ModelingImagesDataIntegration-CoreFunctionalSpecDAPBackup.png

  6. Clear and delete the original Master model.

  7. Using Model Manager on the Web, click to Restore a model, locate the ZIP file, and check the box to Restore as a DAP model. Ensure the Restore As name has the same name as the original Master model; otherwise, Excel Reports will not work.

    image1492.png

    ModelingImagesDataIntegration-CoreFunctionalSpecDAPRestore2.png

  8. Run the calculation on the restored model to refresh the metadata and download alternate hierarchies, attributes, and attribute hierarchies. After this step, the model will be generated and locked.

    ModelingImagesDataIntegration-CoreFunctionalSpecDAPRestore3.png

  9. Validate views, reports, and Excel Reports for the restored model.

  10. Repeat steps 2 through 9 for other models.

    If the restored models pass validation, repeat this process in your production environment.

Details for Power Users

  • When you Restore a Master model as a DAP model, only one map is retained: the one of type Metadata or Both. All other maps are deleted. The map with type Metadata or Both will be converted into a map with type Metadata. If there is no existing map with type Metadata or Both, a new map with type Metadata will be created by default; it will specify to download All Members for all dimensions.

  • When you Restore a Master model as a DAP model, all scopes, formulas, and calculations previously associated with the Master model are deleted. One calculation is created; it is the standard one created with all DAP models, containing five steps to refresh the model. See Hierarchy Updates.

  • All existing attributes from the Master model will be deleted. Attributes and attribute hierarchies mapped to the financial cube in PCR will be downloaded. Attributes mapped to a dimension are not supported because, in this case, the Master model would then have a dimension not found in HACPM_Financial. The Master model should not have dimensions mapped to HACPM_Financial attributes.


Was this article helpful?