Upgrade Path Planner

Oracle EBS upgrade path planner: 11i, 12.0 and 12.1 to 12.2

Pick the Oracle E-Business Suite release you run today and the 12.2 Release Update Pack you are moving to. The planner lays out Oracle's documented route (database to 11.2.0.4 or later, Rapid Install, the 12.2.0 upgrade driver, Online Patching enablement, then the latest RUP with adop), what changes in the releases you cross, and a risk score, effort range and regression test plan sized to your CEMLI customizations, integrations and reports.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 16 cited sources.

1Releases
Verify with vendorRelease year not verified.
CurrentLatest RUP listed in the 12.2 documentation library in October 2026. Release date not verified.
2Landscape
What to count in Oracle EBS
customizations:
CEMLI objects: custom PL/SQL packages, views and triggers, custom tops, Forms and OAF extensions, personalizations, workflows, custom concurrent programs.
integrations:
SOA Gateway and XML Gateway services, SSO with Oracle Access Manager and OID, SOA Suite, OBIEE or other BI, external tax, WMS and CRM systems.
interfaces:
Open interface loads (AP, GL, PO, Order Import), EDI through e-Commerce Gateway, bank files, database links, scheduled extracts.
reports:
Custom Oracle Reports, BI Publisher templates, Discoverer replacements and FSG reports.
sites:
Production instances or operating unit groups you validate and cut over separately.
Modules in use
Integration types
Release 12.1.x (12.1.1 to 12.1.3)12.2.15 (latest RUP)

Direct upgrade: Oracle supports 12.0 and 12.1 straight to 12.2 with no intermediate release. Database to 11.2.0.4 or later, Rapid Install, the 12.2.0 driver, Online Patching enablement, then the latest AD/TXK and RUP with adop.

