The December (20.12) monthly update of the EPM Cloud introduces new functionality for customers to delay updates to an EPM Cloud production environment without the need to create a service request. This is beneficial when you need to complete time-sensitive tasks (i.e. closing of a quarter) or are in a critical phase of your implementation project.
There are two self-service options available beginning with the 20.12 Update:
These self-service features can also be used to remove all skip update requests that were previously made using this command so that the environment is updated to the main code line. You can also use these features to list the skip update requests currently specified for an environment.
Please note that these self-service options cannot be used on environments that contain a one-off patch. Additionally, they can only be used to skip updates for a maximum of 2 cycles, after which the environment will be returned to the main code line.
For further information on requesting production upgrade delays using EPM Automate, including how to request a delay of more than two cycles, please see Requesting Upgrade Delay for Production Environments. For information on using the REST API to skip updates, please see the REST API for Oracle Enterprise Performance Management Cloud > Skip Updates documentation. Please begin using these features for your production upgrade delay requests beginning with the 20.12 release.