Oracle EBS

E-Business Suite estates kept current, upgraded, or moved to Fusion Cloud, on a decision made with the numbers in front of you.

Discuss your project Learn this field

What is it?

Organisations running E-Business Suite are rarely asking whether it works. They are asking what to do next: stay on 12.2 and keep it patched, finish a 12.1 upgrade, or move to Fusion Cloud, and in what order. We inventory the estate, cost each option against it, and then do the work, whichever way the decision goes.

For a technical reader

EBS 12.2 runs a dual filesystem with online patching through ADOP, which turns most patching from an outage into a procedure, and brings edition-based redefinition rules that custom code has to respect. That is where the difficulty in an EBS engagement usually sits: Forms personalisations, OA Framework extensions, custom concurrent programs and direct-to-table interfaces written when nobody expected the suite to outlive them. An upgrade plan or a migration plan is really a plan for that custom estate, which is why the inventory has to come before the timeline rather than after it.

Our services

Estate assessmentWhat is running, what is customised, what is still used, and what each forward option would cost on your estate.
12.1 to 12.2 upgradeUpgrade rehearsed on cloned environments at production data volume, with custom code remediated for online patching.
Maintenance and functional supportPatching, quarterly security updates, performance work and day-to-day functional support on a sustainable cadence.
Migration to Fusion CloudA phased move to Oracle Cloud ERP, HCM or SCM, with coexistence while EBS is still the system of record.

What’s covered

Financials
General Ledger, Payables, Receivables, Assets and Cash Management across the 12.x footprint
Supply chain and manufacturing
Inventory, Purchasing, Order Management, WIP and Advanced Supply Chain Planning
HRMS and Payroll
Core HR, Payroll, Self-Service HR and Time and Labor
Technology stack
Database and middleware currency, concurrent manager tuning, and the Forms and OAF custom estate
Upgrade and patching
12.1 to 12.2 upgrades, online patching with ADOP, and the quarterly security updates
Path to Fusion Cloud
Assessment, coexistence options and a phased migration where moving is the right answer

Business problems we solve

We cannot decide whether to stay or moveBoth are defensible positions. We cost them against your estate rather than arguing the general case, and the recommendation comes with the numbers behind it.
Every patch is an outageOn 12.2 online patching removes most of that, but only if the custom code follows the edition-based rules. Remediating it is the actual work.
Nobody understands the customisationsThey get inventoried and traced to real usage. A large share usually turn out to be dormant and can simply be retired.
The people who built it have goneKnowledge recovery from the running system and the code, written down, is the first deliverable rather than something hoped for along the way.

Our delivery approach

  1. 01
    Inventory the estate as it runsModules actually in use, customisations actually invoked, integrations, patch level and database version. The documented estate and the running estate are rarely the same system, and the gap between them is where the cost hides.
  2. 02
    Cost the options side by sideStay and maintain, upgrade in place, or migrate. Each with the work, the risk and the running cost written down, so the choice is made on comparison rather than preference.
  3. 03
    Rehearse before productionAn upgrade runs on a cloned environment at production data volume until the timings and the failure points are known. A migration moves one business area at a time, with EBS still the system of record until the new one is trusted.
  4. 04
    Leave it maintainableCustomisations reduced to the ones still earning their place, patching on a cadence the team can sustain, and the knowledge written down rather than held by one person.

Solutions & project types

Examples of the work we take on in this area. These describe project shapes, not named client engagements.

12.1 to 12.2 upgradeUpgrade with custom code remediated for online patching, rehearsed at full data volume before the cutover is scheduled.
Financials first to Fusion CloudMoving Financials while EBS continues to run supply chain, with reporting reconciled across both during the overlap.
Customisation reductionRetiring dormant extensions and replacing the rest with standard functionality where Oracle has since closed the gap.
Technology stack currencyDatabase and middleware tiers brought back to supported versions with no functional change in scope.

Technologies & platforms

Financials

  • General Ledger
  • Payables
  • Receivables
  • Assets
  • Cash Management

