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.

In addition to the applicable Important Actions and Considerations discussed in the Cloud EPM Platform section below, this update includes Important Actions and Considerations specific to:

CLOUD EPM PLATFORM

Cloud EPM to Remove the setIPAllowList and getIPAllowList EPM Automate Commands and the IPAllowList REST API

Starting with the February 2026 (26.02) update, Oracle will remove the setIPAllowList and getIPAllowList EPM Automate commands and the IPAllowList REST API.

These commands and REST APIs were temporary solutions implemented due to the lack of an equivalent security feature in Oracle Identity Cloud.However, with the introduction of Network Perimeter functionality in Oracle Identity Cloud, you can set the allowed and/or blocked IP addresses and CIDRs for the whole domain, which also protects access to Cloud Console.

As part of this transition, the following EPM Automate commands and REST APIS used for managing and viewing IP allowlists are marked as deprecated:

If you use the IP allowlists per environment, you must transition to Network Perimeter by the February 2026 update. See Migrating from Per-Environment IP Allowlist to Network Perimeter in an Identity Domain in the Getting Started Guide for Administrators for detailed information.

Applies to: Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Narrative Reporting, Planning, Profitability and Cost Management, Tax Reporting

EPM Automate to Use Java 17 Instead of Java 8

Starting with a future update (currently planned for October 2025 (25.10)), EPM Automate will no longer use Java 8 and will instead use Java 17.

Windows users will not be affected, as the Windows installer includes the required Java version. However, on Linux/UNIX and macOS X, since EPM Automate relies on a user-installed Java version, users will need to update to Java 17 to continue to use the EPM Automate version after this update.

If you're using an older version of EPM Automate on Linux/UNIX or macOS, there's no need to update to Java 17—these versions will continue to work with EPM Cloud environments on this update and later. However, you won't have access to the new features introduced in these versions. Oracle recommends updating to the latest version of EPM Automate to take advantage of the latest functionality.

Plan to Prevent Export and Import of Parameters Marked Secure in Other Web Service Provider Connection Types

Starting with the September 2025 (25.09) update, all the parameters that are marked Secure for Other Web Service Provider connection types will no longer be exported or imported. These parameters are set while specifying Advanced Options for external connections.

This change is being made to enhance the security of Cloud EPM and is consistent to the passwords defined in the Connections interface, which are already not exported and imported.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

Learning Paths Decommissioned

Starting in the December (25.12) update, all Learning Paths will be decommissioned and will no longer be available.

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.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

Replace/Remove the Slash Symbol (/) in Folder Names

Currently, if a folder name contains a slash symbol (/), all the artifacts in that folder are not backed up, failing the daily backup. To avoid this issue, please review your folder names for slash symbols, and remove or replace them.

Oracle plans to automatically replace slash symbols in folder names with a space character in a future update (currently planned for the fourth quarter of 2025).

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

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.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

Plan to Discontinue Support for New Infolets and Other Infolet Actions

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

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

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.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

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 Application Settings, change Smart View Ad Hoc Behavior to Standard.
In Smart View, open worksheets created in Native mode and reconnect.
Refresh the sheets.

NOTE:

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.

For additional information, see Smart View Ad Hoc Behavior Option and Saved Ad Hoc Grids in Working with Oracle Smart View for Office.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

Job Scheduling Migration in Data Management/Data Integration

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. The "Migrate Schedules to Platform Job Scheduler" will be removed in the 25.09 (September) update. Customers must migrate prior to 25.09 if they have not already done so.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, Planning, Tax Reporting

The new scheduling functionality is not available in Profitability and Cost Management and Account Reconciliation.

The EPM Platform Job Scheduler console is not available for Account Reconciliation customers. These customers will need to automate any existing scheduled jobs in Data Management using EPM Automate or rest calls outside of Account Reconciliation.

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.

Applies to: Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

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. After this change, 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.

Applies to: Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

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 (Cloud EPM Financial Reporting Statement of Direction)

Please note that as of the 25.06 (June) update, Oracle Financial Reporting has been de-supported.

For more information:

See Appendix B in the Designing with Reports Guide: Migrating Reports from Financial Reporting.

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.

ACCOUNT RECONCILIATION

Remove Dashes from Balance Load Subsegments

By the November 2025 (25.11) update, dashes will not be allowed in subsegments in balance loads as they are considered a special character. This change will follow the current restrictions in place that prevent dashes from being used in segments and from being entered to subsegments through the UI. Any integrations currently loading dashes will fail and will need to reformat dashes to another character. Customers should start updating mappings to prepare for this change.

