EBS licensing, the metric outlives the discount
Oracle E-Business Suite is licensed module by module on metrics like Application User and Employee, while the database underneath is licensed separately and usually costs more. There is no suite license, only a list of modules each with a quantity and a metric, and the metric you accept at purchase governs your cost for a decade, because metrics move up easily and almost never move back down.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 25 to 35 EBS engagements reviewed 2024 to 2025.
Executive summary
Dormant users are the fastest saving. An Application User is a named individual authorized on a module, whether or not they ever log in, and one person authorized on four modules is four licenses.
Across our engagements, dormant Application Users averaged 30 to 40 percent of the licensed total in estates without a recent review, and buyers who reconciled and deprovisioned before renewal cut counts 20 to 35 percent.
The database is the bigger number.
EBS runs on an Oracle Database licensed separately at technology list prices: a two node production database on 32 cores is 16 processor licenses and $760,000 of Enterprise Edition list before options, over $1.3 million with a normal option stack, before a single application user.
The restricted use grant bundled with EBS covers EBS programs only, and a reporting schema or warehouse feed converts it into a full license requirement: breaches appeared in roughly half the estates we reviewed.
The metric decides the decade.
Application User grows only when you add people; Employee counts the whole population the module serves, growing automatically with headcount and acquisitions; volume metrics reprice when transactions cross a band nobody was watching.
And revenue metrics reprice on financial results entirely outside IT control.
Oracle adds quantity on your existing metric within days, and changing the metric itself needs a new ordering document and a repricing against current list: the discount applies once, the metric applies every year.
Self service is the counting trap. Rolling iProcurement or Self Service HR to the whole workforce authorizes the whole workforce unless the contracted metric says otherwise, which converts a convenience rollout into an enterprise wide license event.
The five questions that prevent it, headcount doubling, acquisitions, divestitures, outsourcing, and the word for word metric definition, get answered in writing before signature, because afterward they are facts you live with.
The metric families, and how each one fails you
| Metric | What it counts | How it grows on you | The common trap |
|---|---|---|---|
| Application User | Named individuals authorized per module | Only when people are added: the most controllable | Leavers and dormant accounts never deprovisioned |
| Employee | The population the module serves | Automatically, with headcount and acquisitions | Contractors and part timers counted as employees |
| Volume: expense reports, order lines | Annual transaction volume in bands | Whenever volume crosses a band boundary | Nobody owns the counter, so bands breach silently |
| Revenue or cost of goods sold | Reported financial figures | With business performance, outside IT control | Acquisitions reprice the line with no usage change |
| Restricted use technology | The embedded database and tools, for EBS only | The moment a non EBS workload joins | A reporting schema converts it to a full license need |
Application User is not Named User Plus. They come from different price lists and count different things: Application User counts authorization on a module, Named User Plus counts individuals and devices authorized on the database.
You can be perfectly compliant on Application Users and badly exposed on the database beneath them, which is the single most common shape of an EBS audit finding we see.
The database underneath, where the money concentrates
The application lines are counted in users.
The database is counted in processors at technology list, and the arithmetic dwarfs most module stacks: 32 Intel cores at the 0.5 factor is 16 processors, $760,000 of Enterprise Edition, and the options a production EBS estate typically runs push past $1.3 million before anyone opens a module.
The restricted use grant is the boundary to police: it covers EBS programs only, and the breaches we found in half the estates came from ordinary work, a reporting schema, a custom application on the same instance, a warehouse feed.
Each converting bundled rights into a full license need at technology prices.
The full database licensing doctrine sits in the database licensing guide, priced line by line against the technology price list.
The Oracle EBS licensing brief
The module and metric map, the restricted use boundary, the self service counting rules, and the support decision worked end to end.
Get the white paper →Same module, three metrics, one growth story
| Scenario | Application User | Employee | Revenue based |
|---|---|---|---|
| Day one: 4,000 staff, 250 real users | 250 licenses | 4,000 licenses | Priced on current revenue |
| You acquire a 2,000 person business | Add only users who log in | Add 2,000 automatically | Reprices on combined revenue |
| You outsource payroll processing | Remove those users at renewal | No relief: population unchanged | No relief |
| Revenue doubles, usage flat | No change | No change | Cost doubles |
| Where it hurts most | Dormant accounts you forgot | Growth and acquisitions | Success itself |
The Employee metric has two honest uses: modules almost everyone genuinely uses, where per head pricing beats counting and removes the overhead, and stable or shrinking workforces in mature businesses, where it buys predictability. Everywhere else it is a bet on your own decline.
The five questions before any module line signs: what happens if headcount doubles and usage does not, whether acquired populations land inside the metric, whether a written divestiture reduction right exists, whether the metric follows outsourced work, and the contractual definition word for word.
- 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 EBS engagements, 2024 to 2025
Across roughly 25 to 35 Oracle E-Business Suite engagements Fredrik Filipsson reviewed in 2024 and 2025, the user list was inflated and the database boundary was leaking:
Licensed Application Users with no login for a year, renewing at full rate wherever nobody reconciled.
Restricted use database grants crossed by reporting schemas and custom feeds.
The support decision completes the picture: EBS is mature, Oracle has moved the Premier Support date more than once, and third party support at roughly half the fee is a real option with real losses, no new patches, no upgrade path.
Weighed in the third party support analysis and the support cost reduction strategies.
The eventual Fusion migration is its own negotiation on its own calendar, and the module inventory that starts it is the same one the license review needs, the full catalog in the EBS module list.
Your first five moves
- Reconcile Application Users against login activity and deprovision the dormant 30 to 40 percent before the renewal prices them again.
- Audit the restricted use boundary: every schema, feed, and custom application on the EBS instances, because the breach is ordinary work.
- Read every metric definition word for word and answer the five growth questions in writing before any new module line signs.
- Assign an owner to every volume metric counter, because bands breach silently when nobody watches the throughput.
- Price the support decision honestly, Oracle against third party at half the fee, on your patch and upgrade reality. The Oracle practice runs the estate with you.
Frequently asked questions
How is Oracle E-Business Suite licensed?
Module by module, each on its own metric and line: Application User for named authorized individuals, Employee for the population a module serves, volume metrics for transaction throughput, and revenue metrics on financial figures.
There is no suite license, and the database underneath is licensed separately on technology metrics, usually for more than the application lines.
What is the difference between Application User and Named User Plus?
Different price lists counting different things: Application User counts authorization on an EBS module, Named User Plus counts individuals and devices authorized on the database.
Compliance on one says nothing about the other, and being clean on Application Users while exposed on the database beneath is the most common shape of EBS audit finding.
What does the EBS restricted use database cover?
EBS programs only: the bundled grant covers the database serving E-Business Suite itself, and a reporting schema, custom application, or warehouse feed on the same instance converts the requirement into full technology licensing at list.
Breaches appeared in roughly half the estates we reviewed, almost always from ordinary work nobody checked against the grant.
What is the fastest EBS licensing saving?
Dormant user reconciliation: Application Users who had not logged in for a year averaged 30 to 40 percent of licensed totals, and buyers who reconciled and deprovisioned before renewal cut counts 20 to 35 percent.
The authorization, not the usage, is what licenses, so the deprovisioning discipline is the cost control.
Should EBS use the Employee metric?
Only in two cases: modules nearly everyone genuinely uses, where per head pricing beats counting, and stable or shrinking workforces where it buys predictability.
Everywhere else the Employee metric grows automatically with headcount and acquisitions while offering no relief for outsourcing or reduced usage, a bet on your own decline.
Is third party support viable for EBS?
It is a genuine decision: EBS is mature, Oracle has moved the Premier Support date more than once, and third party support at roughly half the fee is real, with real losses, no new patches, no upgrade path, and no route back without cost.
The answer depends on your patch reality and Fusion timeline, priced honestly rather than assumed either way.
