Install and configure Shared Services and Planning and verify that they are running. See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
Ensure that users performing Lifecycle Management operations are assigned the LCM Administrator, Planning Administrator, and Application Creator roles. See the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.
Ensure read access permissions are assigned to the LCM Administrator for task lists. See the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.
Determine the migration scenario that best fits your requirements. See Migration Scenarios.
Before migrating a Planning application, migrate the Shared Services Native Directory artifacts (users, groups, and provisioning). See Migrating Native Directory (Security). For a listing of Shared Services Native Directory artifacts, see Shared Services and Lifecycle Management.
Note: | To use Lifecycle Management for Planning or Essbase, Essbase must use Shared Services Native Directory and not a legacy security mode. |
Planning Classic application migrations—Before a destination application can be selected using the Migration Wizard, the application must exist or a shell application needs to be created in Planning.
Planning Performance Management Architect application migrations—Before migrating non-dimensional artifacts, Performance Management Architect dimensions must be migrated first and 'deployed after import'. For a listing of Performance Management Architect artifacts, see Performance Management Architect and Lifecycle Management.
The following application-level Calendar properties must match in both the source and destination applications:
Start year
Base time period (for example, 12 months, Quarters, and Custom)
Start month
The Period Dimension members must match in both the source and destination applications. For example, if the Period dimension in the source has a “Quarter 1” member, a “Quarter 1 member must exist in the destination.
Source and destination plan types must match (for example, if the source application has a plan type called Plan1, a Plan1 plan type must exist and in the destination application).
Source and destination plan types must be assigned in the same order (for example, if the source application has Plan1 and Plan2, Plan1 and Plan2 plan types must appear in the same order in the destination application).
If the source has a “Single Currency” application type, then the destination application should be of the same type