IMPORTANT Actions and Considerations

CLOUD EPM PLATFORM

Generative AI Features Require Cloud EPM 26.04 or Later

Beginning in July 2026, Oracle will provide Generative AI functionality only for environments running the April (26.04) or later update. Environments that are not upgraded to 26.04 or later update by the end of July 2026 will lose access to Generative AI features.

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

EPM Automate to Require Java 17 or Newer

Starting with the August 2025 (25.08) update, EPM Automate installations will be supported on Java 17 or later only.

Note: Because the required Java version is included with the EPM Automate client installer on Windows, this change only affects Linux client installations. You must ensure that Java 17 or newer installed on the Linux client machine and that JAVA_HOME points to it.

ENTERPRISE DATA MANAGEMENT

Relaxed Permission Validation for In Flight Submitted Requests Extended to Enrichers

In the March (26.03.56) update, permission checks for In Flight requests were relaxed for actions that were performed before the last submitted date (including changes made by the request Owner or a Collaborator while in Draft, or after a request is recalled or pushed back). This allowed a request to continue processing if a submitter’s or collaborator’s permissions changed, or if they were removed from the system after the request was submitted.

Starting with this update, those permission check changes have been extended to request enrichers as well. Requests will continue to be processed if a submitter’s, collaborator’s, or enrichers permissions change, or if they are removed from the system after the request was submitted.

Note: This change applies only to In Flight requests. For requests in the Submit stage (either initially or after being recalled or pushed back), normal permission enforcement for submitters and collaborators, and (starting in this update) enrichers still applies.

Replay Automatically Handles Incomplete Subscriptions

Starting with the March (26.03.56) update, when you initiate a Replay Subscription for a request, any subscriptions that have the In Process status and are older than 24 hours are marked as Failed before starting the replay.  These incomplete subscriptions may be due to a service restart or other type of system interruption.  This allows the failed subscriptions to be reprocessed during the replay operation.

Requests with Zero Request Items Cannot be Transitioned via REST API

Starting with the March (26.03.56) update, attempting to transition (for example, Submit, Approve, Reject, etc.) a request with zero request items using the REST API now returns an error message. Requests must have at least one request item in order to be transitioned using the REST API.