Migrating to Extended Dimensionality and Enterprise Cloud Service

When you create a new Financial Consolidation and Close application, it is enabled with Extended Dimensionality, which is the ability to add additional Custom dimensions using an Essbase version that supports Hybrid cubes. In addition to the system predefined dimensions, you can create a maximum of four Custom dimensions based on your application needs. If your application is enabled with the Multi-GAAP reporting option, you can create three Custom dimensions.

If you are using a Legacy Non-Hybrid application that only allows two Custom dimensions:

You can migrate the application to Hybrid using the Enable Hybrid Mode Application option.
You can also migrate it to the Enterprise Cloud Service.

Note: Be sure to follow the supported migration paths. See "What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service?" in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

To use this migration procedure, you should have one pod with a Legacy Cloud Service and another pod with an Enterprise Cloud Service.

To enable this option, follow these steps:

On the Legacy pod, using the Migration process, create a full backup snapshot of the application.
On the Legacy pod, using EPM Automate, execute the recreate command, setting the value of the EssbaseChange parameter to Upgrade.
```
epmautomate recreate -f EssbaseChange=Upgrade
```
This will upgrade the Essbase version and will also delete the application. See "EPM Automate Commands" in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.
On the Legacy pod, import the application from the backup.
After you complete these steps, the Essbase version will be upgraded and the Enable Hybrid Mode Application option will be available.
On the Home page, click Application, select Overview, and from the Actions menu drop-down, select Enable Hybrid Mode Application.
Before the migration task runs, the system displays a warning that this action cannot be undone and a validation screen showing a summary of changes. Before launching the migration, click the Summary/Download link to view the changes. Note the insertion rules and on-demand calculations that will be affected. You must review these after the migration process.
Click Launch to start the migration task.
This task can take a long time to complete based on the amount of data that needs to be migrated. You can view the status and job details in the Jobs console.
Make sure that the migration task completed successfully. If the task fails for some reason, you can re-run the task from the Application Overview screen.
After the application has been migrated, export the application from the Legacy pod and import it into the Enterprise pod.

When you run the Enable Hybrid Mode Application option, the migration process results in the following changes in metadata:

The DataStorage property for seeded Movement, Intercompany, and Multi-GAAP top members changes to DynamicCalc.
In the View Dimension, QTD, HYTD, YTD change to Stored members and new members QTD_Rule, HYTD_Rule, YTD_Rule are seeded. In a custom calculation such as an Insertion Rule (Configurable Calculation rule) or an On-Demand rule, references to FCCS_YTD are converted to FCCS_YTD_RULE, FCCS_QTD is converted to FCCS_QTD_RULE, and FCCS_HYTD is converted to FCCS_HYTD_RULE. If you have created forms that reference FCCS_QTD, FCCS_YTD or FCCS_HYTD, you will need to modify the forms to reference the corresponding _RULE members.
There is a change in Performance order for Dimensions.
SolveOrder: Period, View, Movement, DataSource, Consolidation (only when Ownership Management is disabled) dimension members are seeded with default SolveOrders defined.
For Multi-GAAP (if it exists) and Custom Dimensions (for example, Product): The DataStorage properties for all the user-defined upper-level members are changed to DynamicCalc.