Changes to the Cloud EPM Update Cadence Policy for Environments Not on the Mainline
Effective immediately, to meet stringent security and compliance requirements, Oracle will implement the following changes to the update cadence policy for Cloud EPM environments that are not on the main code line.
- An environment may remain on a one-off patch for a maximum of three months. Any exception beyond that must be approved by Oracle and is granted only for three more months, for a total of six months. During this period:
- If the regression is fixed in a monthly update within the three (or six, if approved) months: The environment will be upgraded to the applicable monthly update and returned to the main code line.
- If the regression is not fixed in a monthly update within the three (or six, if approved) months: The environment will be upgraded to a new one-off patch based on the latest code line, ensuring it remains current while retaining the required fix.
- An environment may remain on Skip Update or Manual Skip Update for a maximum of three months. Any exception beyond that must be approved by Oracle and is granted only for three more months, for a total of six months.
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
Business Benefit: The changed policy ensures that required updates are expeditiously applied to your environments to ensure security and compliance.
Steps to enable and configure
You don't need to do anything to enable this feature.
Key resources
- In the Operations Guide