Using Lifecycle Management to Migrate Profitability and Cost Management Files to Another Environment

To migrate a complete Profitability and Cost Management application from one environment to another, you must perform three separate migrations to reconstruct the entire application:

Caution!

Managing Profitability and Cost Management application artifacts through Oracle Hyperion Enterprise Performance Management System Lifecycle Management is only supported within the same version of the product.

The following procedure provides the general steps required to migrate from one environment to another. For detailed instructions on performing the migration, see the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide.

  To migrate Profitability and Cost Management applications to another environment:

  1. Back up the destination environment before beginning the migration. See the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.

  2. From EPM Workspace, select Navigation, then Administer, and then Shared Services Console.

  3. Create the export migration definition for the Performance Management Architect metadata as follows:

    1. From Hyperion Shared Services Console, select Application Groups, then Foundation, and then EPM Architect.

    2. From the Artifact list, expand Application Metadata, then expand Profitability Applications, and then select the specific application to be exported.

      If required, expand the application and select one or more of the following elements for export:

      • Import Profile

      • Local Dimensions

      • Profitability Settings

    3. Click Define Migration, and then complete the Migration wizard steps, as outlined in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide, and using the following information:

      • Source is Foundation/EPM Architect

      • Destination is the File System

      Tip:

      Enter a folder name that identifies that the folder contains the Performance Management Architect metadata, for example: Bike_epma.

    4. Optional: When the migration is complete, on the Shared Services Console, under File System check for the newly created Performance Management Architect migration folder.

  4. Create the export migration definition for the Profitability and Cost Management metadata as follows:

    1. From Hyperion Shared Services Console, select Application Groups, then the Default Application Group (or other Shared Services project) that contains the Profitability projects, and then the Profitability and Cost Management model. For example, Bike.

    2. From the Artifact List, select the artifacts that you want to migrate, and then click Define Migration. For example, you may select individual artifacts, such as Assignment Rules or Drivers, or you can select all artifacts.

    3. Complete the Migration wizard steps, as outlined in Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide, using the following information:

      • Source is HPM/Model Name

      • Destination is the File System

      Tip:

      Enter a folder name that identifies that the folder contains the Profitability and Cost Management metadata, for example: Bike_hpm.

  5. Navigate to the Windows File System to zip the migration files:

    1. From the Windows File System, navigate to the Performance Management Architect migration folder. By default, the migration folder is in EPM_ORACLE_INSTANCE/import_export/user@Native Directory.

    2. Select the Performance Management Architect migration folder (for example, Bike_epma), and zip the complete folder structure.

      Select the Performance Management Architect migration folder, including all files, and zip the complete folder structure.
    3. From the Windows File System, navigate to the Performance Management Architect migration folder. By default, the migration folder is located at EPM_ORACLE_INSTANCE/import_export/user@Native Directory.

    4. Select the Profitability and Cost Management migration folder (for example, Bike_hpm), and ensure that all files within the migration folder are included in the ZIP file.

      Select the Profitability and Cost Management migration folder, including all files, and zip the complete folder structure.
  6. E-mail the Performance Management Architect and Profitability and Cost Management ZIP files to the appropriate party.

  7. On the destination server, unzip the Performance Management Architect ZIP file to the same file structure (for example, unzip the file to EPM_ORACLE_INSTANCE/import_export/user@Native Directory) as follows:.

    1. From Hyperion Shared Services Console, select File System, and then the EPMA Migration file. For example, Bike_epma.

    2. From the Artifact List, expand Application Metadata, then check Profitability Applications, and then click Define Migration.

    3. Complete the Migration wizard steps, as outlined in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide, using the following information:

      • Source is File System

      • Destination is the Foundation/EPM Architect

  8. From EPM Workspace, select Navigate, then Administer, then Application Library, and then select Deploy to deploy the Profitability and Cost Management application. For complete instructions, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide.

    At this point, this is just a shell application. It does not contain any model structure or data.

  9. On the destination server, unzip the Profitability and Cost Management ZIP file to the same file structure (for example, unzip the file to EPM_ORACLE_INSTANCE/import_export/user@Native Directory) as follows:

    1. From Hyperion Shared Services Console, select File System, and then the Profitability and Cost Management Migration file. For example, Bike_hpm.

    2. From the Artifact List, select the artifacts to be imported, and then click Define Migration.

    3. Complete the Migration wizard steps, as outlined in the Oracle Hyperion Enterprise Performance Management System Lifecycle Management Guide, using the following information:

      • Source is File System

      • Destination is the HPM/Model Name

  10. Within Profitability and Cost Management, under Task Areas, select Manage Model, then Model Summary, and the Model Level Preferences tab and then select the Essbase host in the imported environment.

  11. Within Profitability and Cost Management, under Task Areas, select Calculate, and then Manage Database to deploy the model to add the model data. For complete instructions, see the Oracle Hyperion Profitability and Cost Management Administrator’s Guide.

  12. Import model data from Essbase into the newly deployed model. See the Oracle Essbase Database Administrator's Guide.

    The model is now complete and available for calculation.