ENTERPRISE DATA MANAGEMENT

Custom Validations Are Now Run on Predefined Members in Cloud EPM Applications

Starting with this update, custom validations are now run on nodes that have the Enterprise Predefined Member property set to True in Enterprise Data Management for Planning Modules, Financial Consolidation and Close, Enterprise Profitability and Cost Management, and Tax Reporting applications. This change in behavior may result in new validation warnings or errors for nodes that did not fail validations in previous releases. Custom validation expressions should be modified to exclude predefined members if the validations should not apply to them.

FINANCIAL CONSOLIDATION AND CLOSE

Considerations for Creating Additional Cubes

The ability to create Additional Block Storage Cubes was introduced in the July (25.07) update on a restricted basis and is available only by submitting a technical Service Request (SR). Note that this information is required for the Service Request:

Is the application in DSO format? Additional cubes can only be enabled on DSO applications.
Is the application Ownership enabled? Ownership Management is not currently supported with additional cubes.
Are you using Translation Overrides?
Are you using the Calculate Movements feature?
Have you configured Scenario/Year override members for the system-generated Opening Balance calculations?
Are you using the seeded Balance the Balance Sheet calculation?
What is the proposed use case? For example: "We would like to separate out our additional external reporting detail into another cube."

Migrating an Application with Consolidation Setting for Translation Rules

If you enable the new Skip Translation Rules if Entity Currency Equals Parent Currency consolidation setting in 25.08 and then import a 25.08 snapshot into a 25.07 environment, the import process should display a backward compatibility warning that the new feature is not imported. However, the import process does not display any warning. Also, the 25.07 environment will display a consolidation setting called FCCS_SETTINGS_LBL_SKIP_TRANS_RULES_IF_EC_EQUALS_PC, which is invalid.

Data Source Currency Attribute

The 25.06 What’s New incorrectly stated that the label of the Data Source Currency Attribute option was changed to Default Currency. The Data Source Currency Attribute label is actually Entity Currency.

Member Formula Changes for Enhanced Organization by Period (EOBP) Applications

After you upgrade from 25.02 to 25.03, the CalcStatus formula changes for the FCCS_CSTATUS FILTER and FCCS_NSTATUS FILTER system members are not updated in Enhanced Organization by Period (EOBP) applications. To apply the formula changes, you must manually run the Enable Features option without selecting any features.

Importing Enhanced Organization by Period Applications

Importing an application that has the Enhanced Organization by Period (EOBP) feature enabled into a non-EOBP environment is not supported.

PROFITABILITY AND COST MANAGEMENT

REST API Supported Media Types

The supported media type for all Profitability and Cost Management REST APIs is "application/json".

You must always set the "Content-Type: application/json" header, to avoid the "Unsupported Media Type" error.

This requirement has always been documented in the REST API for Oracle Enterprise Performance Management Cloud guide. If your REST API calls have been working without this header, or with a different media type, you will now need to correct your API calls to use and specify the supported media type.

Oracle Profitability and Cost Management Application Type Statement of Direction

The Oracle Profitability and Cost Management Application Type Statement of Direction provides an overview of the strategic plans and future direction of Oracle Profitability and Cost Management Cloud Service and Oracle Enterprise Performance Management Enterprise Cloud Service Profitability and Cost Management business process. Included is information about the change in Development focus to the newer Enterprise Profitability and Cost Management Application Type available exclusively with Enterprise Performance Management Enterprise Cloud Service.

Oracle Support Document 2955235.1 (Oracle Profitability and Cost Management Application Type Statement of Direction)

ENTERPRISE PROFITABILITY AND COST MANAGEMENT

Possible Future Restrictions on Special Characters

Oracle recommends against the use of special characters in names and descriptions.

New system requirements may restrict certain special characters in Description fields for models, rule sets, rules, and profit curves. Other fields, such as job comments, may also be affected. Any such changes will be announced and take effect with at least three months notice.

New Calculation Warning

In some cases, an allocation rule generates "Allocation In" but not "Allocation Out" or "Allocation Offset." This can occur due to missing source or driver data, or use of label-only hierarchy members.

To help identify such cases, a new warning has been added during calculation that suggests reviewing the rule setup, data, and hierarchy selections. For example, "Rule 'XXX' has produced Allocation In but did not produce Allocation Out for one or more sources. Review the Source Data, Driver Data, and the Storage Types of the Hierarchies selected in the rule."