Oracle E-Business Suite 12.2 is the most tenacious on-premise ERP product in Oracle's portfolio. Its online patching capability (adop) — introduced with Release 12.2 — eliminated the need for downtime windows during patching, making EBS 12.2 a credible on-premise platform for organisations that needed to defer cloud migration indefinitely. Oracle has extended Premier Support for EBS 12.2 multiple times — currently to December 2031 — in recognition of the fact that the installed base of 20,000+ EBS 12.2 customers is simply not migrating to Oracle Fusion Cloud Applications at the pace Oracle's revenue model demands.
What Oracle account teams do not volunteer when discussing the EBS 12.2 roadmap: Extended Support surcharges begin after Premier Support ends, and Oracle Fusion Cloud Applications migration projects carry a real cost of £2M–£20M+ in system integrator fees, data migration, and business process re-engineering. Third-party support on Oracle EBS 12.2 — available on all active Release Update Packs (RUPs) — eliminates Oracle's 22% annual Support and Updates Licence fee (SULS) entirely, delivering 50–64% saving from year one without touching your ERP application or forcing a migration decision under Oracle deadline pressure.
Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle EBS 12.2 Premier Support: Active through December 2031. Extended Support (paid surcharge): Available January 2032–December 2033 (subject to Oracle confirmation). Sustaining Engineering: Indefinite — but no new patches, no new regulatory updates, no new country localisation, and no new certifications. Third-party support provides a materially better support proposition than Oracle's own Sustaining Engineering phase, at approximately 60% lower cost than Premier Support SULS. The relevant question is not "when does Oracle support end?" — it is "what am I actually receiving from Oracle Support that justifies 22% of NLV today?"
The Oracle Fusion Cloud Migration Pressure — What It Actually Costs
Oracle's account motion for EBS 12.2 customers follows a predictable pattern: present Oracle Fusion Cloud Applications (Oracle Cloud ERP) as the inevitable destination, signal that EBS 12.2 roadmap investment is declining, emphasise the integration benefits of Oracle Cloud (SaaS + PaaS + OCI infrastructure), and time the Fusion pitch to coincide with EBS renewal negotiations to maximise leverage.
The actual cost of migrating from EBS 12.2 to Oracle Fusion Cloud ERP for a mid-market enterprise (500–2,000 users, 5–8 EBS modules active) runs £2M–£7M in system integrator fees alone — before Oracle Cloud subscription costs, before data migration, and before the business process re-engineering required to accommodate Fusion's standardised process model (which does not support the same level of custom workflow that EBS 12.2 FLEXFIELDS and custom Forms enable). Our Oracle Cloud Migration Guide white paper provides the full five-year total cost model across four organisation size profiles.
Oracle EBS 12.2 RUP Patch Level Matrix — TPS Eligibility
| EBS 12.2 Release / RUP | Oracle Premier Support Status | TPS Available | Notes |
|---|---|---|---|
| EBS 12.2.0 (base release) | No — RUP required for support | ✓ Yes | RUP upgrade recommended |
| EBS 12.2.3 (RUP3) | No — superseded | ✓ Yes | Legacy cohort, large installed base |
| EBS 12.2.4 (RUP4) | No — superseded | ✓ Yes | Significant install base, banking/utilities |
| EBS 12.2.6 (RUP6) | No — superseded | ✓ Yes | Public sector and manufacturing cohort |
| EBS 12.2.8 (RUP8) | Oracle Premier Support (2031) | ✓ Yes — largest active TPS cohort | Most common active release |
| EBS 12.2.10 (RUP10) | Oracle Premier Support (2031) | ✓ Yes | Finance-module focused deployments |
| EBS 12.2.12 (RUP12) | Oracle Premier Support (2031) | ✓ Yes | Latest RUP — healthcare, FS primary cohort |
| EBS 12.2.13 (RUP13) | Oracle Premier Support (2031) | ✓ Yes | Payroll localisation updates |
What GoVendorFree TPS Covers for Oracle EBS 12.2
GoVendorFree's Oracle TPS covers all active EBS 12.2 modules under a single contract. Coverage includes the application, technology stack, and database tier where applicable:
- EBS Financials (FI): General Ledger (GL), Accounts Payable (AP), Accounts Receivable (AR), Fixed Assets (FA), Cash Management, Treasury, and Advanced Global Intercompany System (AGIS) — including Multi-Org configurations and Primary Ledger / Secondary Ledger setups
- EBS Supply Chain Management: Purchasing (PO), Inventory Management (INV), Order Management (OM/ONT), Manufacturing (WIP, BOM, MRP/ASCP), and Quality Management — including configurator (CZ) and service contracts (OKS)
- EBS Human Capital Management (HCM): Oracle HRMS (Core HR, Payroll, Absence Management, Self Service HR), iRecruitment, Learning Management, and Time & Labour — including country-specific localisation payroll support for UK, Germany, France, Australia, and US
- EBS Projects: Oracle Projects (PA), Project Costing, Project Billing, Project Resource Management, and integration with Primavera P6 for project-driven organisations
- EBS Technology Stack: Oracle Forms 6i/10g/11g/12c, Oracle Reports, Oracle Application Framework (OAF), Workflow (WF), XML Publisher/BI Publisher, and AD/TXK patching alternatives for technology stack patches
- Online Patching (adop): Support for EBS 12.2 online patching cycles — patching edition configuration, fs_clone and fs_upgrade operations, and cutover failure diagnosis
- Oracle Database Integration: Oracle Database 12c/19c under EBS 12.2 — RDBMS support for the EBS application tier where database issues arise from EBS-DB interaction (covered under Oracle Database TPS)
Oracle EBS Customisations and TPS — The Boundary Question
Oracle EBS 12.2 customisation depth varies significantly across the installed base. The E-Business Suite customisation framework — FLEXFIELDS, custom Forms (OAF), workflow modifications, custom database packages, and seeded process extensions — enables a high degree of configuration. Under Oracle's standard support policy, customisations are explicitly excluded from Oracle Support scope: Oracle will not debug custom code, will not support custom database packages, and will not diagnose issues that are isolated to customer-specific extensions.
Third-party support maintains this same boundary clearly: TPS covers the standard Oracle EBS application code, the technology stack components, and the Oracle Database tier. Custom code is customer-owned and customer-supported — the same position as under Oracle support, with the same practical implication. What TPS adds, that Oracle Sustaining Engineering does not, is continued proactive security advisory and interoperability guidance for the customisation layer — helping organisations understand how Oracle security patches would interact with their custom Forms and packages, without mandating that they apply Oracle patches on Oracle's schedule. See our Oracle EBS third-party support overview for the full customisation handling framework.