Understanding EPM Cloud Change Management Process

Generally, each Oracle Enterprise Performance Management Cloud subscription is comprised of two environments. If you have a four-stage process (involving an environment each for development, test, acceptance, and production), you must purchase a new subscription for the two additional environments that you require.

Oracle is responsible for the change management process involved in updating the software and configuration of all environments. Any issue caused as the result of this process is defined as a regression.

You (not Oracle) are responsible for the change management of custom artifacts such as dimensions, forms and reports in all environments. The migration of artifacts from one environment to another is a self-service operation.

Oracle delivers software and configuration updates through one of the following:

• Monthly update: Contains a set of features and bug fixes for all instances of all services. The monthly update is applied to the test environments on the first Friday of the month and to production environments on the third Friday of the month.
• Weekly patch: Includes bug fixes and is mainly for fixing regression bugs found in test environments. The weekly patch is applied to all test environments on the second Friday of the month.
• One-off patch: Contains fixes for regression bugs, customer blocking bugs, or new features. One-off patches are applied to specific test environments on request.

  Customers whose environments are updated with a one-off patch test the updated environments and provide approval to apply the patch to production environments. Subsequently, Oracle applies the one-off patch to their production environments.

• Emergency patch: Contains one bug fix that needs to be applied immediately to an environment. This patch can be applied to test, production, or both as required.