IMPORTANT Actions and Considerations

One-Week Lag Between Readiness Documents Live and Help Center Live

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

NETSUITE CLOUD EPM PLATFORM

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

Starting with the May (26.05) 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  and will stop working starting with the May (26.05) update:

If you use the IP allowlists per environment, you must transition to Network Perimeter before this 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.

Note: Execution of these commands using an older version of EPM Automate will be ignored starting the May (26.05) update. 

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

Renaming of Roles References in Cloud EPM

In the past, Cloud EPM user interfaces and documentation used the label Predefined Roles for the identity domain–level roles (Service Administrator, Power User, User, and Viewer). However, Oracle Identity Cloud uses the label Application Role for the identity domain–level roles. This inconsistency has caused confusion across Cloud EPM. To address this, starting with the May (26.05) update, Cloud EPM screens and documentation will use the label Application Role to refer exclusively to the identity domain–level roles.

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

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: Profitability and Cost Management,Close Management and Consolidation, FreeForm, Narrative Reporting, Planning and Budgeting, 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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, Profitability and Cost Management, Close Management and Consolidation, FreeForm, 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 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Profitability and Cost Management, Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Close Management and Consolidation, FreeForm, Planning and Budgeting, 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: Close Management and Consolidation, FreeForm, Planning and Budgeting, 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:

NETSUITE ACCOUNT RECONCILIATION

Computing the Amounts in Each Period When Using an Amortization Schedule

Starting with this 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.

NETSUITE CLOSE MANAGEMENT AND CONSOLIDATION

Removal of the configConsolWithThreadVar Substitution Variable

Starting with this update, the configConsolWithThreadVar substitution variable will be removed, and any variable value that you have specified will be ineffective. The default value is False.  If you currently have this substitution variable set to True, please set the value to False in advance of its removal, and report any issues that you encounter to Oracle Support.

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

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.

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