Contents

Important Announcement

A Customer Connect session regarding this advisory was conducted on Thursday, December 4, 2025. Service Administrators, System Integrators, and Implementation Consultants participated in this interactive forum, where they had the opportunity to seek clarification, ask questions, and discuss concerns directly with the Oracle Fusion Cloud Enterprise Performance Management team. A recording of the Customer Connect session is now available for review.

Overview

Oracle regularly updates the technical components of Oracle Fusion Cloud Enterprise Performance Management and Oracle Fusion Cloud Enterprise Data Management to maintain a current and secure technology stack. As part of this process, Oracle Essbase—a key component used in Planning, FreeForm, Financial Consolidation and Close, Tax Reporting, Profitability and Cost Management, and Enterprise Profitability and Cost Management business processes—was upgraded to version 21c (21.7).

After thorough internal testing, many customers were upgraded to Essbase 21c with the October 2025 (25.10) update in both test and production environments. Following the successful rollout of 25.10, Oracle updated the remaining test environments to Essbase 21c in the 25.11 update. However, a few customers reported issues in their test environments related to calculation accuracy and system slowness. Although these problems were specific to customizations within certain customer applications and were only observed sporadically across different customers, Oracle has paused the deployment of 25.11 to production environments and the deployment of 25.12 and 26.01 to all environments.

This advisory addresses frequently asked questions about this decision and offers guidance for specific customer scenarios.

Note:

If you need assistance determining the best approach for your environments, please open a service request.

The Oracle Update Rollout Decision

What was the root cause for the 25.11 update being withheld from Production environments?

A few customers reported issues in their 25.11 test environments related to calculation accuracy and system slowness. These problems were specific to customizations within certain customer applications and were only observed sporadically across different customers.

Why did Oracle also decide to skip the 25.12 (December 2025) and 26.01 (January 2026) updates?

The year-end is a critical period for many customers’ business processes. Oracle deferred these updates to avoid any risk of disruption during this time, allowing additional time to fix reported issues and to validate future updates.

Based on issues reported so far, what areas of the applications would Oracle recommend customers test to ensure Essbase 21c works well?

The Oracle Essbase 21c upgrade has no impact on these business processes:

  • Narrative Reporting
  • Account Reconciliation
  • Enterprise Data Management

Oracle recommends customers investigate the following areas of their applications to ensure Oracle Essbase 21c does not have any cause for concern:

  • Overall Tests across Financial Consolidation and Close, Planning, Profitability and Cost Management, and Tax Reporting: Run all allocations, data loads, data exports, and reports and confirm that there are no regressions in results and no performance degradations.

  • Financial Consolidation and Close:

    Performance Test:

    Run Consolidate and Translate Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated - especially if your insertion points use the Essbase functions @CALCMODE and @EQUAL in Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL).

    1. Run On-Demand Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated. Especially test ODRs using @CALCMODE and @EQUAL Essbase functions in Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL).
    2. Data Retrieval: Test your ad-hoc grids, data forms, and reports in Essbase 21c. Retrievals should take a similar amount of time as it used to take in Essbase 11g.
    3. Data Integration: Test the same data integration exports using All Data mode and Replace Mode.
    4. Restructure Cube: This task in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when same cube was selected.

    Data Integrity Test:

    1. Ad-hoc Data Comparison: Consolidated data retrievals on ad-hoc grids with Essbase 21c (Sheet A) with Essbase 11g (Sheet B) must tie out. Sheet A - Sheet B = 0.
    2. Data Exports (Dynamic and Stored Sparse Data): Data Integration Export using All Data mode for Essbase 21c must tie with Essbase 11g.
    3. Custom Member Formula Tests: Ratios/Statistical Analysis must match between Essbase 21c and Essbase 11g with the same Solve Orders.

    Video Guides:

  • Planning: Open forms, run rules, confirm aggregated numbers, run reports and dashboards, and confirm consistent run times. Check member formula calculations for both BSO and ASO cubes to ensure consistency.

  • Profitability and Cost Management: Run all allocations after the Essbase 21c upgrade, confirm that there are no performance degradations, and ensure that data reconciles.

