erp

Fusion Cloud ERP and quarterly updates, or another decade on Oracle E-Business Suite 12.2

Fusion Cloud ERP gets four updates a year, ready or not. E-Business Suite 12.2 has Premier Support through at least 2037, so staying put is a perfectly real option. We help teams run either one well, and move between them when there's an actual case for it.

ERP
platform dossierOracle Fusion ERP & E-Business SuiteERP
Vendor
Oracle
Fusion update cadence
Quarterly; 26D What's New published 18 Oct 2026
EBS latest release
12.2.15, announced 17 Oct 2025
EBS 12.2 support
Premier Support through at least Dec 2037
release watch
  • Fusion Cloud ERP 26D18 Oct 2026
  • EBS 12.2 Premier Support through at least Dec 203707 Aug 2026
connects with
in short·20-second read

Cohash implements Oracle Fusion Cloud ERP and supports Oracle E-Business Suite 12.2.

For Fusion we configure financials, procurement and projects, build integrations in Oracle Integration Cloud and regression-test every quarterly update before production sees it. EBS work is mostly 12.2 release update packs and keeping customizations compliant with online patching. If the business case holds, we plan the move to Fusion. Oracle lists EBS 12.2 Premier Support through at least December 2037.

you probably need this if
  • Every Fusion quarterly update triggers a scramble because nobody owns the regression pack.
  • EBS patching is two or more release update packs behind and ADOP cycles keep failing.
  • Demantra drives your demand plan and its Premier Support ends in December 2026.
Ask an engineer facts checked 2026-10-20 · 4 sources
how it runs
  1. 01Estate review
  2. 02Update or upgrade plan
  3. 03Rehearse
  4. 04Run and hand over
you keep
  • Quarterly update calendar with regression pack and owner per flow
  • EBS customization register with online patching compliance status
  • RUP and AD/TXK patch plan with timed clone rehearsal
+ 3 more documents
who does it
Oracle Fusion Financials functional consultantOracle Fusion Procurement and Projects consultantOracle Integration Cloud (OIC) developer
oracle-erp · release timeline
  1. 17 Oct 2025 EBS 12.2.15 is the latest release update Announced 17 October 2025 and listed as the latest 12.2 release in Oracle's Lifetime Support Policy. source ↗
  2. 07 Aug 2026 EBS 12.2 Premier Support through at least Dec 2037 Under Oracle's Continuous Innovation model, 12.2 gets new features through updates instead of a major upgrade. Oracle may extend the date in one-year increments. source ↗
  3. 07 Aug 2026 EBS Value Chain Planning and Demantra exception Oracle's exceptions table lists Premier Support for 12.2 Value Chain Planning and Demantra products ending December 2026, and Sales and Marketing products in December 2027. source ↗
  4. 18 Oct 2026 Fusion Cloud ERP 26D Oracle published the Financials 26D What's New on 18 October 2026. Readiness pages run 26A, 26B, 26C and 26D for 2026, one update a quarter. source ↗
  5. today · Oct 22, 2026
the story · oracle fusion erp & e-business suite estate

From the first call to a setup your own team can run.

Here's what usually prompts a call about your Oracle Fusion ERP & E-Business Suite estate, what we do about it and in which order, and where you end up.

  1. chapter 01 · where it hurts

    Why teams reach out

    • Every Fusion quarterly update triggers a scramble because nobody owns the regression pack.
    • EBS patching is two or more release update packs behind and ADOP cycles keep failing.
    • Demantra drives your demand plan and its Premier Support ends in December 2026.
  2. chapter 02 · what we change

    How we solve it

    • Fusion Cloud ERP implementation
    • Quarterly update readiness
    • EBS 12.2 support and RUPs
    • EBS to Fusion migration
    • Integrations
    • Staffing and run support
  3. chapter 03 · how it runs

    Our approach

    • Estate review
    • Update or upgrade plan
    • Rehearse
    • Run and hand over
  4. chapter 04 · where you end up

    What changes

    • EBS is back on a current release with patching that works, and the Demantra replacement has an agreed target and date.
    • Update problems surface in test, with time to fix them before the production update date.
    • Quarterly update calendar with regression pack and owner per flow
    • EBS customization register with online patching compliance status
what we do

Our Oracle Fusion ERP & E-Business Suite work

6 kinds of Oracle Fusion ERP & E-Business Suite work, each run by engineers who have done it on live tenants.

  1. General ledger, payables, receivables, fixed assets, procurement and project management configured from your chart of accounts and approval rules, with data conversion through FBDI loads.

  2. For each Fusion update (26A to 26D this year) we read the What's New, flag features that change your flows, run a regression pack in the test pod, and track opt-in features you choose to enable.

  3. Release update packs up to 12.2.15, AD and TXK patching, online patching (ADOP) cycles and custom code made edition-based-redefinition compliant.

  4. A customization inventory, a decision on what to rebuild in Fusion, VBCS or OIC and what to retire, data conversion design and parallel close before cut-over.

  5. Oracle Integration Cloud flows, REST and SOAP services, BI Publisher extracts and file-based loads between Oracle ERP and banks, HR, CRM and the data warehouse.

  6. Fusion functional consultants, OIC developers and EBS DBAs and developers, onsite in the US or nearshore and offshore across time zones.

