IMPORTANT Actions and Considerations

One-Week Lag Between Readiness Documents Live and Help Center Live

Because Oracle readiness documents (What's New and New Feature Summary) are live one week before the monthly update is applied to Test environments, some links to documentation included in the readiness documents will not work until after the Oracle Help Center update is complete when the monthly update is applied to Test environments.

Deprecation of Java 8 for EPM Automate

Starting with the August (25.08) update, EPM Automate will discontinue the use of Java 8. Instead, it will start using Java 17.

Windows users of EPM Automate are not affected by this change because the Windows installer ships with the required Java distribution. Because the use of EPM Automate on Linux/UNIX operating systems is dependent on a user installed Java version, users of such operating systems must update to Java 17 to continue using EPM Automate.

Upcoming Changes to the Permission Required to Create Forms, Dashboards, and Library Folders

In a future update, Oracle plans to change the permissions required to create forms, dashboards, and sub folders. With this change, users assigned to the Power User predefined role will require write access to the folder in which they create forms, dashboards, or sub folders.

Currently, all users assigned to the Power User predefined role can create forms, dashboards, and sub folders in folders to which they have read access.

Plan to Replace the Slash Symbol (/) in Folder Names with a Space Character

Starting with the September 2025 (25.09) update, if a folder name contains the slash symbol (/), it will be replaced with a space character. This is to ensure that the daily backup is created without issues. Currently, if a folder name contains a slash symbol (/), all the artifacts in that folder are not backed up, failing the daily backup.

Future Direction for Forms and Dashboard 1.0

The de-support date for Forms 1.0 and Dashboard 1.0 has been shifted from June 2025 (25.06) to October 2025 (25.10). Effective October 2025, all environments will default to the 2.0 setting for Forms and Dashboards with existing environments having the option to switch back to 1.0 with no support for 1.0. All new environments deployed effective October (25.10) will be deployed with Forms 2.0 and Dashboards 2.0 only; the option to switch to Forms 1.0 will no longer be available.

Customers are advised to change application settings from 1.0 to 2.0 and convert their dashboards from 1.0 to 2.0 as soon as possible. Gaps found in 2.0 should be reported using the Service Request process so that Oracle Support can evaluate if the request is justified and, if so, resolve them. Any issues found in 1.0 for either Forms or Dashboards will be resolved in 2.0 if it can be reproduced in 2.0. There will be no bug fixes or enhancements to Forms or Dashboards 1.0.

Task Manager will continue to display standalone forms using Forms 1.0 even if the Application setting is set to 2.0. Dashboards within Task Manager will display in 2.0 when the application setting is set to 2.0.

For more information, see Forms 1.0 and Dashboard 1.0 Statement of Direction. You will need to sign into Oracle Support to access this document.

Plan to Discontinue Support for New Infolets

Starting with the October 2025 (25.10) update, Oracle will no longer support the following infolet actions:

  • Creation of new infolets
  • Copy As, which duplicates an existing infolet
  • Designating an infolet as Default and defining infolet dots on the Home page

Plan to Discontinue Support for Reverting to Legacy List Pages

Starting with the October 2025 (25.10) update, Oracle plans to de-support the option to revert to Legacy List Pages.

Removal of Support of Native Mode Option for Smart View Ad Hoc Behavior Application Setting

The Native mode option for the Smart View Ad Hoc Behavior application setting is no longer supported in Smart View. 

While customers can continue using Native mode, this mode is no longer supported for escalations and enhancements.

Standard is the ad hoc mode upon which all enhancements in Cloud EPM are being delivered.

Oracle stopped supporting Native mode at the end of year 2024. Customers on Native mode are advised to convert the Smart View Ad Hoc Behavior application setting for their environments to Standard mode and test their use cases.

Any gaps found should be logged as an enhancement to Standard mode. Enhancements should be logged on the Customer Connect EPM Platform Idea Lab as soon as possible for Oracle to review.

Perform the following steps to begin working with Standard mode in your test environment:

  1. In Application Settings, change Smart View Ad Hoc Behavior to Standard.
  2. Open worksheets from Smart View and reconnect.
  3. Refresh the sheets.

NOTES:

  • The expectation for existing Native mode worksheets is that they will work “as is” when the setting is changed to Standard. New ad hoc sheets will only be created in Standard mode using Standard features.

  • Smart Forms are not supported in Standard mode. There is no plan to support them in Standard mode.

Job Scheduling Migration in Data Management/Data Integration

With the addition of the new Job Scheduling feature in Data Integration in the September (24.09) update, customers must migrate any existing job schedules from Data Management to the EPM Platform Job Scheduler console. The scheduling functionality accessed from the user interface in Data Management has now been deprecated. To support the migration to the new job scheduler, a new script titled "Migrate Schedules to Platform Jobs Scheduler" is available from System Maintenance Tasks in Data Management.

Calculation Manager Errors and Considerations Enforcement

In a future update, Calculation Manager will enforce the execution of the Errors & Considerations diagnostic tool for any rule being launched, validated, or deployed. This enhancement is scheduled to coincide with the enhancement to the Rules listing page. Administrators will see the Rule Status indicating if there are Errors and/or Considerations in the listing page in addition to the Errors & Considerations tab in Calculation Manager.

Rules will continue to deploy and execute even with Errors or Considerations. In all cases, existing rules that are already deployed will continue to run as-is without any change in behavior. However, Oracle Support will require all Errors to be cleared before reviewing any issues submitted for such rules. Any remaining Considerations will require justification for why they are not cleared before Oracle Support will review any such rules.

Change in Behavior for Grids Created from Groovy and REST APIs for ASO Cubes

In a future update, the suppression behavior for grids created via Groovy DataGridDefinitionBuilder and the exportdataslice REST API for ASO cubes will be made consistent with that of the run time data grids created using the Form Designer. Previously, if a grid was built for an ASO cube in Groovy or REST API, then the system used the NON EMPTY MDX clause to suppress missing rows when the suppressMissingBlocks flag was true. Now, when a grid is built for an ASO cube, it will use the NON EMPTY MDX clause when suppressMissingRows is true, and suppressMissingBlocks will be ignored. This means that ASO grids with suppressMissingRows true and suppressMissingBlocks false will now start using MDX. Likewise, ASO grids with suppressMissingRows false and suppressMissingBlocks true will no longer use MDX. Grids where the suppressMissingRows and suppressMissingBlocks flags had the same value will not be impacted. These changes may result in a change in behavior or performance for some ASO grids. If this happens and is undesirable, consider toggling the value of suppressMissingRows from the builder or the JSON payload in case of the REST API.

Oracle Financial Reporting Statement of Direction

Please refer to the announcement on Cloud Customer Connect in the Enterprise Performance Management Resource Center: Announcing Updated Guidance on Cloud EPM Financial Reports Deprecation

Please refer to the Statement of Direction for Oracle Financial Reporting:

Oracle Support Document KB62016 (EPM Cloud Financial Reporting Statement of Direction)

Please note that in this update, Oracle Financial Reporting is now de-supported.

For more information:

  • On June 8, the most recent Oracle Cloud Customer Connect event, Migrating Your Financial Reporting to Reports, was presented. There is a presentation, an event recording, and an FAQ sheet accessible. In order to view the event recording and documentation, you must log in to Cloud Customer Connect.

Start Using the New URLs for Oracle Help Center Libraries

When accessing Enterprise Performance Management and Enterprise Data Management libraries on the Oracle Help Center, update your bookmarks to use the new URLs. For example, the new Planning library URL is https://docs.oracle.com/en/cloud/saas/planning-budgeting-cloud/index.html

The older URLs, such as  https://docs.oracle.com/cloud/latest/planning-budgeting-cloud/index.html are currently being redirected, so the best practice is to use the new URLs.

Start using these new Oracle Help Center URLs now for the libraries for Enterprise Performance Management:

Change in Behavior for Duplicate Members Being Returned While Using MDX

Starting with the August (25.08) update, the behavior for removing duplicate members for MDX flows will be made consistent with the behavior for removing duplicate members for non-MDX flows.

Currently, certain flows in Planning use MDX expressions such as “Suppress Missing Block” for BSO, “Suppress Missing Rows” for ASO, and “Database suppression” for both ASO and BSO. When MDX is not used, duplicate members are removed from a single row or column definition. In some cases, the duplicate removal in a single row or column definition was silently failing leaving unexpected duplicate members. We are fixing the MDX flow behavior to match the non-MDX behavior which correctly removes duplicates.

Just like the existing non-MDX flow, you can force duplicates by adding them in separate row/column definitions. This existing functionality will not change.

This change will impact Planning forms, Smart View, Reports Groovy grids, and REST grids.