If we are interested in assisting with the assessment of Oracle’s planned resolutions, how can we participate or get involved in testing them?

If you previously reported issues related to Essbase 21c, you will receive an early weekly patch with fixes applied to the environment specified in your service request.

If you are interested in participating in the early testing cycles to help validate these fixes, please submit a service request asking for inclusion in the early test cycle. In your service request, be sure to provide the following information:

  • Confirmation that you are an Essbase 21c fix candidate
  • The URL of the test environment where you would like the patch applied
  • The specific business process running in the test environment

You may request Oracle to apply the fix across multiple test environments for different Oracle Fusion Cloud Enterprise Performance Management business processes impacted by Essbase 21c, such as Planning, FreeForm, Financial Consolidation and Close, Tax Reporting, Profitability and Cost Management, and Enterprise Profitability and Cost Management. This approach helps Oracle validate the fixes across a diverse set of Cloud EPM business processes.

Impact on Business Processes and Customizations

Does this advisory apply to NetSuite EPM customers also?

Yes, this advisory applies to all Oracle Fusion Cloud Enterprise Performance Management business processes, including NetSuite EPM.

What should we do if our business processes do not use Essbase?

Although business processes such as Oracle Fusion Cloud Enterprise Data Management, Narrative Reporting, and Account Reconciliation do not use Oracle Essbase, they are synchronized with the overall Cloud EPM update schedule and should follow the guidance provided in this document. Please review these sections for exceptions:

What steps should we take if we are developing new Cloud EPM business processes in our test environment on 25.11?

You may continue developing and testing on your 25.11 test environment. When ready to go live, submit a service request to upgrade your production environment to 25.11 and then proceed with deployment. See Requesting Oracle to Apply Monthly Update to Production Environments Prior to the Third Friday in the Operations Guide for instructions.

Update Rollout Management

What is Oracle’s recommendation to keep test and production environments compatible?

To maintain compatibility for cloning or migration, Oracle recommends that both the test and production environments be kept on the same monthly update until Oracle Fusion Cloud Enterprise Performance Management resumes regular monthly updates. You can take one of these steps:

How do we revert a test environment from 25.11 to 25.10?

Submit a service request to Oracle asking that the 25.11 test environment be rolled back to 25.10. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

The rollback process recreates the environment in its initial state and removes all application content, including:
  • Data
  • User-created artifacts (such as applications, cubes, and scripts)
  • Any customizations
After the rollback is complete, import a 25.10 snapshot into the reverted environment (you cannot use the backup snapshots created in 25.11). You may take one the following actions:
  • Import a snapshot created for this environment before it was updated to 25.11. Use the listBackups EPM Automate command to verify that the availability of a valid 25.10 snapshot in the environment. Please note that the daily snapshots are retained for 60 days only. So, the most recent 25.10 snapshot created before November 7 will be available only until beginning of January.
  • Clone from the production environment (which is on 25.10). For instructions, see:

Can we keep some business processes on a different version?

Due to integration challenges, Oracle does not recommend running business processes on different monthly updates with some notable exceptions. Please review the Integration section of this FAQ for further clarifications.

How do we manage cloning between test and production when they are on different monthly updates?

Cloning is supported only when:

  • Both the source and target environments are on the same monthly update
  • The target environment on the next monthly update (one update higher than the source environment)

If your test environment is on 25.11 and your production environment is on 25.10, you can clone from the production environment to the test environment, but not from the test environment (on 25.11) to the production environment (on 25.10).

What preventative measures will Oracle implement to ensure similar issues do not occur in the future?