capability 01 / 06in production

Fusion Cloud ERP implementation

General ledger, payables, receivables, fixed assets, procurement and project management configured from your chart of accounts and approval rules, with data conversion through FBDI loads.

capability 02 / 06in production

Quarterly update readiness

For each Fusion update (26A to 26D this year) we read the What's New, flag features that change your flows, run a regression pack in the test pod, and track opt-in features you choose to enable.

capability 03 / 06in production

EBS 12.2 support and RUPs

Release update packs up to 12.2.15, AD and TXK patching, online patching (ADOP) cycles and custom code made edition-based-redefinition compliant.

capability 04 / 06in production

EBS to Fusion migration

A customization inventory, a decision on what to rebuild in Fusion, VBCS or OIC and what to retire, data conversion design and parallel close before cut-over.

capability 05 / 06in production

Integrations

Oracle Integration Cloud flows, REST and SOAP services, BI Publisher extracts and file-based loads between Oracle ERP and banks, HR, CRM and the data warehouse.

capability 06 / 06in production

Staffing and run support

Fusion functional consultants, OIC developers and EBS DBAs and developers, onsite in the US or nearshore and offshore across time zones.

typical situations

Oracle Fusion ERP & E-Business Suite situations we walk into

We pieced these together from Oracle Fusion ERP & E-Business Suite situations that come up a lot. They're patterns. You won't find a specific client in them.

case file 01

EBS 12.2.9 with Demantra and a December 2026 support date

composite · not a client story
  1. Beforethe situation

    EBS 12.2.9 runs financials and order management, and Demantra drives the demand plan. Patching stalled after two failed ADOP cycles, and Demantra's Premier Support ends in December 2026.

  2. What we dothe work

    We fix the custom objects that broke online patching, rehearse an ADOP cycle on a clone and plan the RUP path to 12.2.15. In parallel, demand planning options are scored against the forecast process the planners actually run.

  3. Afterwhere you end up

    EBS is back on a current release with patching that works, and the Demantra replacement has an agreed target and date.

case file 02

Fusion financials where each quarterly update breaks approvals

composite · not a client story
  1. Beforethe situation

    Fusion Cloud ERP went live last year. Since then two quarterly updates have changed approval routing and a BI Publisher report, and both times the team heard about it from users on day one.

  2. What we dothe work

    We build a regression pack around close, payments, approvals and the top reports, schedule it in the test environment after each update lands there, and review the What's New for features that change behavior.

  3. Afterwhere you end up

    Update problems surface in test, with time to fix them before the production update date.

approach

How a Oracle Fusion ERP & E-Business Suite engagement runs

We don't start a step until the last one has produced something you can check.

  1. step 01

    Estate review

    On EBS we look at the current RUP level, custom objects, online patching compliance and the integration list. On Fusion we look at opt-in features, extensions and OIC flows, and at how the last two updates were tested.

  2. step 02

    Update or upgrade plan

    On the Fusion side, a calendar that puts a test window in front of every Oracle update date. On the EBS side, a RUP and AD/TXK patch plan that includes the custom code fixes it needs.

  3. step 03

    Rehearse

    Fusion regression packs run in the test environment after each update lands there. EBS patch cycles and any migration conversions are rehearsed on clones with timings recorded.

  4. step 04

    Run and hand over

    Production updates or cut-over with your team, then runbooks, the regression pack and the customization register left with the people who'll own them.

architecture

Where Oracle ERP sits between finance, HR and the warehouse

Fusion Cloud ERP, or EBS 12.2 for teams that stay on premises, holds the ledger, payables and procurement. Oracle Integration Cloud carries data in from HR, CRM and banks and out to the data platform, while Oracle access management controls who signs in.

Where Oracle ERP sits between finance, HR and the warehouse Fusion Cloud ERP, or EBS 12.2 for teams that stay on premises, holds the ledger, payables and procurement. Oracle Integration Cloud carries data in from HR, CRM and banks and out to the data platform, while Oracle access management controls who signs in. 01 · SOURCES 02 · INTEGRATION 03 · ERP 04 · ANALYTICS worker data invoices to bill bank statements REST · FBDI legacy interfaces SSO BICC extracts data conversion WO Workday HCM workers · costcenters Sf Salesforce orders · customers Banks statements · payments Oracle IntegrationCloud REST · FBDI · BIP extracts MU MuleSoft where it's theenterprise hub ERP Fusion Cloud ERP GL · AP · AR ·procurement E-Business Suite 12.2 on-premises or OCI OAM Oracle Identity SSO · access Snowflake finance reporting
Read the diagram as text
  1. Workday HCM → Oracle Integration Cloud: worker data
  2. Salesforce → Oracle Integration Cloud: invoices to bill
  3. Banks → Oracle Integration Cloud: bank statements
  4. Oracle Integration Cloud → Fusion Cloud ERP: REST · FBDI
  5. MuleSoft → E-Business Suite 12.2: legacy interfaces
  6. Oracle Identity → Fusion Cloud ERP: SSO
  7. Fusion Cloud ERP → Snowflake: BICC extracts
  8. E-Business Suite 12.2 → Fusion Cloud ERP: data conversion
