1. Lifecycle Management Guide
  2. Planning and Lifecycle Management
  3. Planning Migration Considerations

Planning Migration Considerations

  • Oracle Hyperion Enterprise Performance Management System Lifecycle Management migration to and from Oracle Hyperion Planning is a long-running operation.

  • Some Planning artifacts have dependencies; for example, forms have dimension dependencies. Instead of migrating only the dimension members required for a form, Lifecycle Management migrates the entire dimension. You must manually select any necessary dependencies. See Migrating Artifacts.

  • The source and destination applications must have exactly the same settings for Plan Type, Calendar, and Single- or Multi-currency.

  • If Planning does not exist in the target environment, Lifecycle Management creates an application shell.

  • Oracle Essbase must be in Oracle Hyperion Shared Services mode to use Lifecycle Management.

  • Essbase artifacts are displayed under the Planning application node, and the data artifact is displayed under the Essbase Data category.

  • For a first-time test-to-production migration, Oracle recommends migrating all the Planning-related artifacts under the Planning node.

  • Oracle recommends migrating Essbase data only for a first-time test-to-production migration, and not for any incremental migrations.

  • To export or import Planning data artifacts, Lifecycle Management must have a shared file system path.

  • To enable data migration across distributed environments, filesystem.artifact.path must be a shared path. The Lifecycle Management file system location must be accessible from all environments in the distributed setup.