Application Migrations with Cross-Product Artifact Dependencies

To ensure a successful migration, Oracle Hyperion Enterprise Performance Management System Lifecycle Management enforces a specific order when importing artifacts, but only at the product level. Lifecycle Management does not automatically order the import of artifacts across multiple products (at the artifact level). For example, a Oracle Hyperion Financial Management application might consist of dimensions and business rules, user provisioning from Oracle Hyperion Shared Services, and reports from Oracle Hyperion Financial Reporting.

When using Lifecycle Management to migrate artifacts from multiple products, you must ensure that the cross-product dependent artifacts are present at the destination before importing the product artifacts. This is especially important when performing a first-time Lifecycle Management migration.

The following documents provide step-by-step instructions on how to perform first-time Lifecycle Management migrations:

  • Oracle Enterprise Performance Management System Migrating Oracle Hyperion Planning Applications

  • Oracle Enterprise Performance Management System Migrating Oracle Hyperion Profitability and Cost Management Applications

  • Oracle Enterprise Performance Management System Migrating Oracle Hyperion Financial Management Applications

See the documentation library at http://docs.oracle.com/cd/E57185_01/index.htm.