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.

Classic Environments Will Default to Legacy List Pages

Starting with this update, all customer environments on the Oracle Cloud Infrastructure (OCI) will default to the new standardized user interface for EPM Platform artifact pages (with an option to revert to the legacy user interface using the Legacy List Pages application setting). However, all EPM Cloud Classic environments will default to Legacy List Pages with an option to switch to the new standardized pages. The Classic environments will default to the new standardized pages after they are moved to OCI.

For information about migration from Classic to OCI, see EPM Cloud Classic to Oracle Cloud Infrastructure (OCI) Migration of US Government Environments in Oracle Enterprise Performance Management Cloud Operations Guide.

Reports Card Tabs Will Become Individual Cards on the Home Page

Starting with the March 2025 (25.03) update, Oracle plans to restructure the Reports card tabs as individual cards on the Home page.

Currently, the Reports card consists of three tabs: Reports, Financial Reports, and Documents. After restructuring, you'll see individual cards for Reports, Financial Reports, and Documents on the Home page.

Cube Refresh to Validate for Conflicting Metadata Names

In an upcoming update (currently targeted at the second quarter of 2025), Oracle plans to validate for conflicting metadata (member or dimension names). These validations will occur during Cube Refresh, and recommendations will surface as warnings to the user. If an application is found to have conflicting metadata names, the Cube Refresh will complete with a new status called "Completed with Warnings." Customers can then correct the metadata names and avoid erroneous behavior and potential bugs. Customers can also view the validation warnings on the Jobs console.

Non-secure (HTTP) URLs Not Allowed in Task Manager Connections

Starting with the April 2025 (25.04) update, the Task Manager Connections screens and the Create Connection and  Update Connection REST APIs will require the use of the secure HTTP protocol (HTTPS). Non-secure HTTP URLs will no longer be supported. All URLs specified in the Task Manager Connections screens and the Create Connection and the Update Connection REST APIs must start with the secure HTTP protocol ( https://) after this update.

This is being done to improve security. If you have concerns or questions, please create a service request.

Oracle No Longer Deprecating EPM Automate and REST API Settings for Idle Session Timeout for OCI (Gen 2) Environments

In a previous Readiness document, Oracle announced that starting with the February (25.02) update, the setIdleSessionTimeout and getIdleSessionTimeout EPM Automate commands and the corresponding REST APIs would no longer work for OCI (Gen 2) environments.

Oracle has decided not to deprecate these EPM Automate commands and the corresponding REST APIs. They will continue to work for OCI (Gen 2) as well as Classic environments.

Custom Parameter URL Name Change in Digital Assistant for Oracle Cloud EPM

The custom parameter URL is now common for all business processes in Digital Assistant for Oracle Cloud EPM. The new custom parameter format for existing users has changed to epmBaseURL.

See Configuring Authentication Parameters for an OAuth 2 OCI (Gen 2) Environment in Getting Started with the Digital Assistant for Oracle Cloud Enterprise Performance Management for more information.

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.

Future Direction for Forms and Dashboard 1.0

Starting with the June 2025 (25.06) update, Oracle plans to de-support Forms 1.0 and Dashboards 1.0. Also effective the June update (25.06) all new environments 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 Dashboards 1.0 to 2.0 and convert their dashboards from 1.0 to 2.0 as soon as possible. Gaps found in Dashboards 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.

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.

Additional Execution Sequencing Routines for Task Manager Jobs

In a future update, Task Manager Jobs will include additional execution sequencing routines to ensure application and data integrity. When potential conflicting jobs are executed simultaneously, the service will sequence the jobs to ensure application integrity. While the individual job’s execution times will not be impacted, the job’s start time may be delayed due to the optimization sequencing.

Change in the Default Format When Exporting to Microsoft Excel

In a future update, the default format for exporting table data to Microsoft Excel from Task Manager will be changed to .XLSX instead of .XLS.

Plan to Discontinue Support for Infolets

Oracle plans to stop supporting the creation of infolets in a future update. Applications using the Redwood Experience will no longer see the option to create infolets on the listing pages. In applications using non-Redwood themes, the Create button on the Infolets page will be disabled. There will be no future enhancements or support for infolets.

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

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:

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.

Data Management Feature Migration to Data Integration

The user interface pages listed in the table below are no longer available in Data Management, but are available in Data Integration. Data Integration is available from the Data Exchange card from the home screen, and users can access these features in the current update. Data Management is not going away – we are only moving a few features now that have 100% parity with Data Integration. REST APIs are not impacted by this change.

Data Management Data Integration Data Integration Navigation Path

Source System

Configure Connections

From the Data Integration UI, select the Actions drop down, and then Applications.

In Applications, there is an icon next to the drop down labeled Configure Connections.

Target Application

Applications

From the Data Integration UI, select the Actions drop down, and then Applications.

Period Mapping

Period Mapping

From the Data Integration UI, select the Actions drop down, and then Period Mapping.

Category Mapping

Category Mapping

From the Data Integration UI, select the Actions drop down, and then Category Mapping.

Data Integration is the next generation of the Data Management user interface, enabling users to easily build and manage integrations. As feature parity between Data Integration and Data Management becomes complete, Data Management features will be turned off, and users will use the new Data Integration user interface instead.

This transition is gradual; future What's New documents will include information about the first set of planned changes as well as updates about additional changes planned for the future.

All Data Integration features discussed in this document are currently generally available.

Integration definitions built with Data Management are also visible in Data Integration, which enables an easy transition. (Data Integration is a new user interface on the Data Management data model and does not require migration of content from Data Management to Data Integration).

Please note that additional new integration features will only be included in Data Integration, and will not be back-ported to Data Management. Critical bug fixes and security fixes will still be made to Data Management until all features are fully migrated. In addition, all features from Data Management will be migrated to Data Integration with the exception of the following:

  • The batch feature will be replaced by the new Pipeline feature. The Pipeline feature was available in the June (23.06) update.
  • The Report Definition feature will not be migrated, only the Report Execution feature.
  • The ability to create new Custom Applications in Data Management will no be longer available, and customers should use the “Data Export to File” application type instead. (Existing integrations using a custom application will not be impacted.) See Removal of Support for Custom Application in Data Management in the Important Actions and Considerations section of this document.

For reference, please see the Data Integration guide available from the documentation library. Select the desired business process, then Books, and then scroll down to the Administering Data Integration for Oracle Enterprise Performance Management Cloud documentation link.

See Administering Data Integration for Oracle Enterprise Performance Management Cloud for more information.

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 EPM Cloud Platform category: Announcing Updated Guidance on Cloud EPM Financial Reports Deprecation

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

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

Please note that the Oracle Financial Reporting tentative deprecation dates have been moved to mid-to-late CY25.

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.