IMPORTANT Actions and Considerations
CLOUD EPM PLATFORM
Generative AI Features Require Cloud EPM 26.04 or Later
Beginning with the July (26.07) update, 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
ENTERPRISE DATA MANAGEMENT
Record Count Log Download Uses Numeric Cell Formatting and Adds an Order Column
Starting with the March (26.03.56) update, the Record Count Log Excel download writes the count-related columns as Number-formatted cells (instead of text) so the values can be used for summation, comparisons, and other numeric operations in Excel. The count columns in the Nodes and Record Count Contribution sections are written with 0 decimal places, thousands separators enabled, and a prefixed negative sign for negative values.
In addition, the Excel download now includes an Order column (also Number-formatted) that contains the row sequence (1, 2, 3, …) to help you restore the original ordering after sorting.
Archived Status Now Displayed in Property Inspector
Starting with the March (26.03.56) update, the Property Inspector indicates when an application or node type is archived by appending the label “(Archived)” to the application and node type names in the left navigation pane. The “(Archived)” label is also displayed in the right-side detail panel for Node Type Overrides, after the node type link.
Editable Flag Can Now Be Changed at Application and Node Type Levels Regardless of Base Setting
Starting with the March (26.03.56) update, the Property Inspector no longer disables the Editable checkbox at the Application or Node Type levels when the base property parameter for Editable is unchecked. Users with permission to edit properties at the Application or Node Type levels can now change the Editable setting regardless of how it is set at the level above (that is, at the Base level for the application, or the Application level for the node type).
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.
Relaxed Permission Validation for In Flight Submitted Requests
Starting with the March (26.03.56) update, permission checks for In Flight requests are 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 allows a request to continue processing if a submitter’s or collaborator’s 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 still applies. Changes made by enrichers continue to be validated even if they were made prior to the recall or push back.
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.
Financial Consolidation and Close Application Registration Now Applies Dimension-Specific Node Type Overrides
Starting with the March (26.03.56) update, initial registration of Financial Consolidation and Close (FCCS) applications applies more restrictive node type overrides by dimension for the Data Storage, Data Storage (cube), Aggregation, and Data Type properties (including allowed values and, in some cases, specified default values). As a result, the values available for these properties may be limited based on the dimension being registered. Modify Registration does not update existing application or node type overrides for these properties and dimensions; however, if you add a new dimension and then run Modify Registration, EDM applies the appropriate overrides for the new dimension. Allowed values managed directly during registration (such as Currencies and Smart Lists) continue to be updated by Modify Registration at the application level.