Order Management Suite Patching Strategy For One-Off Requests and RUPs
(Doc ID 396910.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Order Management - Version 220.127.116.11 to 12.1 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
Order Management releases Cumulative patches for the following code lines - 11.5.10 - R12.0. Order Management does not release Cumulative Patches for 12.1. Rather, there are Applications-wide "point" releases (12.1.2, 12.1.3, etc.). Please see E-Business Suite Release R12.1 Info Center for latest 12.1.x announcements (navigation path: My Oracle Support > Knowledge tab > Tools and Training > E Business Suite > Select 12.1 Info Center).
Oracle recommends that customers apply Cumulative patches at regular scheduled intervals. This document explains the release process for One-Off patches.
By default all bug fixes are placed into an Order Management Cumulative patch that is released on a scheduled basis.
The Scheduled Release Date matrix (*) for R11.5.10/R12.0 RUPs is located on <Note 453944.1> Order Management Cumulative Patches
Approval For one-off requests:
Severity 1 Bugs:
One-Off patches will be automatically released (if technically feasible)
Escalated Severity 2 Bugs:
One-off patches will be automatically released as individual patches, and estimated time of patch release will be provided in the bug after it is closed. If the provided ETA is too late, Support can request an earlier release. The request will be considered by development based on the customers business impact and any milestone or critical date that is presented. There is no need for support to log a separate one-off request, suport can communicate directly to development via the bug.
Severity 2 Bugs:
These patches are not released as one-off patches but are bundled into Cumulative patches (where applicable). If there is an emergency situation where a one-off is required, or if cumulative patches are no longer available for given Applications release, Support can log a one-off request for a patch. Support will be required to obtain the following information from the customer when requesting such a one-off patch:
- Strong business justification for the one-off
- Functional & Financial impact
- Specify the required date if the one-off is required before the CU release date (the reasons why this is required need to be included and customers need to be aware of the below implications of applying one-off fixes as noted below)
Note - Beginning December 1, 2010, 11i10 one-off patch approval will be subject to minimum patch levels as explained in E-Business Suite 11.5.10 Minimum Patch Level and Extended Support Information Center <Note 1199724.1>.
Points to Note Regarding One-Off Patch Requests:
- Oracle aims to minimize separate one-off patches so that we can improve the quality of the code and minimize potential consequences associated with a one-off patch.
- One-off patches have limited testing due to adhoc/emergency basis of these patches. These patches are not regression tested within the entire code line.
- One-off patches are not always technically feasible.
- The full implications of an individual patch are not always known.
- Numerous one-off patches are inherently less predictable.
- Environments with numerous one-off patches are non-standard which can cause unique type problems that are more difficult to diagnose and fix.
- Regular code upgrades (roll up patches), which have been fully testing will naturally increase overall stability.
For you the customer:
1) We ask that schedule for and apply roll up patches at regular intervals or as required.
2) If you cannot schedule and apply a roll up, we will review your situation and provide the ETA for the one-off. Development will do their best to prioritize your request.
These Cumulative Patches and Roll up Patches should not be confused with the traditional Recommended Patch List (RPL) patches from Development.
NAV Path for RPL: Metalink > Patches & Updates > E-Business Suite Recommended Patch List > Maintenance Release = 11.5.10 CU.2 > Select your product (i.e. Order Management) with 11i.SCM.PF.J
RPLs additionally continue to be highly recommended from Development.
Some customers may be concerned with the size of roll up patch. There are standard scripts to check how many changes a roll up will make to a customer's system. For example, a customer can choose to try 'adpatch apply = no' to see how many changes will happen.
Or, Support can provide you with our Patchcomp.sh script. Since this script is not available as a Metalink note, please request this from your Support representative. We can download it and email it to you.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document