Oracle Hyperion HFM 11.2.x Importing applications

Importing Applications

You can import an application across databases or across EPM systems using homogeneous databases, however both EPM systems must use either Oracle Database or SQL Server. Source applications can originate from prior releases as far back as 11.1.2.4, however to upgrade older applications, you must run the Financial Management Upgrade Application task in EPM System Configurator from one Financial Management server. To import an application, you must have the Application Administrator role and be provisioned in Shared Services for the Financial Management Application Creator role.

You can import an application to the same environment and rename it, or you can register the new application in a different project and cluster.

You can import data for all years and scenarios, or select specific years and scenarios.

By default, the process duplicates the application profile information, metadata, and security information. You can also select to import the task and data audit information from the source application to the destination application.

Prerequisites for Importing Applications

These steps are required before you import applications:

• You must create a data communication link between the source and destination databases.

• If you are using Oracle databases, you must create a Database Link.

• If you are using SQL Server databases, you must create a Linked Server.

• You must make sure that the HFM database has the rights to create a Database Link or Linked Server.

• You must grant a one-time explicit DB privilege for database users configured in the Database Link or Linked Server rather than provisioning the users through roles.

To import an application:

1. Log on to the destination EPM system.
2. Select Navigate, then Administer, and then Consolidation Administration.
3. Select Administration, and then Import Applications.
4. Select Database Link if you are importing between Oracle databases, or select Linked Server if you are importing between SQL Server databases.

   When you select Database Link or Linked Server, the source applications are listed.

5. From the application list, select the source application.
6. Specify the Destination Application Name and Destination Application Description.

   The source application is imported with this name and description.

7. For Cluster, select the cluster the application should be registered on.
8. For User Management Project, select the project the application should be registered on.
9. Optional: Select the Import Audit Tables option to import the Data Audit and Task Audit tables from the source to the destination application.
10. Optional: Select the Import Data Tables option to import the data tables from the source to the destination application.

    If you select Import Data Tables, you may also specify the Scenario and Year filters.

11. Optional: Select the Purge Source Data option to purge the source data tables after copying to the target application.
12. Click Import.

When you start the import process, the system displays a warning that the operation is data intensive and asks if you want to continue.

It then displays the Admin Tasks page, where you can monitor the progress of the Import Application task.

After the system successfully imports the source application, it registers the newly created application to the cluster and project that you specified, and you can open the new application.