Oracle EBS roadmap planner: stay on 12.2, move to OCI or Oracle Cloud ERP
For Oracle E-Business Suite owners deciding what happens next. Describe your release, database, modules, CEMLIs, integrations and team, and the planner compares four paths: stay on 12.2 and modernize, re-platform to OCI, move to Oracle Fusion Cloud ERP, or keep EBS and add Fusion modules. Every score and number shows the reasoning behind it, and every cost is yours to enter.
No vendor prices and no sales pitch: every cost is your own number, and every score shows its reasons.
Facts the plan rests on
Checked against Oracle documentation on 2026-10-22. Support dates are Oracle statements that can change; confirm them against your contract.
- EBS 12.2 Premier Support
- Oracle states Premier Support for 12.2 runs through at least 2037 and is reviewed annually for another year. Confirm in the current Lifetime Support Policy. Oracle: EBS 12.2 Premier Support extended through at least 2037 (announcement PDF)
- Latest 12.2 release in the documentation library
- 12.2.15 (Release 12.2.15 Readme, My Oracle Support Doc ID 3072818.1). Oracle E-Business Suite Documentation Web Library, Release 12.2 (lists the 12.2.15 Readme, Doc ID 3072818.1)
- Direct upgrade paths to 12.2
- Oracle supports direct upgrades from 12.0 and 12.1 to 12.2, and publishes a separate 11i to 12.2 upgrade guide. Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2: Overview of the Upgrade
- Minimum database for a 12.2 upgrade
- 11.2.0.4. Doc ID 1349240.1 has the database preparation steps for your instance. Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2: Overview of the Upgrade
- Oracle Database 19c with EBS
- The 12.2 upgrade guide covers 19c, where EBS runs in a pluggable database (multitenant). Check Certify on My Oracle Support for later database releases. Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2: Performing the Upgrade
- Online patching downtime
- adop phases are prepare, apply, finalize, cutover, cleanup. Only cutover involves a brief downtime. Oracle E-Business Suite Maintenance Guide, Release 12.2: Patching Procedures (adop phases)
- Online patching readiness
- ADZDPSUM.sql, ADZDPMAN.sql, ADZDDBCC.sql and gscc.pl must report no exceptions in custom code before online patching is enabled (Doc ID 1531121.1). Oracle E-Business Suite Developer's Guide, Release 12.2: Preparing for Online Patching
- Custom code standards for 12.2
- Doc ID 1577661.1, Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2. Oracle E-Business Suite Developer's Guide, Release 12.2: Preparing for Online Patching
- Database block size
- EBS 12.2 requires an 8K database block size. Oracle E-Business Suite Concepts, Release 12.2: Database Features (Edition-Based Redefinition)
- Fusion Cloud ERP updates
- Fusion Cloud Applications are released as named updates (for example 26C). Oracle applies them to test before production on a published calendar; verify your pod's dates with Oracle. Oracle Cloud Applications Readiness: ERP, update 26C
Describe your EBS estate
Defaults are a typical 12.1.3 estate so the results are not empty. Replace them with yours.
Past Premier Support and in Sustaining Support: no new security fixes or new certifications. Verify the exact dates in the Lifetime Support Policy.
Supported in the 12.2 upgrade guide. Plan the move to 19c, which changes the database to multitenant (CDB with an EBS PDB).
Hardware refresh dates and data center contracts are often the real deadline. Note them in the cost model.
Drives subscription quotes and training; enter what your license reports show.
Include contractors. Under 1.5 FTE is a key person risk.
Banks, MES, WMS, CRM, EDI hubs, data warehouse. Each has a second end to change.
Modules in use
Hover or tap to see the nearest Oracle Cloud area. Verify product scope with Oracle and in the fit-gap worksheet.
Customizations by CEMLI type
Counts are enough to start. The worksheet in step 5 takes individual objects.
Custom Forms, OAF pages and controllers, custom concurrent programs, custom schemas and tables
Changed seeded packages, forms, workflows or views; triggers on Oracle tables
Statutory reports, tax engines, e-invoicing, country bank formats
Open interface loads, PL/SQL APIs, DB links, file drops, SOA or Integrated SOA Gateway services, EDI
Oracle Reports, BI Publisher templates, Discoverer, custom Workflow and AME rules, alerts
What each type means on 12.2 and on Fusion
| Type | On 12.2 (online patching) | On Fusion Cloud ERP |
|---|---|---|
| Extensions | Custom tables need editioning views and APPS synonyms; custom schemas must be registered. ADZDPMAN.sql lists what to fix by hand. | No custom Forms or database objects in the Fusion schema. Rebuild as Visual Builder or OCI PaaS extensions, or replace with standard features. |
| Modifications | Highest risk in 12.2: changes to seeded code are overwritten by patches and many violate online patching standards. Move them to extensions or personalizations. | Not possible in SaaS. Each one is replaced by standard features, configuration or a PaaS extension. |
| Localizations | Mostly reports and interfaces; retest after every RUP. Check whether Oracle now ships the requirement. | Check Oracle's country localizations and tax partner integrations first. Gaps become partner products or PaaS. Verify country coverage with Oracle. |
| Interfaces and integrations | Anything that writes to EBS must go through APPS synonyms and avoid DDL on the run edition. DB links and direct table writes need review. | No direct database access. Inbound becomes REST or FBDI loads, outbound becomes BI Publisher, BICC extracts or events, usually through an integration platform. |
| Reports and workflows | Low code risk, high test volume. Discoverer is desupported for EBS; plan its replacement in any path. Verify with Oracle. | Rebuild in OTBI or BI Publisher on Fusion data. Approvals move to Fusion approval rules. Many reports retire once standard analytics exist. |
What hurts and what binds you
Each tick moves the scores by the points shown in the reasons. Nothing is hidden.
Pain points
Constraints
1: we need to control every change. 5: we will test and adopt new features every quarter. Fusion moves you onto Oracle's update calendar.
Hybrid: areas to move to Oracle Cloud first
Options compared
Fit starts at 50 and moves by the listed reasons. Effort is person-days from your counts and the assumptions in step 6.
Fit score (0 to 100)
Effort (person-days)
Hybrid: EBS core plus Fusion modules
Keep EBS for operations (manufacturing, order to cash, supply chain) and move selected areas to Oracle Cloud first: HCM, EPM, procurement, planning or the ledger.
| Base score | 50 |
| 165 customizations stay in EBS | +2.1 |
| 1 areas chosen to move first | +3.5 |
| Fit (clamped to 0 to 100) | 56 |
The score ranks paths for your inputs; it is not a prediction of success. Read it with the triggers below.
Triggers that flip the decision
- If you lose your DBA and apps DBA staff:Move to Oracle Fusion Cloud ERP leads
- If you retire three quarters of the customizations:Move to Oracle Fusion Cloud ERP leads
- If you reach the current 12.2 code level first:Stay on 12.2 and modernize leads
- If "Hard to hire or keep EBS and apps DBA skills" becomes a pain:Move to Oracle Fusion Cloud ERP leads
- If "Hardware or data center refresh due" becomes a pain:Re-platform to OCI leads
- If "Patching and upgrades take too long" becomes a pain:Move to Oracle Fusion Cloud ERP leads
- If "Run cost is too high" becomes a pain:Re-platform to OCI leads
- If "Data must stay in our own data center" starts to apply:Stay on 12.2 and modernize leads
Gap between first and second: 8 points. Under 10 points, treat the two as a tie and let the cost model and a fit-gap decide.
5-year cost model, your numbers
Enter annual figures from invoices and quotes. Nothing here is a vendor price; leave a field empty if it does not apply.
Internal plus partner, per person-day.
From your Oracle support renewal.
Database, RAC and options used by EBS.
Servers, storage, DC, DR, backup, hosting fees.
Applied in month 1 to stay and hybrid.
Compute, database service, storage, network, all environments.
For 300 users and the modules ticked. Ask for renewal caps.
Fusion and hybrid only.
After leaving EBS: audit and history access.
Months EBS keeps running in parallel.
Check your contract's rules for partial termination; verify with Oracle.
From go-live. Negative means fewer.
From go-live. Negative means fewer.
From go-live. Negative means fewer.
From go-live. Negative means fewer.
Enter at least one number above and the 5-year comparison, cumulative chart and per-line formulas appear here.
CEMLI disposition worksheet
Retain, replace with standard, rebuild as a PaaS extension, or retire, object by object.
When the worksheet has items, its dispositions replace the counts in the effort for this path only.
Retain (0)
Keep as is on the target path; fix only what online patching or the new platform requires.
Effort factor 0.6
Replace with standard (0)
Drop the custom object and use a standard feature or configuration; effort moves into testing and change management.
Effort factor 0.8
Rebuild as PaaS extension (0)
Rebuild outside the core: Visual Builder, OCI functions, an integration platform, or an EBS extension that follows 12.2 standards.
Effort factor 1.2
Retire (0)
No longer needed. Confirm with the owner and archive the output before switching it off.
Effort factor 0.05
No objects yet. Add rows from your counts above, or add them one at a time below. Name them as in your inventory (for example XXAR_INVOICE_EXTRACT).
How to decide each disposition
- Start with usage. Pull concurrent request history (FND_CONCURRENT_REQUESTS) for the last 12 to 18 months before purging. Reports nobody ran are retire candidates.
- Modifications first. Each change to seeded code is a patch risk on 12.2 and impossible in SaaS. Ask whether a newer standard feature, a personalization or an extension does the job.
- Interfaces by direction. Inbound loads become REST or FBDI on Fusion; outbound extracts become BI Publisher, BICC or events. Count both ends, including the other system's change.
- Localizations by country. Check what Oracle now delivers for each country before you rebuild anything; verify coverage with Oracle.
- Retire needs a sign-off. Record the business owner and archive the last output before switching anything off.
Planning assumptions
Starting values for a first estimate, not benchmarks. Replace them with your partner's estimates or your own history.
| Person-days per object | Stay on 12.2 | Move to OCI | Fusion Cloud ERP | Hybrid |
|---|---|---|---|---|
| Extensions | ||||
| Modifications | ||||
| Localizations | ||||
| Interfaces and integrations | ||||
| Reports and workflows | ||||
| Per connected system |
Technical upgrade, RUP, AD/TXK, before CEMLI work.
Configuration days per module (Fusion and hybrid)
Fusion Financials: General Ledger
Fusion Financials: Payables
Fusion Financials: Receivables
Fusion Financials: Assets
Fusion Financials: Cash Management
Fusion Procurement
Fusion SCM: Inventory Management
Fusion SCM: Order Management and Pricing
Fusion SCM: Manufacturing and Cost Management
Fusion SCM: Process Manufacturing
Fusion SCM: Supply Planning and Demand Management
Fusion SCM: Inventory Management and Oracle WMS Cloud
Fusion Maintenance
Fusion Project Management and Project Financials
Fusion HCM (Global HR, Payroll)
Oracle EPM Cloud
Upgrade to 12.2 checklist
0 of 21 done. Online patching readiness and custom code standards come first.
Plan
Database
Custom code
Online patching
Technology stack
Test
Cutover
Paths this planner does not score
Third-party support
Some owners freeze EBS on a third-party support contract. It lowers run cost but ends access to Oracle patches, RUPs and new certifications, and any later return to Oracle support may carry back fees. Model it as stay with no upgrade path and price the exit before you sign.
A different ERP
Moving to a non-Oracle ERP is the same shape as the Fusion path (re-implementation, data conversion, rebuilt integrations) with a different license and partner model. Use the Fusion column as the template and replace the subscription numbers with your quotes.
Do nothing on 12.1 or 11i
Running on Sustaining Support means no new security fixes and no new certifications for operating systems, browsers or databases. The risk grows each quarter; record it explicitly with your auditors if this is the choice.
An on-prem AI layer works on every path
Assistants for AP exceptions, order status, concurrent request triage or SQL over read-only views can run beside EBS on your own hardware, with no change to EBS and no data leaving your network. On Fusion the same layer reads REST APIs and extracts. Size it before you commit to a path, because it changes which pains remain.
Notes, export and review
How to use the Oracle EBS roadmap planner
- 1
Describe the estate
Pick your current release and database, tick the modules in use and enter counts of customizations by CEMLI type. Counts are enough to start; the worksheet below takes individual objects when you have the inventory.
- 2
Say what hurts and what binds you
Tick pain points (skills, infrastructure age, reporting, close cycle) and constraints (data residency, validated systems, change freeze windows). Set your appetite for the quarterly update cadence of a SaaS product.
- 3
Read the comparison and the triggers
Each path gets a fit score with the contributions listed line by line, plus effort in person-days. The trigger list shows which single change to your inputs would flip the recommendation.
- 4
Enter your own numbers
Type in your current support, infrastructure and staff costs, the quotes you have for OCI or Fusion subscriptions, and a blended services rate. The five-year model shows the formula for every line.
- 5
Dispose of each CEMLI and run the checklist
Mark each customization as retain, replace with standard, rebuild as a PaaS extension or retire. If you are below 12.2, work through the upgrade checklist, starting with the online patching readiness reports.
- 6
Export, save or ask for a review
Download PDF, Excel, Word or CSV for the steering committee, save to your free Netray account, or send the result to an engineer for a second opinion.
Questions
How long is Oracle EBS 12.2 supported?
Oracle states that Premier Support for E-Business Suite 12.2 runs through at least 2037, and that it reviews each year whether to extend it by another year. That commitment applies to 12.2 on its continuous innovation model; 12.1 and earlier releases are in Sustaining Support. Check the current Oracle Lifetime Support Policy for your contract before you plan around a date.
Do we have to move from Oracle EBS to Fusion Cloud ERP?
No. On 12.2 at a current code level, staying is a supported choice. The move is driven by your pains (skills, hardware, reporting, close) and constraints (residency, validation, customizations), which is what the planner scores. A hybrid start with HCM, EPM, procurement or planning is common when operations are stable.
What is the difference between Oracle Fusion and Oracle EBS?
EBS is an on-premises or self-hosted application you patch and customize, with full database access. Fusion Cloud ERP is SaaS: Oracle runs it and applies quarterly updates, you cannot modify Oracle code or query the database directly, and extensions run outside the core. Moving is a re-implementation, not an upgrade.
What are CEMLIs and why do they drive the decision?
CEMLI is common shorthand for the custom objects in an Oracle estate: configurations, extensions, modifications, localizations and integrations; this planner splits them into extensions, modifications, localizations, interfaces, and reports with workflows. Modifications to seeded code are the expensive ones on every path: they break online patching on 12.2 and are not allowed in Fusion.
What does online patching mean for our custom code?
EBS 12.2 uses Edition-Based Redefinition and a dual file system so patches apply while users work; only the cutover phase has downtime. Custom code must follow the 12.2 standards in My Oracle Support Doc ID 1577661.1, and the readiness reports (ADZDPSUM, ADZDPMAN, ADZDDBCC and gscc.pl) must be clean before online patching is enabled.
Is moving EBS to OCI the same as moving to the cloud?
It moves infrastructure, not the application. You keep EBS, your licenses (subject to Oracle's rules for your contract) and your customizations, and you still patch and support the application. It is often used to meet a hardware deadline and buy time before a Fusion decision.
Why does the planner not show Oracle prices?
Fusion Cloud ERP subscriptions and OCI estates are priced by contract, metric and discount, so any number we printed would be wrong for you. The cost model takes the numbers from your quotes and invoices and shows the formula for each line, so the comparison is only as good as the inputs you put in.
Which database versions can EBS 12.2 use?
The 12.2 upgrade guide requires at least 11.2.0.4 to upgrade and documents 12.1.0.2 and 19c, where EBS runs in a pluggable database. Check the Certify tab on My Oracle Support for later database releases and your operating system before planning beyond 19c.
Can we add AI to Oracle EBS without moving to the cloud?
Yes. Retrieval and agent layers can sit beside EBS on your own hardware and read through APIs and read-only database views, with no change to EBS itself. The on-prem AI architecture builder sizes the models, GPUs and connectors for that layer.
Related Oracle EBS resources
- Oracle EBS 12.2 upgrade readiness checklistA shorter checklist for the upgrade project kick-off.
- Oracle Fusion vs EBS migration fit-gap worksheetRequirement by requirement fit-gap for the Fusion path.
- EBS module to Oracle Cloud product referenceWhich Fusion product replaces each EBS module.
- Oracle EBS custom code inventory worksheetBuild the CEMLI inventory this planner needs.
- EBS adop patch cycle downtime calculatorEstimate cutover downtime for each patching cycle.
- Oracle Fusion quarterly update test checklistWhat the quarterly SaaS cadence asks of your team.
- Oracle EBS instance health assessmentBaseline the instance before you decide.
- Fusion SCM terminology vs EBSWork definitions, cost books and other renamed concepts.
- CIO guide: stay on EBS 12.2 or move to Fusion
- EBS adop patching cycle on R12.2
- Fusion Visual Builder sandbox extensions
- Oracle EBS AI integration on premises
- ERP customization vs extension
- On-prem AI architecture builderSize an AI layer that runs beside EBS on your hardware.
Everything for Oracle E-Business Suite
Guides, reference tables, troubleshooting and tools in one hub.
Open the Oracle EBS hubSources
Product facts in the planner were checked against these pages on 2026-10-22. Versions differ; verify against the documentation for your release.
- Oracle E-Business Suite Documentation Web Library, Release 12.2 (lists the 12.2.15 Readme, Doc ID 3072818.1) (seen 2026-10-22)
- Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2: Overview of the Upgrade (seen 2026-10-22)
- Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2: Performing the Upgrade (seen 2026-10-22)
- Oracle E-Business Suite Maintenance Guide, Release 12.2: Patching Procedures (adop phases) (seen 2026-10-22)
- Oracle E-Business Suite Developer's Guide, Release 12.2: Preparing for Online Patching (seen 2026-10-22)
- Oracle E-Business Suite Concepts, Release 12.2: Database Features (Edition-Based Redefinition) (seen 2026-10-22)
- Oracle: EBS 12.2 Premier Support extended through at least 2037 (announcement PDF) (seen 2026-10-22)
- Oracle E-Business Suite Support (Oracle support page) (seen 2026-10-22)
- Oracle E-Business Suite Concepts, Release 12.2: Architecture (seen 2026-10-22)
- Oracle E-Business Suite Upgrade Guide, Release 11i to 12.2 (seen 2026-10-22)
- Oracle Cloud Applications Readiness: ERP, update 26C (seen 2026-10-22)
- Oracle Fusion Cloud Applications: Configuring and Extending Applications, 26C (seen 2026-10-22)