The October update of the Oracle Essbase database upgrade went smoothly. The issues reported by customers were exposed when they were triggered due to specific customizations in customer applications that were migrated in Test. These issues were not found in many other customer applications who took this update nor were they found in the out of box content that Oracle Fusion Cloud EPM delivers through its applications. The immediate preventive measure that Oracle has taken is to not update customer production environments. Meanwhile, the Cloud EPM team at Oracle is working with the Oracle Essbase database team to have these issues resolved, and will be working closely with the customer applications that reported these issues to ensure that fixes for these issues are well tested before we roll it across all remaining customers’ test and production environments. We are also providing guidance to customers on areas to test and allowing customers additional time to test their applications before the next fleetwide monthly update.

Are the current banner messages in our applications indicating a Groovy update in January 2026 (26.01) still relevant?

There is no January 26.01 release. Groovy updates initially planned for 26.01 will be deferred to a later date that will be announced once we resume regular monthly customer environment updates.

Managing Skip Update Requests

How does the skip update request work if Oracle is not applying monthly updates?

If you set a skip update request for a monthly update that Oracle is not applying, no action is required on your part. For example, if you are on the 25.08 update and have skipped 25.09, 25.10, and 25.11, no further action is needed.

The skipUpdate EPM Automate command allows you to skip updates only for up to 3 months from the current update. If you wish to skip updates further in the future, you need to submit a service request for Oracle to process the skip update for you.

We submitted a skip update request for 25.11. Will it hold when Oracle resumes monthly updates in 2026?

You can make skip updates requests only for up to 3 months from the current update. For instance, if you are on the 25.10 update, you can set skip update request for 25.11, 25.12, and 26.01. In this scenario, to skip for releases beyond 26.01, you must submit a service request asking Oracle to process the skip update for you.

Managing Essbase Version Variations within Cloud EPM Deployments

How do we identify the Essbase version of our environment?

Check the Activity Report to identify the Oracle Essbase version of the environment. For more information, see Information About Your Environment in the Getting Started Guide for Administrators.

Can we downgrade the Essbase version to a version earlier than the current 21c?

No, Oracle cannot downgrade just the Essbase version because it is a part of the technology stack. You can, however, revert your environment to a monthly update which contains the desired Essbase version. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

How do we manage different combinations of Essbase versions in the 25.10 update?

  1. Our test environment is on 25.11 with Essbase 21c, but the production environment is on 25.10 also with Essbase 21c. How do we roll back the test environment to 25.10 on Essbase 21c rather than take the production environment to 25.11?

    Submit a service request asking Oracle to downgrade the test environment to 25.10 with Essbase 21c. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

  2. Our test environment is on 25.11 with Essbase 21c, but the production environment is on Essbase 11g. How do we roll back the test environment to 25.10 on Essbase 11g?

    Submit a service request asking Oracle to downgrade the test environment to 25.10 with Essbase 11g. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

  3. Our test environment is on 25.10 with Essbase 21c while the production environment is on 25.10 with Essbase 11g. Should the production environment be on updated to 25.10 with Essbase 21c to support cloning? Can it remain on 25.10 with Essbase 11g?

    In this scenario, you can clone from the production environment (on 25.10 with Essbase 11g) to the test environment. However, you cannot clone from the test environment (on 25.10 Essbase 21c) to the production environment.

    Submit a service request asking Oracle to do one of these steps:

We rolled back our 25.11 test environment with Essbase 21c to 25.10 with Essbase 11g. Can we import a snapshot from the 25.11 environment into the reverted 25.10 environment?

Oracle Fusion Cloud Enterprise Performance Management does not support snapshot import from an environment with Essbase 21c to an environment with Essbase 11g. Hence, you cannot import a snapshot from the 25.11 environment with Essbase 21c into a 25.10 environment with Essbase 11g.

Can we manually migrate artifacts from a 25.11 environment Essbase 21c to a 25.10 environment Essbase 11g?

Oracle does not recommend the manual migration of artifacts across environments on different Essbase versions.

