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 Classic Environments Will Default to Legacy List Pages

All customer environments on the Oracle Cloud Infrastructure (OCI) default to the 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 Cloud EPM Classic environments default to Legacy List Pages with an option to switch to the standardized pages. The Classic environments will default to the 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.

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

Change in the Group Assignment Audit Report Columns

Starting with the May (25.05) update, the columns in the Group Assignment Audit Report created through Migration User Interface, groupAssignmentAuditReport EPM Automate command, and Group Assignment Audit Report REST API will have the following changes:

Proposed Changes to the Group Assignment Audit Report

Planned Changes to the Group Assignment Audit Report

A new column named User/Group Type will be added as the second column of the report. This column will indicate whether the entity in the User/Group Name (first) column is a user, a predefined group, an IDCS group, or an EPM group.
The Action column will be moved as the third column in the report.
A new column named Group Type will be added to the report. This column will indicate whether the group in the Group column is an IDCS group or an EPM group.
The label of the Administrator column will be changed to Performed By.

These changes are being done to make the report more usable.

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

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.

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

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.

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

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

Starting with the December 2024 (24.12) update, 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.

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

See Configuring Authentication Parameters for an OAuth 2 OCI (Gen 2) Environment in Getting Started with the Digital Assistant 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.

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

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.

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

Plan to Discontinue Support for Infolets

Oracle plans to stop supporting the creation of infolets in a future update (currently targeted at June through September 2025). 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.

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 your test environment:

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.

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.

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

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.

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.

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 in the Cloud EPM Business Process, and users can access these features in the current Cloud EPM update. Data Management is not going away – we are only moving a few features now that have 100% parity with Data Integration. Profitability and Cost Management customers are not affected by the migration and do not see a change in their Data Management user interface. 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 Cloud EPM 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 in the Cloud EPM business processes.

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. Please note that Account Reconciliation, Financial Consolidation and Close, Planning and Tax Reporting provide a feature to report against the Data Integration relational tables using a custom SQL and a BI Publisher report template via Task Manager.

The ability to create new Custom Applications in Data Management will no 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 Custom Application in Data Management under Cloud EPM Platform in the Important Actions and Considerations section of this document.

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

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

See Administering Data Integration 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.

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. 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.

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

Please note that the Oracle Financial Reporting de-support date has been finalized for June 2025.

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

User Access to Profile Card

Starting with the April 2025 (25.04) update, everyone with a ‘User’ role will see the Profiles card by default. Users will be able to view Profiles that they have a workflow or viewer role on, which aligns with the reconciliations they can see currently. For customers that have already turned on the option to “Allow workflow users to reassign reconciliation profiles” there is no change in behavior since that option displays all Profiles to Users. As before, Viewer users will not have access to the Profile card unless they have been granted the Profile View or Profile Manage privilege.

ENTERPRISE DATA MANAGEMENT

Migration Snapshots Earlier Than 22.12 No Longer Supported

Starting with this release, migration snapshots earlier than December 2022 (22.12) cannot be imported in Oracle Enterprise Data Management. The previous earliest supported snapshot was December 2021 (21.12). See About Snapshots.

Non-secure (HTTP) URLs Not Allowed in Enterprise Data Management Connections

Starting with the April 2025 (25.04) update, application connections and global connections in Enterprise Data Management will require the use of the secure HTTP protocol (HTTPS). This restriction will be enforced during application registration, on the Connections tab of the Application inspector, in the Global Connection inspector, and to the REST APIs for updating application and global connections. Non-secure HTTP URLs will no longer be supported. All URLs specified for application and global connections 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.

FINANCIAL CONSOLIDATION AND CLOSE

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

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

Issues with Member Selection When Connecting to the Models or Designer Screen Using Connections From Another Environment

When connected to the Models screen or the Designer screen using Connections from another environment, you may experience an unexpected error message while selecting members, or the Member Selector dialog may not always open as expected. To work around this issue, access these screens directly from within Enterprise Profitability and Cost Management.

Preferences Related to Calculation Performance

There are three calculation performance related preferences in Enterprise Profitability and Cost Management that can be used to alter calculation performance characteristics and behavior in certain special cases. Each preference can be set or changed by creating a substitution variable. When creating the substitution variable, be sure to create it for “All Cubes”.

NOTE: The default values shown in the table do not require the creation of a substitution variable.

Variable Name	Default Value	Description / When to Use	Behavior
EPCM_CALC_NET_ENABLE	No	“NET” is for “nonempty tuple”. Allocation rules on sparse cubes may perform better by setting this preference to “Yes”. Not all Enterprise Profitability and Cost Management applications will see a performance benefit from enabling this preference. Note: This affects Allocation Rules only, Custom Calculation rules are not impacted by this setting.	No (default): All applicable cells in rule ranges are considered during the calculation. Yes: Cells with no values are ignored/skipped during the calculations.
EPCM_CALC_USE_SCRATCH_CELLS	Yes	An enhancement in the calculation algorithm generally improves performance for certain types of Allocation rules. In rare cases, Allocation rules can be out of balance due to this enhancement. If you detect out-of-balance rules, use this variable to disable the enhancement as a temporary workaround. If you detect out-of-balance rules, use this variable to disable the enhancement, and report the issue to Oracle Support.	Yes (default): The calculation performance enhancement is enabled, which may offer better calculation performance. No: The calculation performance enhancement is disabled.
EPCM_ENABLE_JAPI_CONNECTION_POOL	Yes	This variable is for an enhancement that improves the management of Essbase connections during calculation. The enhancement generally improves stability and may improve performance during high-concurrency calculations. It is now enabled by default; you can use this variable to disable it if directed to do so by Oracle Support.	No (default): The Essbase connections enhancement is enabled. Yes: The Essbase connections enhancement is not enabled.

Variable Name

Default Value

Description / When to Use

Behavior

EPCM_CALC_NET_ENABLE

“NET” is for “nonempty tuple”. Allocation rules on sparse cubes may perform better by setting this preference to “Yes”. Not all Enterprise Profitability and Cost Management applications will see a performance benefit from enabling this preference.

Note: This affects Allocation Rules only, Custom Calculation rules are not impacted by this setting.

No (default): All applicable cells in rule ranges are considered during the calculation.

Yes: Cells with no values are ignored/skipped during the calculations.

EPCM_CALC_USE_SCRATCH_CELLS

Yes

An enhancement in the calculation algorithm generally improves performance for certain types of Allocation rules. In rare cases, Allocation rules can be out of balance due to this enhancement. If you detect out-of-balance rules, use this variable to disable the enhancement as a temporary workaround. If you detect out-of-balance rules, use this variable to disable the enhancement, and report the issue to Oracle Support.

Yes (default): The calculation performance enhancement is enabled, which may offer better calculation performance.

No: The calculation performance enhancement is disabled.

EPCM_ENABLE_JAPI_CONNECTION_POOL

Yes

This variable is for an enhancement that improves the management of Essbase connections during calculation. The enhancement generally improves stability and may improve performance during high-concurrency calculations. It is now enabled by default; you can use this variable to disable it if directed to do so by Oracle Support.

No (default): The Essbase connections enhancement is enabled.

Yes: The Essbase connections enhancement is not enabled.