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

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

Renaming of Roles References in Cloud EPM

In the past, Cloud EPM Access Control screens and documentation used the label Predefined Roles for the identity domain–level roles (Service Administrator, Power User, User, and Viewer). The label Application Roles was used for the granular roles within business processes.

However, Oracle Identity Cloud and Console use the label Application Role for the identity domain–level roles. This inconsistency has caused confusion across Cloud EPM. To address this, Cloud EPM screens and documentation will adopt the following terminology changes starting with the 26.01 (January 2026) update:

The label Application Role will now exclusively refer to the identity domain–level roles. It will be synonymous to the currently used Predefined Role label. However, the documentation and user interfaces will continue to refer to use the Predefined Role label at this time.
The label Granular Role will be used to refer to the business process–specific roles in user interfaces and documentation.

Upcoming Change to Default Idle Session Timeout

Starting with the November 2025 (25.11) update, the default idle session timeout for Cloud EPM will be reduced from 75 minutes to 30 minutes. This means users will be automatically signed out from identity domain after 30 minutes of inactivity — a change aimed at enhancing platform security.

You can continue to customize this setting using the setIdleSessionTimeout command in EPM Automate or the Set Idle Session Timeout REST API. The timeout can be set to any value between 4 and 480 minutes.

Note:

If you've already customized your idle session timeout, your current setting will remain unchanged after the update.
If you wish to keep the timeout at 75 minutes, you’ll need to update it manually before November 2025, using one of the methods mentioned above.

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

Starting with the February 2026 (26.02) 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:

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

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

Learning Paths Decommissioned

Starting in the December (25.12) update, all Learning Paths will be decommissioned and will no longer be available.

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

Oracle plans to automatically replace slash symbols in folder names with a space character in a future update (currently planned for the fourth quarter of 2025).

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

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: Close Management and Consolidation, FreeForm, Planning and Budgeting, Profitability and Cost Management, 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.
Open worksheets from Smart View and reconnect.
Refresh the sheets.

NOTE:

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

NETSUITE ACCOUNT RECONCILIATION

Changes to Eligibility of Reconciliations for Auto Submit and Auto Approve Rules

Starting with the November (25.11) update, reconciliations in an open status with transactions that are only from a Data Integration load or are carried forward from a previous reconciliation will be eligible for Auto Submit Reconciliation and Auto Approve Reconciliation rules in the post processing of a balance load. Reconciliations that have one or more transactions added by the user for that period will continue to be ineligible for Auto Submit Reconciliation and Auto Approve Reconciliation rules unless rules are run manually.

Changes to Profile Validation

Starting in the November (25.11) update, user roles will be evaluated to determine if a profile is valid or not. This may mean that previously valid profiles will show as invalid, if the user has been removed, or does not have sufficient privileges. There will be no change to the Create Reconciliations job where the user role has always been validated prior to creation.

Remove Dashes from Balance Load Subsegments

By the November 2025 (25.11) update, dashes will not be allowed in subsegments in balance loads as they are considered a special character. This change will follow the current restrictions in place that prevent dashes from being used in segments and from being entered to subsegments through the UI. Any integrations currently loading dashes will fail and will need to reformat dashes to another character. Customers should start updating mappings to prepare for this change.

NETSUITE CLOSE MANAGEMENT AND CONSOLIDATION

Plan for Removal of the configConsolWithThreadVar Substitution Variable

Starting with the December (25.12) 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 (SR). 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."

Migrating an Application with Consolidation Setting for Translation Rules

If you enable the new Skip Translation Rules if Entity Currency Equals Parent Currency consolidation setting in 25.08 and then import a 25.08 snapshot into a 25.07 environment, the import process should display a backward compatibility warning that the new feature is not imported. However, the import process does not display any warning. Also, the 25.07 environment will display a consolidation setting called FCCS_SETTINGS_LBL_SKIP_TRANS_RULES_IF_EC_EQUALS_PC, which is invalid.

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.

Member Formula Changes for Enhanced Organization by Period (EOBP) Applications

After you upgrade from 25.02 to 25.03, the CalcStatus formula changes for the FCCS_CSTATUS FILTER and FCCS_NSTATUS FILTER system members are not updated in Enhanced Organization by Period (EOBP) applications. To apply the formula changes, you must manually run the Enable Features option without selecting any features.

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.

NETSUITE PROFITABILITY AND COST MANAGEMENT

Ampersand (&) No Longer Supported as a Valid POV Delimiter

The ampersand (&) is no longer supported as a valid POV delimiter in the following EPM Automate commands and REST APIs:

Calculate Model
Clear Data by Point of View
Copy Data by Point of View
Delete Point of View

Anything preceded by & will be considered a substitution variable. If you are using & as a POV delimiter in any of these EPM Automate commands or REST APIs, you must replace it with another valid POV delimiter.

Possible Future Restrictions on Special Characters

Oracle recommends against the use of special characters in names and descriptions.

New system requirements may restrict certain special characters in Description fields for models, rule sets, rules, and profit curves. Other fields, such as job comments, may also be affected. Any such changes will be announced and take effect with at least three months notice.

New Calculation Warning

In some cases, an allocation rule generates "Allocation In" but not "Allocation Out" or "Allocation Offset." This can occur due to missing source or driver data, or use of label-only hierarchy members.

To help identify such cases, a new warning has been added during calculation that suggests reviewing the rule setup, data, and hierarchy selections. For example, "Rule 'XXX' has produced Allocation In but did not produce Allocation Out for one or more sources. Review the Source Data, Driver Data, and the Storage Types of the Hierarchies selected in the rule."