However, under rare circumstances where such a manual migration is essential because upgrading the production environment to 25.11 is impossible, you may manually migrate artifacts that do not impact Essbase metadata or data, for example, forms and dashboards.

Note:

For Essbase-dependent processes (Planning, FreeForm, Financial Consolidation and Close, Tax Reporting, Enterprise Profitability and Cost Management, and Profitability and Cost Management) do not manually import any artifact that impacts Essbase data.

Integration, Snapshots, and Migration

What should we be cautious about when reverting from 25.11 to 25.10?

Reverting from 25.11 to 25.10 results in Oracle recreating the environment to bring it back to its initial, provisioned state and removes all application content, including:

  • Data
  • User-created artifacts (such as applications, cubes, and scripts)
  • Any customizations
You can import only a 25.10 snapshot into a 25.10 environment. After reverting the test environment to 25.10, because you cannot use the backup snapshots created in 25.11, unique changes or data updates done in 25.11 will be lost.

Can we roll back our test environment from 25.11 to 25.10 on Essbase 21c?

For Planning FreeForm, Financial Consolidation and Close, Tax Reporting, and Enterprise Profitability and Cost Management: you can import a 25.11 snapshot into a 25.10 environment with Oracle Essbase 21c.

Submit a service request asking Oracle to roll back the 25.11 test environment to 25.10 with Essbase 21c. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

For Narrative Reporting only: You can import a 25.11 backup snapshot into a 25.10 environment.

For Account Reconciliation and Enterprise Data Management only: You cannot import a 25.11 backup snapshot into a 25.10 environment.

Can we upgrade the environments from 25.10 to 25.11 and import 25.10 snapshots into them?

This action is supported for all business processes, including Planning, FreeForm, Financial Consolidation and Close, Tax Reporting, Profitability and Cost Management, Enterprise Profitability and Cost Management, Account Reconciliation, Enterprise Data Management, and Narrative Reporting

See Requesting Oracle to Apply Monthly Update to Production Environments Prior to the Third Friday in the Operations Guide for instructions.

How will integration work across Cloud EPM business processes and versions?

In general, all business processes are expected to be on the same Oracle Fusion Cloud Enterprise Performance Management update for integrations to be supported with some notable exceptions for Narrative Reporting, Enterprise Data Management, and Account Reconciliation:

  • Narrative Reporting 25.11 will work with Financial Consolidation and Close, FreeForm, Planning, Profitability and Cost Management, and Tax Reporting 25.10 except for Remote Library and Navigation Flows.

  • Enterprise Data Management 25.11 will work with the rest of Cloud EPM on 25.08, 25.10, 25.11, except for Task Flows and Navigation Flows. Please submit a service request to upgrade the production environment to the 25.11 update.

  • 25.12 (customer patch request) for Enterprise Data Management will be supported with the rest of Oracle Fusion Cloud EPM on 25.10 or 25.11. Submit a service request to request 25.12 features.

  • 25.12 (customer patch request) for Account Reconciliation will be supported. Submit a service request to request 25.12 features. Review these guidelines for Account Reconciliation:

    • Data integration between environments (for example pulling balances from Financial Consolidation and Close to Account Reconciliation) should work fine. Note: Oracle recommends not using Pipeline on a different version; however, using Pipeline within Account Reconciliation itself will be supported.
    • Task Manager integration with Account Reconciliation will work if configuration is already in place. New connections cannot be set up, and existing connections cannot be edited.

  • Navigation Flows and Cross Pod Data Maps require you to be in the same version across all EPM business processes where they are applicable.

  • Oracle Smart View for Office 25.200 will be supported across all Cloud EPM business processes across different versions.

Feature Requests, Bug Fixes, and Customer Support

What should we do if we are waiting for new features planned in Cloud EPM Roadmap?

For Enterprise Data Management and Account Reconciliation, you can request features from the December 2025 (25.12) update to be applied to your 25.10 or 25.11 environments. To do so, submit a service; these features will be delivered based on service request only. When you request features through a service request, you will receive access to the appropriate Enterprise Data Management and Account Reconciliation documentation.

