The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

Distinguishing Between E-Business Suite 12.1 and 12.0 Patches

Steven Chan
Senior Director

Sometimes our release processes get ahead of our internal infrastructure.  This happened when we released Oracle E-Business Suite Release 12.1.1.  We discovered post hoc that it was not possible to distinguish between patches intended for Apps 12.1 and those intended for Apps 12.0 in the "Patches & Updates" function in My Oracle Support and Metalink.  Whoops -- clearly suboptimal.

This issue was resolved in mid-July, when the Patches & Updates function got a brand-new "Compatible With" column:  


The new "Compatible With" column clearly distinguishes between the patches for each Release 12 codeline now.

Don't Mix and Match R12.0 and R12.1 Patches

This distinction is important.  You shouldn't attempt to apply an R12.1 patch against your R12.0 instance, or vice versa.  If you tried to do that, you'd see a somewhat-cryptic error message like this:

AutoPatch error: This patch is not compatible with your current codelines. This patch is compatible with: entity 'gl' - codeline 'R12.GL.A'. Your current on-site codeline for the entity 'gl' is: 'R12.GL.B'. You should not apply this patch. Apply an equivalent patch that is compatible with your current codelines instead.
Sorting Patches Out After They've Been Downloaded

It's now easy to tell patches apart on the "Patches & Updates" download screen, but how can you tell them apart after they've been downloaded?  It's pretty simple. You can identify the codeline for a given patch by the letter in the third-digit:

  • Patches for EBS 12.0 will show an 'A' (e.g. "8414069.R12.AR.A")
  • Patches for EBS 12.1 will show a 'B' (e.g. "8414069.R12.AR.B")
For more tips about telling these patches apart, see:

Join the discussion

Comments ( 4 )
  • Ramnik Gupta Wednesday, August 26, 2009


    I had similar issue with R12.1.1 after upgrade for post patches. when I applied R12.0 codeline patch on R12.1.1 it failed with similar error.

    I clarify about the patch with Oracle support by opening an SR. Support suggested to dowload the R12.1.1 codeline (.B) patches and apply.


    Ramnik Gupta

  • Steven Chan Wednesday, August 26, 2009

    Hi, Ramnik,

    Thanks for your comment. I'm sorry to hear that you encountered this issue, but I'm pleased that Support was able to help you straighten this out.



  • Madhu Akella Wednesday, June 9, 2010

    Hi Steve,

    Are we supposed to apply ATG_PF.H.RUP7 to 11i environment prior to upgrading to Release 12.1.x? We are currently on RUP6 on and are planning for our R12 upgrade and are interested in knowing if it is a pre-requisite step. I haven't found any documentation to that effect.



  • Steven Chan Thursday, June 17, 2010

    Hi, Madhu,

    I'm afraid that I'm not really up to speed on the EBS 12.1.x upgrade prereqs, so I can't comment authoritatively on this. If you can't locate this in our upgrade documentation, your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

    Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.



Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.