IMPORTANT Actions and Considerations

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

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

Warning for Unclosed Grids Created through Groovy

Starting with the August (26.08) update, if a grid is created in a Groovy script but is not closed, an error message will be thrown during Groovy script validation. If you deploy and run the rule anyway, the job console will show "competed with warnings" with a message indicating that one or more grids in the script were not closed.

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

Upcoming Restriction on Using IP Addresses in Connection URLs

You are no longer able to define or update connections using IP addresses in the Connection URL. The Manage Connections page prevents users from creating new connections or modifying existing ones that reference an IP address in their URLs. This change is being implemented to enhance security and ensure compliance with Oracle best practices.

Oracle recommends proactively reviewing your existing connection definitions and updating any URLs that use IP addresses to hostname-based URLs before this change takes effect.

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

Removed Support for Entry of User Who is Not the Logged-in User as Proxy User

On the Data Integration Pipeline Details page, the system now defaults to the logged-in username in the Proxy User field. You cannot enter a different username as a proxy user. Previously, you could specify any username in the Proxy User field and system prompted for the password if it was not the logged-in username.

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

For more information, see Allowing Non-Administrators to Execute Jobs in the Pipeline in Administering Data Integration.

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

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

Unicode Whitespace in Member and Alias Names

Previously, users could inadvertently include invisible Unicode whitespace characters, such as non-breaking spaces, at the end of member or alias names. While the service allowed these names, Essbase did not support or store them, resulting in silent failures during cube refresh operations. This often led to inconsistency between EPM Cloud and Essbase, potential duplicate errors, and customer support escalations.

The system now automatically trims any trailing Unicode whitespace from member and alias names during metadata validation and integration processes. This brings EPM Cloud and Essbase into strict alignment and eliminates instances where data is not written or members are out of sync due to invisible control characters. If the uniqueness of member or alias names among siblings is violated after trimming, users now receive a clear error message.
If you previously relied on trailing spaces (including invisible Unicode spaces) for uniqueness, review your member and alias names to ensure they remain unique after trimming. Most customers are not expected to be impacted, but if you encounter an issue, create a Service Request for assistance.

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

Snapshot Import Fails with Reserved Word or Duplicate Names

Snapshot import fails with errors if metadata includes member or alias names that are reserved words in Essbase (such as "COUNT") or were not unique among siblings after whitespace normalization. In these cases, attempts to import or refresh the cube would result in an error indicating the invalid or duplicate name.

Review and update your exported and archived metadata to ensure that member and alias names do not use reserved words and are unique after whitespace trimming. If your process fails due to these validations, update the problematic names as per the guidance in the error messages. For any unexpected issues or questions, create an Oracle Service Request for support.

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

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

Enterprise Performance Management (EPM) Skills for Oracle Digital Assistant (ODA) Statement of Direction

Please refer to the announcement on Cloud Customer Connect in the Enterprise Performance Management Resource Center: Enterprise Performance Management Skills for Oracle Digital Assistant Statement of Direction

Please refer to the Statement of Direction for Enterprise Performance Management Skills for Oracle Digital Assistant:

Oracle Support Document KB867980 (Statement of Direction for Enterprise Performance Management Skills for Oracle Digital Assistant)

Please note that the Enterprise Performance Management Skills for Oracle Digital Assistant de-support date has been finalized for November 2026.

For more information:

ACCOUNT RECONCILIATION

Changes to the TM_AUDIT_TRAIL Table
In the August 2026 (26.08) update, the Transaction Matching table TM_AUDIT_TRAIL will be updated to improve storage utilization and performance. Several columns that previously stored text will now store numeric codes or identifiers (for example, OBJECT_TYPE, FIELD_NAME, MODIFICATION_TYPE, SERVICE, MODIFIED_BY). Some status values in OLD_VALUE or NEW_VALUE may appear as numeric strings.

Action: If your custom report queries the TM_AUDIT_TRAIL table directly, you must update the queries to handle new numeric types and decode values using the provided mappings.

Computing the Amounts in Each Period When Using an Amortization Schedule

Starting with the April 2026 (26.04) update, when calculating the amortization amounts for each period, fractional pennies are now carried over to the next period until they equal one penny. The sum of the amortization amounts in the summary will always be equal to the original amortization amount.

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

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

PLANNING

Workforce Rules Being Deprecated

In the 24.12 update, the following Workforce rules were updated to automatically determine the FixParallel dimension for all new applications.

Workforce Rules

Synchronize Defaults 2.0
Synchronize Definition 2.0
Process Loaded Data with Synchronize Defaults
Process Loaded Data with Synchronize Definition
Calculate Compensation for all 2.0

Strategic Workforce Planning Rules

Process Loaded Strategic Workforce Data
Calculate Supply for All Data
Calculate Demand for All Data

Oracle recommends that any customers who created applications prior to the December 2024 update modify the following Action menus to use the 2.0 version of the rules:

Existing Actions
New Hires Actions

Note that these action menus will be tracked as modified artifacts, and you must reverse your customizations and then re-apply them to take advantage of any new features for these menus in the future.

The prior versions of these rules will be deprecated sometime in the fourth calendar quarter of 2026.

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)

Feature Removal Notice: Rules Outline and Waterfall Tabs

Due to underlying technology changes, starting with the July (26.07) update, you will no longer be able to view, create, edit, or delete individual rules and rule sets from the Rules Outline tab in the Application > Calculation Rules screen, or in the Waterfall tab in the Models > Designer screen. Rules will still be viewable and editable in the Rules Express Editing and Mass Edit tabs in each of those screens. The Manage Rules screen (invoked from the Navigator) will continue to provide full create, edit, and delete capability for rules sets and rules.

Screen	Feature	Status
Calculation Rules in the Application Cluster	Rules Outline tab Create/Edit Rules and Rule Sets screens Rules Express Editing tab	Removed Removed Available
Designer in the Models Cluster	Waterfall tab Create/Edit Rules and Rule Sets screens Mass Edit tab	Removed Removed Available
Manage Rules from the Navigator	Create/Edit/Delete Rules and Rule Sets	Available

ENTERPRISE PROFITABILITY AND COST MANAGEMENT

& (ampersand) is No Longer Supported in REST APIs and EPM Automate Commands

Due to conflicts with other features, the ampersand (&) is no longer supported as a POV delimiter in Enterprise Profitability and Cost Management REST APIs and EPM Automate commands. Please update your scripts to use a different delimiter. Supported delimiters are:

_ (under score)
# (hash)
~ (tilde)
% (percentage)
; (semicolon)
: (colon)
- (dash)

See Enterprise Profitability and Cost Management REST APIs and EPM Automate Commands for more information.