IMPORTANT Actions and Considerations

CLOUD EPM PLATFORM

Generative AI Features Require Cloud EPM 26.08 or Later by the End of January 2027

Generative AI functionality will require the August (26.08) or later update of Cloud EPM by the end of January 2027. Any environment that is not upgraded to 26.08 or late update by the end of January 2027 will no longer have access to Generative AI features.

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

EPM Automate Clients Earlier Than 26.09 Will Not Work with 26.12 and Later EPM Cloud Environments

Starting with the December (26.12) update, Cloud EPM environments will no longer support EPM Automate clients bundled with the 26.08 update or earlier.

Beginning with the 26.09 update, EPM Automate will change the format of the encrypted password (.epw) file to enhance its security. Cloud EPM environments on 26.09, 26.10, and 26.11 updates will be able to read the legacy .epw file format and the new file format created by EPM Automate that will be bundled with the 26.09 update.

Starting with the 26.12 update, Cloud EPM environments will accept only the new .epw file format generated by EPM Automate 26.09 or later. 

To avoid authentication failures, Oracle recommends that you complete these steps after your environment is updated to 26.09. You must complete these steps before you can use EPM Automate to access 26.12 Cloud EPM environments:

  1. Upgrade EPM Automate to version 26.09 or later.
  2. Run the EPM Automate encrypt command to generate a new .epw file in the updated format.

The new .epw file will work with all Cloud EPM environments on update 26.09 or later.

Note: If you use an.epw file with EPM Agent: Continue to use an .epw file generated with the EPM Automate encrypt command from the 26.08 update or earlier until the EPM Agent is updated to the 26.10 update.

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

Removal of Support for User Names Prefixed with the Cloud Account Name for EPM Automate Login Command and REST APIs

Starting with the November (26.11) update, the login EPM Automate command and REST APIs will no longer accept user names prefixed with the Cloud Account name.

Currently, you can specify a user name in the format accountName.userName (for example,epmCloudAccount.example.user@example.com) when using the EPM Automate login command and Cloud EPM REST APIs. You can also specify the user name without the account name prefix (for example, example.user@example.com).

Beginning with the November (26.11) update, the accountName.userName format will no longer be supported. You must specify the user name without the accountName prefix when using the EPM Automate login command and Cloud EPM REST APIs.

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