use cases

Typical Oracle Fusion ERP & E-Business Suite projects

The work teams usually bring us, and the platforms Oracle Fusion ERP & E-Business Suite has to talk to while we do it.

  1. ORA-01 Each Fusion quarterly update breaks a report, an approval or an integration common request
  2. ORA-02 You're on EBS 12.1 or an early 12.2 RUP and patching has fallen behind common request
  3. ORA-03 You still plan on Demantra or Value Chain Planning in EBS, and support ends in December 2026 common request
  4. ORA-04 The board wants a Fusion business case that accounts for every customization common request
  5. ORA-05 Integrations to banks and HR are built on scripts nobody maintains common request
Oracle Fusion ERP & E-Business Suite · connected platforms
you keep

What a Oracle Fusion ERP & E-Business Suite engagement leaves behind

These are working documents, written against your configuration, so your team can run them without us.

  • tests01

    Quarterly update calendar with regression pack and owner per flow

    yours to keep
  • inventory02

    EBS customization register with online patching compliance status

    yours to keep
  • tests03

    RUP and AD/TXK patch plan with timed clone rehearsal

    yours to keep
  • report04

    EBS to Fusion fit scoring for every customization and report

    yours to keep
  • inventory05

    OIC integration catalog with auth method and error handling per flow

    yours to keep
  • runbook06

    Data conversion runbook with parallel close results

    yours to keep
talent and delivery · oracle fusion erp & e-business suite

Certified engineers, wherever you need them.

Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.

Onsite

Engineers at your sites in the US

Nearshore

Overlapping hours with US teams

Offshore

Overnight progress on your backlog

All time zones

Coverage handed over across time zones

24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
roles we staff
  • Oracle Fusion Financials functional consultant
  • Oracle Fusion Procurement and Projects consultant
  • Oracle Integration Cloud (OIC) developer
  • Oracle EBS Apps DBA (12.2, ADOP)
  • Oracle EBS technical developer (PL/SQL, OAF, BI Publisher)
01Should we stay on EBS 12.2 or move to Fusion Cloud ERP?

Both are defensible. Oracle lists EBS 12.2 Premier Support through at least December 2037, so staying is a supported choice. Moving makes sense when the customizations are mostly workarounds Fusion now covers, when you want to stop running infrastructure, or when the quarterly feature flow matters to the business. We score each customization before recommending either.

02How much testing does each Fusion quarterly update need?

Enough to cover the flows that would hurt if they broke: period close, payments, approvals, integrations and key reports. We keep a regression pack sized to those flows, run it in the test environment after each update lands there, and review the What's New for features that change behavior.

03What happens to Demantra and Value Chain Planning on EBS?

Oracle's exceptions table lists Premier Support for 12.2 Value Chain Planning and Demantra products ending in December 2026. If you rely on them, the planning replacement needs a decision now. Options include Oracle's cloud planning products or another planning platform.

04Why do EBS customizations break during patching?

Online patching in 12.2 uses edition-based redefinition, so custom objects must follow Oracle's development standards for it. Code written for 12.1 often doesn't. We run the compliance checks, fix what they report, and rehearse an ADOP cycle on a clone.

05How long does an EBS to Fusion move take?

It depends on modules, ledgers, countries, data volume and how many customizations need a new home. Most of the schedule goes to data conversion rehearsals and parallel close. We set the plan after the customization inventory, not before.

06Do you provide Oracle ERP engineers on contract or permanent terms?

Yes. We staff Fusion, OIC and EBS roles on contract, contract-to-hire or permanent terms, onsite in the US or nearshore and offshore.

services

Related services

Projects on Oracle Fusion ERP & E-Business Suite usually end up touching one of these, so they're worth a look.

sources 4 sources linked last checked 2026-10-20 content fingerprint 34708837
  1. 01Oracle readiness: Fusion Cloud ERP update list (26A to 26D)docs.oracle.com ↗
  2. 02Oracle readiness: Financials 26D What's New (18 Oct 2026)docs.oracle.com ↗
  3. 03Oracle Lifetime Support Policy: Applications (effective 7 Aug 2026)oracle.com ↗
  4. 04Oracle E-Business Suite: 12.2.15 announcement and 2037 Premier Supportoracle.com ↗
Reviewed by the Cohash team Oracle Fusion ERP & E-Business Suite is a trademark of its owner, used here to identify the platform. how we handle facts and data →
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it