Steps
17
1 to confirm
Releases crossed
4
Release 12.2
Risk
64 / 100
High
Effort
266-687 d
about 13-34 person-months
  1. 1
    PreparationDocumented

    Run several test upgrades on a clone of production

    Oracle recommends several upgrade tests on a clone of the existing system on similar hardware, especially for customized systems, to work out issues and to measure the real upgrade time. Then run a benchmark with your configuration, product mix and user load before you schedule production downtime.

    Source 1Source 5
  2. 2
    PreparationDocumented

    Check for products not offered in 12.2

    Daily Business Intelligence (DBI), Balanced Scorecard (BSC) and Embedded Data Warehouse (EDW) are not offered with Release 12.2. Customers still using Oracle Student System (IGS) or Oracle Student Recruiting (IGR) should not upgrade. Plan replacements for any reporting built on DBI or EDW.

    Source 2Source 6
  3. 3
    UpgradeDocumented

    Upgrade the database to 11.2.0.4 or higher

    Release 12.2 requires the database at minimum version 11.2.0.4. You can upgrade the database before the upgrade downtime, which removes a step from the outage. Enabling TLS 1.2 only requires database 12.1.0.2. Follow MOS Doc ID 1349240.1 (Database Preparation Guidelines for a Release 12.2 Upgrade).

    Source 1Source 5Source 4
  4. 4
    PreparationDocumented

    Inventory customizations and clear Online Patching readiness violations

    Compile an inventory of database, application tier and technology customizations (OAF, Forms, Reports, Java, PL/SQL). Apply the Online Patching Readiness and GSCC Report patch with adpatch and run ADZDPSUM.sql (repeat until no further EBR violations in dependent schemas), ADZDPMAN.sql (violations you must fix before enablement) and ADZDPAUT.sql (fixed automatically, information only). Registering custom schemas fixes many violations; never register SYS, SYSTEM or CTXSYS. Customized seeded concurrent programs, menus and value sets are not supported and are overwritten by the upgrade.

    ADZDPSUM.sqlADZDPMAN.sqlADZDPAUT.sqlADZDPCUST.sqlSource 7Source 3Source 6
  5. 5
    PreparationDocumented

    Meet the EBS_SYSTEM schema standards for custom objects

    Release 12.2 adopts the EBS System Schema (EBS_SYSTEM) so that no EBS-owned objects need to reside in SYS or SYSTEM. Custom code must meet the mandatory compliance requirements before the completion patch, or custom objects become invalid. See MOS Doc IDs 2755875.1 and 1577661.1.

    Source 3Source 7
  6. 6
    PreparationDocumented

    Move external integrations to 12.2-certified releases

    External integrations must be on releases certified with 12.2 before the upgrade: OSSO 10g to Oracle Access Manager 11g, OID 10g to OID 11g, BPEL 10g to SOA Suite 11g, OBIEE 10g to 11g, ODI 10g to 11g, Oracle Portal to WebCenter Portal 11gR2. If you used XML Gateway web services or Integrated SOA Gateway, install SOA Suite before the upgrade. Third-party integrations may need changes to meet the 12.2 standards (MOS Doc ID 1916149.1).

    Source 7
  7. 7
    ValidationDocumented

    Run the EBS 12.2 Upgrade Readiness Checker (EURC-DT)

    EURC-DT checks that the critical system administration and pre-upgrade technical steps are done. It works from any previous release, on databases 11gR2, 12cR1 and 19c, on-premises or on Oracle Cloud Infrastructure. Run it during planning, every test upgrade and the production run (MOS Doc ID 2749775.1).

    EURC-DTSource 7
  8. 8
    UpgradeDocumented

    Build the stage area and create the upgrade file system

    Running buildStage is mandatory. Run rapidwiz, choose Upgrade to E-Business Suite Release 12.2.0 and Create Upgrade File System. Rapid Install creates the full run file system (fs1) and only the context file and mandatory directories on the patch file system (fs2); the complete patch file system is created later by fs_clone. Enter the database language and character set of the database being upgraded.

    buildStagerapidwizSource 8Source 4
  9. 9
    UpgradeDocumented

    Upgrade the database objects to 12.2.0

    Enable maintenance mode, apply the AD upgrade patch for 12.2 (patch 10117518) and the 12.2.0 Consolidated Upgrade Patch in pre-install mode, merge the pre-install drivers with u10124646.drv using admrgpch into u_merged.drv, and apply it with AutoPatch. Then run rapidwiz again with Configure Upgraded Release 12.2.0 Instance. Do not start application tier services until a certified RUP is applied.

    adpatchadmrgpchrapidwizAutoConfigSource 8Source 1
  10. 10
    ConversionDocumented

    Enable Online Patching

    Run ETCC (patch 17537119) and the readiness reports again, check free space (at least 25 GB in SYSTEM and 5 GB in APPS_TS_SEED), stop all application tier services and apply the enablement patch 13543062:R12.AD.C with adpatch hotpatch mode. It may run for several hours; never skip a failed worker. Recompile invalid objects, then rerun the readiness reports and the ADZDDBCC.sql compliance checker.

    ETCCadpatchADZDSHOWDDLS.sqlADZDDBCC.sqlSource 8
  11. 11
    ConversionDocumented

    12.1.3 on a multitenant database: save the PDB state

    If you upgrade from 12.1.3 on a multitenant (CDB and PDB) database, run txkSavePDBState.pl from the database tier after the AD and TXK patchsets, and set the Database SID in Rapid Install to the EBS PDB name.

    txkSavePDBState.plSource 8Source 4
  12. 12
    ConversionDocumented

    Register custom schemas with adsplice only after AD/TXK Delta 5

    For 12.0 and 12.1 upgrades with custom applications, do not run adsplice at the 12.2.0 level. Upgrade to R12.AD.C.Delta.5 and R12.TXK.C.Delta.5 or higher first (MOS Doc ID 1577707.1).

    adspliceSource 8
  13. 13
    UpliftDocumented

    Apply the latest AD and TXK RUPs, then the latest 12.2 RUP with adop

    From this point every patch is applied with AD Online Patching (adop). Apply the latest AD and TXK Release Update Packs, then the latest 12.2 Release Update Pack, following MOS Doc ID 1583092.1. Release 12.2.3 or later is required for production use, and Oracle recommends planning for the latest RUP.

    adopSource 8Source 1Source 5Source 9
  14. 14
    ConversionDocumented

    Post-upgrade steps, concurrent programs and SLA history

    Complete the mandatory post-upgrade steps of the RUP, then the product tasks for Financials, Procurement, HR, Projects and SCM. Isolate the post-upgrade concurrent programs to a separate manager queue. Historical 11i accounting data not upgraded into Subledger Accounting can be upgraded later with the XLAONDEUPG program.

    XLAONDEUPGSource 8Source 6
  15. 15
    ConversionDocumented

    Redeploy custom code and integrations to the 12.2 standards

    Deploy custom code, external integrations and third-party integrations after the latest code level. Do not deploy custom applications into the EBS technology stack. In later patching cycles, customizations are applied to the patch edition during the adop apply phase; configuration changes made on the run edition during a cycle are lost at cutover.

    Source 5Source 3Source 11
  16. 16
    UpgradeDocumented

    Plan the move to Oracle Database 19c or 26ai

    Oracle strongly recommends upgrading to Oracle Database 26ai or 19c after the upgrade to Release 12.2 is complete, using the interoperability notes (MOS Doc IDs 2552181.1 for 19c and 2962871.1 for 26ai). Treat it as its own test cycle.

    Source 4
  17. 17
    CutoverVerify with vendor

    Rehearse, freeze and cut over

    Time the full run on a clone with production-sized data at least twice, agree a freeze window, close periods and clear interfaces as the product tasks require, then run, validate and reconcile key balances before users return.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the Oracle EBS upgrade planner

  1. 1

    Pick your releases

    Choose your current EBS release (11.0, 11i, 12.0, 12.1 or a 12.2 RUP) and the target 12.2 RUP, on-premises or on Oracle Cloud Infrastructure.

  2. 2

    Describe your landscape

    Enter counts for customizations, integrations, interfaces, custom reports, database size, users and separately validated instances, then tick the modules and integrations you use.

  3. 3

    Read the path and the drivers

    Review each step with its Oracle source, the changes in every release you cross, and the drivers behind the risk score and effort range.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Critical tests are flagged where your path changes that area.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of Oracle E-Business Suite?