For all other business processes, all features in the roadmap will be planned after the fleet update for Oracle Fusion Cloud Enterprise Performance Management resumes (26.02 or later). The Monthly Cloud Applications Readiness document will be suspended until official Cloud EPM updates resume.

How can we obtain bug fixes while on 25.10 or 25.11 updates?

Submit a service request asking Oracle to apply a customer-specific patch for your current update. If the fix is related to Oracle Essbase, consider reverting to an update that previously worked well for your application. See Requesting a Rollback of Production or Test Environments to a Previous Update in the Operations Guide for instructions.

Where can we find documentation on new features in 25.11 and earlier updates?

The Oracle Cloud Enterprise Performance Management (EPM) help center and online help provides comprehensive documentation, including details on all new features introduced in the 25.11 update. If you are on an earlier update, you can still use the documentation—just keep in mind that some features may have been added in later updates. Use the What’s New to identify which features apply to your specific update.

What is the new roll out plan for Essbase 21c in Cloud EPM?

The earliest we are looking to resume Oracle Essbase 21c is February 2026 (26.02). We will have a better sense in Jan 2026. Once we have the customer reported issues resolved, we will deliver patches for those issues to specific customers. Other customers and partners can also request to deploy these patches in their environments. This will most likely happen in February 2026. Once we have a comfort level after a group of customers have deployed the patches, we will plan on a fleetwide roll out. If you as a customer or partner are interested in participating in validating the patches we roll out for the fixes, refer to If we are interested in assisting with the assessment of Oracle’s planned resolutions, how can we participate or get involved in testing them?

EPM Announcements Related to Monthly Updates

12/11/2025 Email Announcement

Important Reference Sources on EPM Cloud Monthly Updates

Hello Oracle EPM Cloud Service Administrators,

As informed in recent notifications, EPM Cloud has recently paused monthly updates for 25.11 (production), 25.12, and 26.01. Since this decision, over the last two weeks, we have taken steps to provide reliable EPM development sources of information for your reference on this topic:

  1. Detailed FAQ (last updated today) that covers responses to diverse customer questions that have come through to us so far. This will be your go to resource for information on this topic. We will continue to update this document on an as needed basis.

  2. Customer Connect session on Dec 4th 2025 (recording and download file available) which had close to 700 registrations with close to 500 live attendees.

Customers have been reviewing the FAQ document and the Oracle Cloud Customer Connect session and have been engaging in discussion with us on this topic through monitored discussion threads and Announcements in Oracle Cloud Customer Connect.

We are closely monitoring the Essbase 21c fix plans and plan towards the resumption of monthly updates in the Q1 CY2026 timeframe. Over 20% of our customer environments have already taken up the 21c version of Essbase, and we have seen a steady uptick in requests to move to Essbase 21c in 25.11 production environments as customers test their applications and find no regressive impacts in their environments. We encourage more customers and partners to test their critical applications on Essbase 21c version based on guidance provided in the FAQ.

We also want to open up the opportunity for customers and partners to get an early patch of the resolutions for issues reported by some customers in their 25.11 test environments. The process to request for early access to the 21c patches through an SR is covered in the FAQ. We encourage the EPM community to take us up on early validation efforts for their critical applications across Planning, Consolidation, Tax, FreeForm, and Profitability.

11/25/2025 Email Announcement

Important Update: Oracle Monthly Releases – Ensuring Stability and Your Success

Hello Oracle EPM Cloud Service Administrators,

At Oracle, your success and business continuity are our top priorities. As part of our commitment to delivering the highest quality solutions, we want to keep you informed about the latest updates regarding the monthly releases for your environments.

Recent Update Approach