Supply chain

  • Inventory
  • Purchasing
  • Order Management
  • Work in Process
  • Advanced Supply Chain Planning

HRMS

  • Core HR
  • Payroll
  • Self-Service HR
  • Time and Labor

Technology

  • Oracle Database
  • Oracle WebLogic Server
  • ADOP online patching
  • Concurrent Manager
  • AutoConfig

Customisation

  • Oracle Forms
  • OA Framework
  • PL/SQL
  • Oracle Workflow
  • BI Publisher

Integration & data

  • Oracle Integration Cloud
  • Open interfaces and APIs
  • SQL*Loader
  • FBDI on the Fusion side
Learn this field

Where to start with oracle ebs.

Secondary to the work itself, but genuinely useful if you are building the skill. Every link goes to official documentation or an official channel.

Beginner

  • The EBS module map and how the suite is organised
  • Navigate both Forms and OA Framework pages
  • Submit a concurrent request and read its log
  • Multi-org: operating units, inventory organisations, ledgers
  • Run a standard report and find where its data actually lives

Intermediate

  • Open interfaces and the standard import programs
  • Forms personalisation versus customisation, and when each is appropriate
  • Patching with adop and the dual filesystem
  • Period close in Financials and the subledger links
  • Reading execution plans against the EBS schema

Advanced

  • Edition-based redefinition and what it demands of custom code
  • Upgrade path planning from 11i and 12.1
  • Tuning the concurrent manager and the batch window
  • Coexistence architecture alongside Fusion Cloud applications
  • Cutover design for a phased migration

Certifications

  • Oracle E-Business Suite R12.1 General Ledger Essentials
  • Oracle E-Business Suite R12.1 Payables Essentials
  • Oracle E-Business Suite R12.1 Purchasing Essentials
  • Oracle E-Business Suite R12.1 Inventory Essentials

Practice projects

  • Map the module footprint of a running instance from the data, not the documentation
  • Load suppliers and invoices through an open interface and reconcile the result
  • Apply a patch on a 12.2 instance and follow the adop phases through
  • Trace one Forms personalisation to the business rule it implements
  • Write the stay, upgrade and migrate comparison for a two-module estate
FAQs

Questions we get asked.

Is E-Business Suite end of life?

No. Oracle publishes support dates for 12.2 and has moved them out before now, so staying on it is a strategy rather than a countdown. Check the current dates in the Lifetime Support Policy rather than relying on what was true a couple of years ago.

Should we upgrade to 12.2 or go straight to Fusion Cloud?

It turns on how much of your customisation is still load-bearing and how soon the business needs capability EBS does not have. An upgrade is cheaper and buys time; a Fusion move is a larger programme with a different operating model at the end of it. We cost both before recommending either.

What happens to our customisations if we move to Fusion?

Most do not come with you. Fusion constrains extension to supported points, so each one is either met by standard functionality, rebuilt inside those limits, or dropped. Doing the inventory first is what makes that a decision rather than a discovery during testing.

Can you support EBS while we plan the move?

Yes, and that is the common shape of this work: steady maintenance and patching on the running estate while the migration proceeds alongside it.

How long does a 12.1 to 12.2 upgrade take?

It is driven by the size of the custom estate and the number of rehearsal cycles the data volume demands, rather than by module count. The assessment is what produces a timeline worth quoting.

Oracle

Related services.

Oracle ERPOracle Cloud ERP implementation and migration, sequenced so the business keeps running.Oracle SCMSupply chain on Oracle Cloud: planning, inventory, procurement and order management.Oracle HCMCore HR, payroll and talent on Oracle Cloud, with the parallel runs to prove payroll is right.Oracle EPMPlanning, budgeting and close on Oracle EPM, so the cycle stops living in spreadsheets.Oracle Cloud InfrastructureOCI landing zones, migration and operations, built to your security and compliance requirements.
Start the conversation

Talk to our experts about oracle ebs.

Tell us where you are. A specialist will read it and reply within one business day.

Discuss your project