About Essbase in EPM Cloud

Essbase Version that Supports Hybrid Cubes

EPM Enterprise Cloud Service and EPM Standard Cloud Service subscriptions are deployed with an Essbase version that supports Hybrid Block Storage Option (BSO) cubes.

To make parent members of sparse and dense dimension dynamic, the Hybrid BSO cubes support some Aggregate Storage Option (ASO) capabilities in addition to BSO capabilities. For example, all cubes can have dynamic aggregations for calculations. Hybrid cubes provide many benefits including smaller database and application size, better cube refresh performance, faster import and export of data, improved performance of business rules, and faster daily maintenance of the business process. To ensure optimal performance, warnings and error messages are displayed during cube refresh if the business process does not conform to best practices for the following parameters:

  • Block size

  • Number of blocks

  • Number of dense dimensions

  • Maximum number of child members under any dynamic parent

  • Maximum number of child members under any store parent

  • Parents with one child member for level 1 and above of dimensions

  • Level 1 and above not set to dynamic calculation and label only in dense dimensions

  • Usage of dynamic cross-references

These parameters of enabled modules are enforced to ensure that best practices are followed:

  • Number of new rules that can be added to a module

  • Number of rules that can be modified

  • Number of new forms added to a module

  • Number of forms that can be modified

If you have EPM Enterprise Cloud Service and EPM Standard Cloud Service, Financial Consolidation and Close, by default, Custom Planning, Planning Modules other than Workforce, and Free Form applications are created to use Hybrid BSO cubes in place of BSO cubes. However, if you create a Free Form application by importing a snapshot from an Essbase deployment that does not support Hybrid cubes, the Free Form application will use standard BSO cube.

Note:

Oracle Strategic Workforce Planning Cloud does not use Hybrid cubes.

Essbase Version that Does not Support Hybrid Cubes

Legacy Oracle Enterprise Performance Management Cloud subscriptions that were activated before the introduction of EPM Enterprise Cloud Service and EPM Standard Cloud Service are deployed with an Essbase version that does not support Hybrid cubes. These include legacy environments other than the following that were upgraded based on specific service requests:

Note:

The default deployments of these services do not support Hybrid cubes. You can, however, use a self-service process to upgrade Essbase to support Hybrid BSO cubes.

  • Oracle Enterprise Planning and Budgeting Cloud subscriptions

  • Oracle Financial Consolidation and Close Cloud subscriptions

  • Planning and Budgeting Cloud Service Plus One option license

    If you purchased EPM Cloud before June 4, 2019, you may have a license (Planning and Budgeting Cloud Service Plus One Business Process option) that allowed you to deploy Enterprise Planning and Budgeting Cloud business processes (Financials, Strategic Modeling, Workforce, Projects, or Capital) in a Planning and Budgeting Cloud Service environment.

Can I Upgrade to the Hybrid-enabled Essbase?

If your legacy subscription to the following is not deployed to use Hybrid-enabled Essbase, you can upgrade your Essbase deployment.

  • Oracle Enterprise Planning and Budgeting Cloud subscriptions

  • Oracle Financial Consolidation and Close Cloud subscriptions

  • Planning and Budgeting Cloud Service Plus One option license

Upgrading the Essbase version is a self-service operation using the recreate EPM Automate command. See EPM Automate Commands in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

What are the Implications if I Upgrade to Hybrid-enabled Essbase?

The following factors must be considered before upgrading to Hybrid-enabled Essbase:
  • You must manually recreate the application or import an application snapshot after the environment is upgraded because the upgrade process deletes the existing application.

    If you are importing an application snapshot, follow the steps outlined in "Steps for Converting a Legacy Oracle Enterprise Planning and Budgeting Cloud or Planning and Budgeting Cloud Plus One Application to Use Hybrid BSO Cubes" section below.

  • Upgrading your environments to use Hybrid-enabled Essbase does not mean that your applications will automatically use Hybrid cubes. You must enable Hybrid cubes in the application after the upgrade.

    To enable Hybrid cubes:

    1. From the Home page, select Application and then Overview.
    2. From Actions, select Enable Hybrid Mode.

      EPM Cloud validates your application to ensure that it meets the requirements for applications that use Hybrid cubes. These best practices are listed at the beginning of this section.

    3. Modify your application based on the validation errors and warnings. Errors must be resolved before a successful database refresh can occur. On encountering an error, the database refresh process stops and places the application in maintenance mode. Warnings must be reviewed to identify and correct potential issues.
  • Planning applications that use Hybrid-enabled Essbase do not permit incremental data loading using Migration. As a result, you cannot use the daily maintenance snapshot for incremental import of data; you must import the full snapshot to load data.

  • Snapshots of applications that use Hybrid-enabled Essbase, regardless of whether the application has been enabled to use Hybrid cubes, can be migrated only to other Hybrid-enabled Essbase environments.

