To ensure a successful migration, 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 Financial Management application might consist of dimensions and business rules from Performance Management Architect, user provisioning from Shared Services, and reports from 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 Oracle by Example (OBE) series provides step-by-step instructions on how to perform first-time Lifecycle Management migrations for these products:
Essbase 11.1.1 with Lifecycle Management 11.1.1
Financial Management 11.1.1 with Lifecycle Management 11.1.1
Planning 11.1.1 with Lifecycle Management 11.1.1
Reporting and Analysis 11.1.1 with Lifecycle Management 11.1.1
See http://www.oracle.com/technology/obe/hyp_ss/ssindex.htm.