On November 20, we communicated that the 25.11 monthly update would not be automatically applied to production environments across all EPM business processes. This proactive measure to not update production environments with the 25.11 (November 2025) update was taken after identifying a few application-specific issues with the Essbase 21.7.x version included in the 25.11 update. Even though only sporadic performance and accuracy issues were reported by a few customers, we decided to not apply this monthly update to any production environment by default to ensure we deliver the highest quality software.

To maintain the high standards and reliability that you expect from Oracle—especially during this critical period when many of our customers are engaged in their year-end processes—Oracle has decided to not apply the 25.12 (December 2025) and 26.01 (January 2026) updates as well to all environments (test and production) across all EPM business processes.

What This Means for You

Test Environments: By default, your test environments will remain on 25.11. Production Environments: Your production environments will continue to run the stable 25.10 update until the upcoming 26.02 update.

Tailored Guidance for Your Situation

We understand each customer’s situation is unique. Please refer to the guidance below based on your current needs:

  • Interested in New Features from 25.11?

    You are welcome to explore and test the 25.11 update in your test environments. After confirming success, you may submit a service request if you would like to apply 25.11 to some or all of your production environments.

  • Need to Clone from Test to Production?

    If your test environment is on 25.11 and you need to clone to a production environment that is on 25.10 (with different Essbase version), please submit a service request. We can assist you in reverting your test environment to 25.10, allowing for seamless migration. Please ensure you use a compatible snapshot created with 25.10 after this rollback.

  • Developing on Test While Production Is Live?

    You can continue developing and testing with 25.11 in your test environment. Once you are confident, you may request its deployment to production.

  • On Quarterly Updates or On an Update Prior To 25.10 And Prefer No Change?

    If your production environment uses the quarterly release (currently 25.08) and you do not wish to adopt new features from 25.11, no changes are required. If needed, we can help align your test environment with production by reverting it back to 25.08 via a service request.

  • In Initial Development Phase (Not Yet in Production)?

    You can fully leverage the 25.11 features in your test environments now and reach out when you’re ready to move those updates to production.

Stay Connected

We encourage you to join our upcoming Customer Connect session (planned for Thu. Dec 4th, 2025 - to be announced in Oracle EPM Customer Connect Events Page) for direct answers and to share your feedback. We will also have a FAQ question section for this subject in our EPM Cloud documentation to answer common question in this matter.

If you have any questions or require support tailored to your environment, please submit a service request—our team is here to help.

Thank you for partnering with Oracle. We appreciate your trust and look forward to supporting your ongoing success.

PS: This notification applies to all EPM Business Processes: Planning, Financial Consolidation and Close, FreeForm, Tax Reporting, Profitability and Cost Management, Enterprise Profitability and Cost Management, Account Reconciliation, Enterprise Data Management, and Narrative Reporting.

11/20/2025 Email Announcement

IMPORTANT: 25.11 Update will NOT be applied on your Production Environments

Hello Oracle EPM Cloud Service Administrator,

We notified you on October 31 that Oracle would apply the 25.11 monthly update on your production environments on November 21.

As mentioned in What’s New for last few months, this update includes upgrade to Essbase version 21.7.xx. The 25.11 monthly update with 21.7.xx Essbase was already applied on the test environments. A few customers reported problems caused by this new Essbase version. Even though only a few issues were reported, Oracle has decided to not apply this monthly update to any production environment to ensure we deliver the highest quality software.

Thus, your production environments will not be updated with the 25.11 update by default.

Actions to take:

  • Account Reconciliation, Narrative Reporting, and Enterprise Data Management environments: These business processes do not use Essbase and thus, these issues do not apply to these environments. If you want any of your production environments with these business processes to be updated to the 25.11 update, please create a service request.

  • Planning, Financial Consolidation and Close, Enterprise Profitability and Cost Management, Tax Reporting, Profitability and Cost Management environments: These business processes use Essbase. However, if your test environments have not experienced any issues after the 25.11 update and you want your production environments to be updated with the 25.11 update, please create a service request.

If you have any questions about this notification, please create a service request.