You own the licenses, you have no deadline, and you need nothing
Oracle E-Business Suite is a mature on-premises ERP most enterprises paid for years or decades ago. The live commercial conversation is not the license. It is the annual support stream, priced at 22 percent of net license value and lifted every year unless your contract stops it. Oracle removed its own migrate-or-lose-support deadline, the account team is measured on cloud rather than protecting a forecast support line, and a buyer who needs nothing is difficult to move.
Prepared by Redress Compliance · August 9, 2026 · Oracle advisory. Based on roughly 25 to 35 EBS support and negotiation engagements reviewed 2024 to 2025.
Executive summary
Oracle removed its own deadline, so any urgency in the room is Oracle's, not yours. On 25 March 2026 Oracle extended Premier Support for EBS 12.2 through at least 2037, reviewed annually, the seventh such extension in a decade, with Sustaining Support indefinite behind it.
The application licenses themselves are settled, paid and perpetual, which changes the entire shape of the conversation: you are not asking Oracle for anything.
What Oracle wants is a cloud commitment, because the support revenue is already forecast and the account team is measured on new cloud contract value, so support concessions are available and the currency Oracle prefers is an OCI commitment, a Fusion pilot, or a database migration.
What Oracle genuinely fears is a support-base defection to third party support, because that revenue rarely returns.
You cannot quietly drop shelfware, because Oracle's repricing rule works at the level of the order.
The policy on pricing following reduction of licenses states that if a subset of licenses on a single order is terminated, support for the remaining licenses on that order is repriced at Oracle's list price minus the applicable standard discount.
So dropping the 20 percent you do not use can leave the 80 percent you do use costing very nearly the same.
Matching Service Levels compounds it: every license in a license set must sit at the same support level, so partial support is not available.
Shelfware removal is therefore an exercise in order structure, not in asking nicely, and mapping every license to its ordering document decides what you can actually shed before you propose anything.
The technology stack under EBS carries more compliance risk than the application modules, and it has to be closed before you open.
The application modules are rarely the problem; the database options, WebLogic and Java runtime beneath them are, because the restricted-use rights that ship with EBS are narrower than most teams assume.
Partitioning, the Diagnostics Pack and the Tuning Pack are the most common findings, WebLogic deployments run beyond the restricted grant, and Java now sits on an employee metric.
An audit finding discovered mid-negotiation converts a support discussion into a compliance settlement, so audit yourself first and close what you find, because an unresolved audit converts your leverage into Oracle's leverage overnight.
Start twelve months out, because the notice date, not the renewal date, is the deadline that binds you. The useful work takes nine months and Oracle only responds to a buyer who has already done it: a negotiation opened at ninety days is a negotiation about a small percentage.
Oracle support renewals continue automatically unless you serve notice, and the window is short, so find that date in your own paperwork and give it a named owner, because more value is lost to a missed notice date than to any pricing argument.
Model three futures with real documents, and treat third party support as permanent when you do, because reinstatement runs 150 percent of your last annual fee plus the fees for the lapsed period, and if your five-year plan includes returning to Oracle the arithmetic almost never works.
The three futures, priced honestly
| Option | Typical effect on the support line | What you give up | Lead time |
|---|---|---|---|
| Stay on Oracle Premier Support | Flat to a negotiated reduction, uplift capped only if you ask | Nothing functionally, but the cost compounds every year | Immediate |
| Move to third party support | Roughly half, sustained for as long as you stay | Oracle patches, tax and regulatory updates, certification, escalation | Three to six months |
| Migrate to Fusion Cloud | Rises before it falls: you pay both for the whole project | Customizations, and a perpetual license position you never get back | Eighteen to thirty six months |
Every EBS negotiation is really a choice between these three, and the price Oracle offers depends entirely on which you can credibly execute.
Read three clauses in Oracle's Software Technical Support Policies before anything else: pricing following reduction of licenses, which replaces your negotiated discount with the standard one on the surviving licenses; Matching Service Levels, which blocks partial support within a set.
And reinstatement, at 150 percent of the last annual fee plus the lapsed period.
Third party support typically halves the line and is a legitimate answer for a stable estate on a mature release, but it is irreversible in practice, so model it as permanent; the framework sits in the third party support guide and the provider detail in the Rimini Street guide.
If a migration is genuinely on the table, the honest trade is in the Fusion ERP negotiation guide.
The twelve-month sequence, where the order matters more than the duration
- Twelve to eleven months out: build the census, modules deployed, users active, entities in scope, every support identifier and its renewal date, then map every license to its ordering document, because the repricing rule works at order level and the paper decides what is possible.
- Nine to six months out: model three futures, stay, third party, or Fusion, then obtain real third party quotes and a real Fusion estimate under confidentiality, because a credible alternative requires documents, not opinions, and one of the three takes two years.
- Five months out: close any open compliance exposure on database options, WebLogic and Java, because an unresolved audit converts your leverage into Oracle's overnight.
- Four to three months out: open with Oracle stating the position, the alternatives and a decision date, then serve any notice required to prevent automatic renewal, because miss the notice date and you have bought another year at the quoted price.
- Two to one month out: escalate beyond the account team once with your executive sponsor, because support pricing approval sits in a different organization from license sales, then paper every concession into the renewal ordering document, including the uplift cap, because a concession not in the order is one you re-argue next year.
The Oracle E-Business Suite negotiation playbook
The module map, the technology stack tax, the third party support math, and the eleven-move sequence with a value range against each.
Get the white paper →The technology stack tax, and the room
The EBS application modules are rarely the compliance problem; the stack underneath is, and closing it before you open the commercial conversation is what keeps a support discussion from becoming a compliance settlement.
Database options and packs are the most common finding, with Partitioning, the Diagnostics Pack and the Tuning Pack usage leading, covered in the database options and audit exposure guide; WebLogic deployments run beyond the restricted grant that ships with the application.
The Java runtime on application and client machines now sits on an employee metric, set out in the Oracle Java licensing guide; and entity scope creep from acquisitions and divestitures moves usage outside the contracting entity.
Six people belong in the room and not one of them is your implementation partner, because a partner that resells Oracle cannot advise you on leaving Oracle: an executive sponsor who will take exactly one call and mean it, procurement owning the paper and the notice dates.
The EBS functional owner who knows which modules the business uses, the database administrator who knows which options are genuinely installed, legal for the assignment, repricing and audit clauses, and an independent advisor with no reseller relationship on either side.
On the Oracle side you are dealing with at least two organizations, the account executive who sells cloud and the support renewals team that protects the base, and they do not always want the same outcome.
The licensing mechanics sit in the EBS licensing guide and the module detail in the module list; this is the negotiation.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Oracle EBS engagements, 2024 to 2025
Across roughly 25 to 35 Oracle E-Business Suite support and negotiation engagements Fredrik Filipsson reviewed in 2024 and 2025, the same four things were true almost every time, and the common advice made the position weaker rather than stronger.
The common advice is to threaten a move to third party support and let Oracle discount to keep you. We disagree:
Of the support line recoverable without losing any functionality the business used, mostly in order structure, the over-licensed technology stack, and an uncapped uplift.
Where the negotiation usually opened, which is after the only real deadline, the notice date, has already passed, leaving an argument about a small percentage.
The renewals team can tell inside one conversation whether you have quotes, an internal decision paper and an executive who has agreed to sign, so without those the threat costs you credibility you cannot rebuild in the same cycle.
The larger and less glamorous saving sits elsewhere, in the order structure that governs repricing, in the technology stack you over-license, and in the annual uplift nobody ever capped, so do the unglamorous work first and the leverage becomes real rather than rhetorical.
Five things are genuinely in your favor and worth stating explicitly: no end date, no new spend required, a functioning third party support market whose lost revenue does not come back, time if you start twelve months out against a 31 May fiscal year end.
And information asymmetry in your favor for once, because you know your deployment and Oracle does not unless an audit tells it.
Four things hand the leverage straight back, and three are avoidable with planning: an open or expected audit, a live and publicly committed Fusion project, an expiring unlimited agreement or unfinished certification running in parallel, and a divestiture needing assignment consent.
Never negotiate support with an unresolved compliance question. The cost reduction levers sit in the support cost reduction strategies and the ULA interaction in the database ULA negotiation guide.
Your first five moves
- Find the notice date in your current support renewal and give it an owner today, because more value is lost to a missed notice date than to any pricing argument.
- Build the census and map every license to its ordering document, because the repricing rule works at order level and decides what shelfware you can actually shed.
- Read the three policy clauses before you propose anything: pricing on reduction, matching service levels, and reinstatement at 150 percent.
- Audit yourself first on database options, WebLogic and Java and close what you find, because an unresolved audit hands your leverage to Oracle.
- Decide internally before you speak to Oracle, model the three futures with real numbers, and open four months out with the position, the alternative and a decision date. The Oracle practice runs the sequence with you.
Frequently asked questions
When does Oracle E-Business Suite support end?
Premier Support for EBS 12.2 now runs through at least 2037, following Oracle's announcement on 25 March 2026, and Oracle reviews annually whether to extend it by a further year, with Sustaining Support indefinite behind it.
Release 12.1 left Premier Support in December 2021 and sits on Sustaining Support, which delivers no new patches, tax updates or certifications, often at an unreduced fee. There is no deadline forcing a migration, so any urgency in the room is Oracle's, not yours.
Can you drop support on unused EBS licenses to save money?
Not quietly. Oracle's policy on pricing following reduction of licenses reprices the support for the surviving licenses on the same order at list minus the standard discount, so dropping the 20 percent you do not use can leave the 80 percent you do use costing very nearly the same.
Matching Service Levels also blocks partial support within a license set. Shelfware removal is an exercise in order structure: map every license to its ordering document before proposing anything, because the rule works at the order level.
What does Oracle actually want in an EBS negotiation?
A cloud commitment. The support revenue is already forecast, so the account team is not measured on protecting it, it is measured on new cloud contract value.
Support concessions are therefore available, and the currency Oracle prefers is OCI consumption, a Fusion pilot, a named reference, or a longer term, not cash.
What Oracle genuinely fears is a support-base defection to third party support, because that revenue rarely returns, which is where your leverage sits.
Is third party support a real option for an EBS estate?
Yes. Third party support typically halves the support line and is a legitimate answer for a stable estate on a mature release, not a bluff.
You keep your perpetual licenses and the right to run the software, but you lose new Oracle patches, tax and regulatory updates, certification with new Oracle technology, and the escalation path.
Treat it as permanent when you model it, because reinstatement is 150 percent of your last annual fee plus the lapsed period, so a plan to return to Oracle almost never works arithmetically.
Where does the compliance risk sit on an EBS estate?
In the technology stack under the application, not the modules.
The database options, middleware and Java runtime carry more risk because the restricted-use rights that ship with EBS are narrower than most teams assume: Partitioning, Diagnostics and Tuning Pack usage is the most common finding, WebLogic runs beyond the restricted grant.
And Java now sits on an employee metric.
Close that exposure before opening a commercial conversation, because an audit finding discovered mid-negotiation converts a support discussion into a compliance settlement.
How far ahead should you start an EBS support negotiation?
Twelve months before the support renewal, because the useful work takes nine and Oracle only responds to a buyer who has already done it.
Build the census and map licenses to orders, model the three futures with real quotes, close any compliance exposure, then open four months out with the position, the alternative and a decision date.
The binding deadline is the notice date inside your renewal, not the renewal date itself, so find it now and give it a named owner.
