1. Oracle Enterprise Performance Management Cloud Operations Guide
  2. Troubleshooting EPM Cloud Issues
  3. Diagnosing Consolidation Failures and Performance Issues in Financial Consolidation and Close
  4. Use the Dense Sparse Optimization Option

Use the Dense Sparse Optimization Option

All new Financial Consolidation and Close applications, by default, are created to use the Dense Sparse Optimization option that uses Period and Movement as the dense dimensions. Older applications used the Standard option of Account as the dense dimension.

Unless you have a valid business requirement to use the Standard option, migrate existing applications to use the Dense Sparse Optimization option to improve consolidation performance.

The Dense Sparse Optimization option is available only if your environment is on Hybrid-enabled Oracle Essbase. If your environment is not on hybrid-enabled Essbase, see these sources for more information:

  • About Essbase in EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators
  • recreate command in Working with EPM Automate for Oracle Enterprise Performance Management Cloud

To update existing applications to use the Dense Sparse Optimization option, use the migration utility, which is available from the Application Overview screen. When you create or migrate an application with Period and Movement as dense dimensions, Financial Consolidation and Close makes the required changes to seeded members and member formulas.

Prerequisites

Before converting an existing application to use the Dense Sparse Optimization option:

  • Ensure there are no metadata validation errors.
  • Ensure there are no pending metadata changes and that Refresh Database has run successfully.
  • Make a backup of the application.
  • Disable scheduled jobs and reschedule daily maintenance so that it does not interfere with the migration.

Migration Steps

  1. Sign in to Financial Consolidation and Close as a Service Administrator.
  2. On the Home page, click Application, and then Overview.
  3. From Actions, select Make Period and Movement Dense to launch the Migration wizard.
  4. Confirm that you already completed the pre-conversion actions, then click Next and follow the prompts in the Migration wizard.
  5. Wait for the migration process to finish, then log out of the application and log back in.

Post-Migration Steps

  1. Review all member formulas that you created, insertion points, and on demand rules to ensure that they are written following the best practices.
  2. Ensure that the solve order for all parent account members is set to 58. You must set the solve order of any new parent Account member to 58.
  3. Recreate Data Export jobs. Because Period and Movement are now dense dimensions, put either of them in the column instead of Account.
  4. Make these changes to saved metadata load files (csvs) so that they can be used to import metadata into the migrated application:
    • Account.csv: Set the solve order of all parent accounts to 58.
    • Movement.csv: Set all parent movements to Dynamic Calc. Remove the solve order for all members.
    • Data Source.csv: Remove solve order for all members.