Steps for Converting a Legacy Oracle Enterprise Planning and Budgeting Cloud or Planning and Budgeting Cloud Plus One Application to Use Hybrid BSO Cubes

If you have a legacy Oracle Enterprise Planning and Budgeting Cloud subscription or a Planning and Budgeting Cloud Service Plus One option license, you can convert your Planning application to use Hybrid BSO cubes. You should first convert the application in the Test environment and validate that it works properly before attempting to convert your production application.

To convert a legacy Planning application to use Hybrid BSO cubes:

  1. Convert the Planning application in your test environment to a Planning Modules application.

    See "Converting a Standard or Reporting Application to an Enterprise Application" in Administering Planning Modules.

  2. Refresh the database. Ensure that the process runs successfully without errors. See Creating and Refreshing Application Databases in Administering Planning.

  3. Using Migration, create a full backup snapshot of the application in the Test environment. If you did not modify data and artifacts after the last maintenance of the environment, you can use Artifact Snapshot as a full backup of the environment.

    Download the backup to a local computer as a precautionary measure.

  4. Using EPM Automate, upgrade your environment to use Hybrid-enabled Essbase.

    See "EPM Automate Commands" in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

    • Start an EPM Automate session and log into an environment:

      epmautomate login serviceAdmin Example_pwd https://testexample. oraclecloud.com ExampleDomain

    • Execute the recreate command setting the value of the optional EssbaseChange parameter to Upgrade.

      epmautomate recreate -f EssbaseChange=Upgrade

  5. Optional: Generally, the backup snapshot you created in Step 3 is available in the environment. If it is not present, using the uploadFile EPM Automate command or Migration upload the backup snapshot to the environment.

  6. Create the application by Importing the backup snapshot.

  7. Enable Hybrid.

    1. From the Home page, select Application and then Overview.
    2. From Actions, select Enable Hybrid Mode.

      EPM Cloud validates your application to ensure that it meets the requirements for applications that use Hybrid cubes. These best practices are listed at the beginning of this section.

    3. Modify your application based on the validation errors and warnings. Errors must be resolved before a successful database refresh can occur. On encountering an error, the database refresh process stops and places the application into maintenance mode. Warnings must be reviewed to identify and correct potential issues.
    4. Optional: Redesign and streamline your application to make best use of Hybrid BSO capabilities. Steps to streamline your application include making parent members in some sparse dimensions dynamic and removing intermediate rollups from rules, where appropriate. Additionally, you may need to modify the existing member formula syntax to work as expected with Hybrid-Enabled Essbase. Test the application to determine the right combination of sparse dimensions with dynamic parent members that work for your specific application.
  8. Test your application to verify that it works as designed.
  9. Repeat the preceding steps to convert the application in the Production environment.

Enabling Hybrid-Enabled Essbase for Legacy Oracle Financial Consolidation and Close Cloud Environments

For legacy Oracle Financial Consolidation and Close Cloud environments, Hybrid-enabled Essbase is needed only if you require the Extended Dimensionality option which supports more than two custom dimensions in your application. You should first enable Hybrid-Enabled Essbase in the Test environment validate that it works properly before attempting to convert your production environment.

To upgrade to Hybrid-Enabled Essbase:

  1. Using Migration, create a full backup snapshot of the application in the Test environment. If you did not modify data and artifacts after the last maintenance of the environment, you can use Artifact Snapshot as a full backup of the environment.

    Download the backup to a local computer as a precautionary measure.

  2. Using EPM Automate, upgrade your environment to use Hybrid-enabled Essbase.

    See "EPM Automate Commands" in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

    • Start an EPM Automate session and log into an environment:

      epmautomate login serviceAdmin Example_pwd https://testexample. oraclecloud.com ExampleDomain

    • Execute the recreate command setting the value of the optional EssbaseChange parameter to Upgrade.

      epmautomate recreate -f EssbaseChange=Upgrade

  3. Optional: Generally, the backup snapshot you created in Step 1 is available in the environment. If it is not present, using the uploadFile EPM Automate command or Migration, upload the backup snapshot (see Step 1) to the environment.

  4. Create the application by importing the snapshot.

    See Importing Artifacts and Application from a Snapshot in Administering Migration for Oracle Enterprise Performance Management Cloud for detailed instructions.
  5. Enable the Extended Dimensionality option.

How Do I Know if an Application has Hybrid BSO Cubes Enabled?

The Overview tab of your application indicates whether it is set up to use Hybrid cubes. You can open this tab from the Home page by selecting Application and then Overview.

As a general guideline, Financial Consolidation and Close, Custom Planning, Planning Modules, and Free Form applications that you create in EPM Enterprise Cloud Service use Hybrid BSO cubes. Additionally, Financial Consolidation and Close and Planning Modules applications you create in EPM Standard Cloud Service, by default, use Hybrid BSO cubes. Some cubes in these applications may still use ASO cubes, as necessary or as delivered content by Oracle.
Application Overview indicating that Hybrid cubes are enabled