Oracle EBS Release Support

Nadia Bendjedou 23-Apr-2024 13:01:01
Oracle EBS Release Support


Author: Nadia Bendjedou

Job Title: VP of E-Business Suite Product Strategy, Oracle

Bio: Nadia joined Oracle in 1991, and her main objective is to help customers understand the value that each release of the Oracle E-Business Suite brings to them.

If you missed the first instalment of this series, here is a link to part 1: The Continuous Innovation of Oracle EBS. In the second part of our 3-part series, we sit down with Nadia Bendjedou, VP of E-Business Suite Product Strategy at Oracle, to discuss the latest version of EBS, the importance of 12.2.7 and more.

 Q) What does it mean for our customers who are running Oracle EBS 12.2.6?

First of all, please allow me to explain the concept of the Error Correction Baseline Policy. Oracle builds and tests patches against the Error Correction Baseline, and our technology modernisation and certification assume the Error Correction Baseline. But Customers below the Error Correction Baseline are still supported. Let me elaborate using examples. 

  • For the 12.1 release, the Error Correction Baseline has been 12.1.3.
  • As of today, for the 12.2 release, the Error Correction Baseline is 12.2.3. This means that today, we build and test patches against 12.2.3 and we certify new technologies assuming 12.2.3 as the baseline. This is changing as per our announcement back in December 2022. We announced that starting 1st July 2024, the Error Correction Baseline is 12.2.7.

To answer your question directly, a customer on 12.2.6 after 1st July 2024 is “still supported”, but our patches are not automatically tested or produced for releases below 12.2.7. So, customers who are under the 12.2.7 release can still call Support and raise Support Requests (SRs). Yes, customers can still get the fixes to issues for EBS releases below 12.2.7, but they need to contact support and request the fixes, as these will not come automatically. It would be by request and as needed. We still strive to provide a great support experience. We will always let you know what the prerequisites are for any patch. Sometimes, the prerequisites can be more cumbersome than upgrading to the latest release. But, regardless, you are supported.

Having said that, we are still committed to producing the security CPU patches for 12.2.3 and beyond even after 1st July 2024. CPU patches fall under a different category, and we continue to provide these CPUs for 12.2.3 and above.

So, in short, yes, we provide you with CPU patches even below 12.2.7. Yes, we will do our best to provide you with the fix for your release, which may require a prerequisite. But your best experience will always be on our latest release, and we hope you will make that move.  

Q) So, if I am running an EBS environment below 12.2.7, what do I lose from Oracle support after July 1, 2024?

As mentioned earlier, our technology modernisation and certification assume the Error Correction Baseline. We have a couple of projects that we are working on today, namely the Database 23c certification as well as the technology modernisation (FMW 12c). These 2 technology modernisation projects will be limited to EBS 12.2.7 and above. I would stress the point that being “still supported” should not be a strategy to stay below 12.2.7, although it could be a planning consideration. For example, if you are planning a project such as a lift and shift to OCI (Oracle Cloud Infrastructure), I would say don’t stop the project in favour of updating the EBS release. But once you have finished your lift and shift to OCI, I would plan the update of EBS to the latest release being 12.2.13 today. But your strategy should not be to remain below release 12.2.7.

It is also important to note that moving from 12.2.4, 12.2.5 or 12.2.6 to 12.2.13 is a direct path update. Many customers started to believe they would go from 12.2.4 to 12.2.7 first, then to 12.2.13. That is not correct, as you can update your 12.2 from any release to the latest being 12.2.13 at any point in time. I also would like to emphasise always going for the very latest release, N, and not N-1. I know the N-1 has been a myth for many years, and some customers may still think it is the right approach. Please allow me to discourage that myth and always go for the latest release. N, today is 12.2.13.

To learn more about the Error Correction Baseline Policy, please refer to:

If you are interested in reading the third part of this series, here is a link to take you directly to the blog - Oracle EBS Investment Priorities.

At DSP, we are here to help with your EBS situation. If you still need to do that final upgrade to R12.2, check out our Oracle EBS Upgrade services. If you’ve already upgraded to R12 but are below 12.2.7, check out our Oracle EBS Updates services, or if, as Nadia mentioned, you're looking to lift and shift to OCI, take a look at our Oracle EBS Migration to OCI services. Stay around for the final part of the series, where we discuss where EBS is investing and what to expect in the future!