Release 12 eBusiness Suite Codelines, Codelevels and PatchWizard by Paula Elder

In Release 12, Oracle E-Business Suite patches are grouped into codelines. A codeline begins with a point release (for example, Release 12.0) consisting of a unique set of product features, and progresses to include all the patches created to maintain that point release. The initial Release 12.0 point release introduced codeline A. Additional point releases introduce new codelines, each identified by a unique letter. For example, Release 12.1 introduced codeline B, and Release 12.2 is expected to introduce codeline C.


1.jpg

 

Patches associated with codelines not only implement a set of product features for that point release, but also provide fixes to that set of features. We describe this unique set of product features for a point release as a codelevel and assign it a unique number.


2.jpg



Further, codelevels identify patches for individual products. For example, if Oracle General Ledger (GL) is associated with your system, codelevel R12.GL.A.1 is the first set of fixes to codelevel R12.GL.A, R12.GL.A.2 is the second, and so on. Codelevels are cumulative - each one contains the initial set of features plus all the fixes created to date for that product or product family. If individual bug fixes are created along the codeline, then subsequent codelevels will contain the bug fixes. For example, in the diagram above, the two bug fixes along codeline A will be included in codelevel A.2.

 

All codelevels created after the initial point release for a product or product family are aggregated into release update packs (RUPs). RUP1 is equivalent to R12.0.1, RUP2 is equivalent to R12.0.2, and so on. RUPs provide bug fixes. In addition, they may also provide feature enhancements, which provide new functionality that has a limited impact on your system.

 

So how do you know what codeline or codelevel you currently have for your applications?  One way is to use Oracle Application Manager (OAM), accessible from the System Administrator responsibility, click on the Dashboard function and then choose Software Updates - Codelevels Summary.  From this screen you can see all products and families ie

 


3.jpg


 

Knowing what codeline and codelevel you are on is essential for checking that patch prerequisite requirements are met but how do you know what patches are available for your release.  One solution is to use the Patchwizard tool.

 

Patchwizard was introduced in 11.5.10 and has been enhanced in R12.  Using a zip file called  InfoBundleR12.zip (which you download from https://updates.oracle.com/download/InfoBundleR12.zip) copied into a stage area identified in the patchwizard prefenences screen you can run tasks which identify patches you may be interested in based on filters identifying products you wish to keep up to date with.  To access the filters choose Sitemap - Maintenance - Patchwizard - Tasks (Define Patch Filters)

 


4.jpg

 

Once you have the filters you require (the screen shot above illustrates the contents of a seeded filter) you can then run the Recommend/Analyze options which use a combination of  the information found in the InfoBundleR12 zip file and the current codeline, codelevel and applied patch information to list recommend patches, including the impact the patches would have if you were to apply them.  For example



5.jpg

 

Recommended Patches Results List -

 

Impact Details for a Patch Listed in the Recommended Patches List -



6.jpg



Patchwizard can provide you with ability to automate the download of the InfoBundleR12 zip file, as well as the ability to schedule the Recommend Patches tasks to allow for the proactive search for code changes.  This can be achieved with the user base active on the system. If you have the luxury of a system that is allowed an internet connection to the support site you can even configure the patchwizard preferences to allow it to download the latest InfoBundleR12 file, run the recommended tasks and then automatically download and even merge patches identified by your filter.  Obviously you must always double check that any patches you do identify through the tool are test applied before running them on a production system.

 

For more detailed information regarding this tool and patching recommendations for eBusiness Suite please refer to the Oracle Applications Documentation Library and the support site for up to the minute patch lists.  This tool is also covered in the R12 Install, Patch and Maintain class.


Paula Elder

Paula Elder, Senior Instructor at Oracle University, explains the coding behind Oracle E-Business Suite patches and how the patchwizard tool can be applied for patch recommendsations.







Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Expert trainers from Oracle University share tips and tricks and answer questions that come up in a classroom.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today