The latest news directly from E-Business Suite Development

Distinguishing Between E-Business Suite 12.1 and 12.0 Patches

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:

Apply an equivalent patch that is compatible with yourcurrent 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:

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 11.5.10.2 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.
Regards,
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.