Oracle E-Business Suite Release 12.0 will transition from Premier Support to Extended Support
on February 1, 2012. New EBS 12.0 patches will be created and tested during Extended Support against the minimum patching baseline documented in our E-Business Suite Error Correction Support Policy
These new technical requirements have now been finalized. To be eligible for Extended Support, all EBS 12.0 customers must apply
the EBS 12.0.6 Release Update Pack, technology stack infrastructure updates, and updates for EBS products if they're shared or fully-installed. The complete set of minimum
EBS 12.0 baseline requirements are listed here:
What are the impacts of this new baseline?
Oracle Support will assist with diagnosis, triage, and debugging of any
issues that you report for your E-Business Suite environment. You will
continue to have access to any existing online support tools, knowledge
base documentation, and pre-existing fixes.
If you report a new
issue that requires a new bug fix, you should be aware that new patches
will be released only for the new baseline patches listed in the EBS
Error Correction Support Policy. You should plan to apply the
baseline updates (at minimum) listed in Note 1195034.1 by February 2011
in order to receive any new bug fixes.
What EBS 12.0 products are affected by this new baseline?
The Note lists minimum baseline update requirements for the following EBS 12.0 products (see the Note for specific patch numbers):
What about E-Business Suite technology stack components?
- Financials (Payables, Receivables, Advanced Collections, Public Sector Financials, Financials for Asia/Pacific)
- Human Resources (Payroll, US Federal HR)
- Process Manufacturing (OPM Financials, OPM Process Execution, OPM Process Execution Mobile, Inventory Converge)
- Service (Complex Maintenance, Repair & Overhaul)
Chain Planning (Engine + UI, UI Source Side, Data Collections, Global
Order Processing, Collaborative Planning, Demand Planning, Demantra)
Here are the highlights of the technology stack-related minimum baseline requirements from that Note:
- E-Business Suite 12.0.6 Release Update Pack
- Oracle Forms & Reports 10.1.2.3
- Oracle Containers for Java (OC4J) 10.1.3.5
- Oracle Database 10.2.0.5, 184.108.40.206, or 220.127.116.11
- Java 6 for server-side Java
- Sun JRE 1.6.0_03 for Windows desktops
dates for Oracle Forms & Reports, Oracle Containers for Java
(OC4J), Oracle Database, and Java are set by their respective Lifetime
Support Policies. The minimum versions listed in Note 1195034.1 may be
superseded by their respective support policies by February 1, 2012.
12.0 users must ensure that installed versions of the components above
comply with the components' respective Lifetime Support Policies listed
This also applies to
external standalone components (e.g. Oracle Single Sign-On, Discoverer,
SOA Suite) that you may have integrated with your E-Business Suite
You must also plan to update those technology
stack components on an ongoing basis. If you're interested in learning
more about the implications of Fusion Middleware and database support
windows for E-Business Suite users, see these two articles:
Ranking your upgrade options
If I were running EBS 12.0 today, I'd rank my options like this:
1. Upgrade to EBS 12.1.3
Upgrading to EBS 12.1.3
unquestionably provides the greatest return on your patching
investment. This allows you to completely avoid having to ask, "What
EBS 12.0 patches do I need to apply to reach the minimum patching
This option may be relatively more work than
simply patching EBS 12.0, but it's the most-efficient strategy in the
long-run. Moving to 12.1.3 means that you don't need to worry about
new minimum patching baselines until June 1, 2014.
2. Apply the 12.0.6 minimum baseline
Applying the 12.0.6 Release Update Pack, the latest technology stack updates, and the product-specific patches is a straightforward process. This option may require nominally less effort than upgrading
All of these updates will require retesting of all affected products. Testing is usually more time-consuming and resource-intensive than applying the patches themselves. If I was in your shoes and had to go to the trouble of testing everything again, I'd choose Option 1 rather that 2.
3. Do nothing
This is always
an option. I wouldn't recommend it. Leaving your EBS environment at
the, say, 12.0.4 level with one or two other later product family
Release Update Packs may create support problems downstream. For
example, you may report a problem that can be reproduced on 12.0.6 and the minimum baseline. Oracle will provide a patch for that issue, but you will first need to apply the minimum baseline to your 12.0 environment before applying the patch.
Getting ahead of the curve
might seem like February 1, 2012 is a long way off, but don't be
fooled. That's the temporal equivalent of an optical illusion. It's only 12 months away
. I urge you to get started on your EBS 12.0 upgrade planning immediately.