Moving Financial Consolidation data from the production environment to another environment

This is a high-level procedure about how to move Financial Consolidation data from the production environment to another environment, for example, a test environment. For details about specific steps, see the related topics.

You can move Financial Consolidation data from the production to another environment for testing purposes or, for example, to develop or adjust content such as custom reports, dashboards, roles, and transport the content without data to the production environment.

Caution: 
Do not overwrite the production data with the data from a test or development environment. The production environment is the only source of real data.
Note: After you import all required data to the target environment, ensure that the Business Modeling database matches the OLAP database. Otherwise, inconsistencies can occur.
  1. In Business Modeling, export your business model.
    Only members of the Business Modeling Administrator role can export the business model.

    See "Exporting a model".

  2. If you created custom OLAP data roles, export them in EPM Administration.
    Note: Financial Consolidation provides many standard data roles, which are published with the data model.

    See "Exporting data roles".

  3. In EPM Administration, export the OLAP database.
    See "Exporting an OLAP database".
  4. In Financial Consolidation, export ownership data, including participation information, and journal data, including all periods, entities, and groups. If multiple versions are available, you must export journal data for each version.
    See "Exporting ownership change requests with or without participation information" and "Exporting journals".
    Note: Alternatively, create the backup copy of the BIFarmConsolidation SQL database, which stores the ownership and journal data.
  5. Optionally, in EPM Administration, export the applications that contain your custom reports and processes. Alternatively, export individual reports in Application Studio and custom processes in Application Engine Process Editor.
    See "Exporting an application", "Exporting, importing and printing", "Exporting a process package", and "Exporting processes to folder".
  6. In EPM Administration, depending on what type of integration you use, export the model from the Integration or Staging tables, or both.
    See "Exporting a model from Integration" and "Exporting a model from Staging".
  7. In Business Modeling, in the target environment, import the .bmexport file with your business model and publish the model.
    See "Importing and publishing a model".
  8. In EPM Administration, in the target environment, assign application roles to users.
    Assignments of application roles are environment-specific. Therefore, they cannot be transferred.

    See "Making assignments between users, groups, and application roles".

  9. If you have custom OLAP data roles, import them in EPM Administration in the target environment. Then, assign OLAP data roles to users.
    Assignments of data roles are environment-specific. Therefore, they cannot be transferred.

    See " Importing data roles" and "Making assignments between users, groups, and application roles".

    Note: Financial Consolidation standard data roles are published with the data model.
  10. In EPM Administration, in the target environment, import the OLAP database.
    See "Importing an OLAP database".
  11. Optionally, in EPM Administration in the target environment, install the applications that contain your custom reports and processes.
    Alternatively, import individual reports in Application Studio and custom processes in Application Engine Process Editor.

    See "Installing an application", "Exporting, importing and printing", "Importing a process package", and "Importing processes from folder".

  12. In EPM Administration, in the target environment, import the model from the Integration or Staging tables, or both, depending on what type of integration you use.
    See "Importing a model to Integration" and "Importing a model to Staging".
  13. In Financial Consolidation in the target environment, import ownership data, including participation information, and journal data, including all periods, entities, and groups. If multiple versions are available, you must import journal data for each version.
    See "Importing ownership change requests" and "Importing journals".
    Note: Alternatively, if you created the backup copy of the BIFarmConsolidation SQL database, restore the database.
  14. In Business Modeling, in the target environment, run the database alignment.
    See "Database alignment" and "Aligning the Financial Consolidation and journal databases".
  15. In Business Modeling, in the target environment, publish the model again.
    See "Importing and publishing a model".
Related topics
  • Exporting an application
  • Installing an application
  • Making assignments between users, groups, and roles
  • Moving an application to production
  • Exporting a model
  • Importing and publishing a model
  • Exporting data roles
  • Importing data roles
  • Exporting an OLAP database
  • Importing an OLAP database
  • Exporting ownership change requests with or without participation information
  • Importing ownership change requests
  • Exporting journals
  • Importing journals
  • Exporting, importing and printing
  • Exporting a process package
  • Importing a process package
  • Exporting processes to folder
  • Importing processes from folder
  • Exporting a model from Integration
  • Importing a model to Integration
  • Exporting a model from Staging
  • Importing a model to Staging
  • Database alignment
  • Aligning the Financial Consolidation and journal databases