Release 12.2. Oracle named 12.2 the long-term support release in June 2018 and ships new capability as Release Update Packs (RUPs) on 12.2 instead of a new major release. The latest RUP listed in the 12.2 documentation library in October 2026 is 12.2.15 (readme MOS Doc ID 3072818.1). Oracle has extended Premier Support for 12.2 through at least 2037.

Can I upgrade from Oracle EBS 11i directly to 12.2?

Yes, from 11.5.10.2 (11.5.10 CU2 with the minimum patches for Sustaining Support). Oracle's 11i to 12.2 upgrade guide uses a repackaged Rapid Install for a direct upgrade with no 12.0 or 12.1 hop. From 11.0 or 11.5.1 to 11.5.9 you first patch or upgrade to 11.5.10.2. You also need the 11i.AD.I.7 minipack and Multiple Organizations enabled.

Can I upgrade from 12.1.3 to 12.2.15 in one project?

Yes. Oracle supports direct upgrades from 12.0 and 12.1 to 12.2. The route is: database to 11.2.0.4 or later, Rapid Install to create the upgrade file system, the 12.2.0 upgrade driver with AutoPatch, Online Patching enablement, then the latest AD and TXK RUPs and the latest 12.2 RUP with adop. Oracle requires 12.2.3 or later for production and recommends planning for the latest RUP.

What does online patching change for our customizations?

From 12.2, adop patches a copy of the system (the patch edition and patch file system) while users work, and only cutover needs a short downtime. Custom objects must comply with the Edition-Based Redefinition rules: run ADZDPSUM.sql, ADZDPMAN.sql and ADZDPAUT.sql before enablement and ADZDDBCC.sql afterwards. Customizations are applied to the patch edition during the apply phase. Customized seeded concurrent programs, menus and value sets are overwritten by the upgrade.

Which database version does EBS 12.2 need?

The upgrade requires at least Oracle Database 11.2.0.4, and you can do the database upgrade before the EBS downtime. Enabling TLS 1.2 only needs 12.1.0.2. Oracle strongly recommends moving to Oracle Database 19c or 26ai after the EBS upgrade, following the interoperability notes MOS Doc ID 2552181.1 (19c) and 2962871.1 (26ai).

How long does an Oracle EBS 12.2 upgrade take?

Oracle's guidance is to run several test upgrades on a clone with similar hardware to find your real downtime before you schedule production. Project length depends mostly on the number of customizations, integrations and reports. The planner shows a person-day range with the formula behind each line so you can see which inputs move it.

How should we test an EBS upgrade, and what should we automate?

Run regression on a clone: platform tests (responsibilities, Multi-Org access, invalid objects, concurrent managers, custom programs, reports), the business flows you use (procure to pay, order to cash, record to report), and every interface with saved production files. On 12.2 every RUP and every online patching cycle repeats the same regression, so the tests marked for automation pay back each cycle. The planner flags tests as critical where your path changes that area.

Can we upgrade and move to Oracle Cloud Infrastructure at the same time?

Oracle's 12.0 and 12.1 to 12.2 guide documents upgrading an existing 12.1.3 instance to 12.2 on OCI, and EURC-DT supports OCI database services. From other sources, plan to upgrade first and move afterwards, and confirm the tooling with Oracle. EBS on OCI is the same software, so customizations carry over; Fusion Cloud ERP is a different product and a reimplementation, not an upgrade.

Sources

  1. Oracle: E-Business Suite Upgrade Guide, Release 11i to 12.2: overview and supported paths
  2. Oracle: Upgrade Guide 11i to 12.2: upgrade impact and changes
  3. Oracle: Upgrade Guide 11i to 12.2: pre-upgrade tasks
  4. Oracle: Upgrade Guide 11i to 12.2: performing the upgrade
  5. Oracle: Upgrade Guide, Release 12.0 and 12.1 to 12.2: overview
  6. Oracle: Upgrade Guide 12.0 and 12.1 to 12.2: upgrade impact and changes
  7. Oracle: Upgrade Guide 12.0 and 12.1 to 12.2: pre-upgrade tasks
  8. Oracle: Upgrade Guide 12.0 and 12.1 to 12.2: performing the upgrade
  9. Oracle: E-Business Suite Documentation Web Library Release 12.2 (RUP readmes and release notes)
  10. Oracle: EBS Concepts, file system structure (dual file system)
  11. Oracle: EBS Maintenance Guide, patching procedures (adop phases)
  12. Oracle: EBS 12.2 Premier Support extended through at least 2037
  13. DSP: EBS 12.2 Premier Support extended through at least 2036
  14. OATUG: the future of Oracle E-Business Suite (June 2017)
  15. IT Convergence: Oracle support levels, Premier, Extended, Sustaining
  16. Wikipedia: Oracle E-Business Suite (Release 12, February 2007)

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.