A hundred license lines, and the shelf forms in the same place every time
Oracle E-Business Suite ships as separately licensed modules across eight families. The list is easy to find. What decides your invoice is harder: the metric behind each module, the indicative list band it prices at, and which modules end up on the shelf paying support for nothing. The family is a planning grouping. The module is the entitlement, and audits price at module level.
Prepared by Redress Compliance · August 9, 2026 · Oracle advisory. Based on roughly 15 to 20 Oracle EBS license reviews run 2024 to 2025.
Executive summary
The family is a planning grouping; the module is the entitlement, and audits price at module level.
Owning Purchasing does not license iProcurement, and owning Core HR does not license Payroll: every line on your ordering document is the entire entitlement, and a module not named on a line is a module you do not have, however logically it belongs to a family you did buy.
Over a hundred license lines sit across eight families, and in the reviews behind this page mid market and large estates ran between 12 and 30 modules with genuine daily activity against entitlement lists carrying 20 to 45 lines. The difference is not waste in the accounting sense.
It is a support annuity you can often stop paying, provided you can prove the module was never used.
Support is 72 percent of the ten year bill, which is why the metric beats the discount.
On a typical 200 user Financials module at 60 percent discount, roughly 368,000 dollars of net license carries about 927,000 dollars of support across ten years, compounding at a 3 percent annual uplift most contracts permit.
A deeper discount lowers the support base, which is the real reason to push on it; the inverse is the trap, because a module you never deploy still costs its share of that support stream, calculated on the net license fee whether the module runs or not.
A single dormant Sourcing line for 40 users at 55 percent off is close to 156,000 dollars across ten years for software nobody opened, and two or three of those lines is a headcount.
The metric you accept at purchase sets your cost for a decade, because metrics almost never get renegotiated downward.
Application User counts a named authorized person per module, so one person using four modules is four licenses.
The Employee metric on HCM and self service modules counts the whole workforce the module serves, part time and often contractors, whether or not they ever log in, so a 4,000 person company licensing Core HR pays against 4,000 people, not the 60 in the HR department.
Grow the business 15 percent and the Employee lines grow automatically while Application User lines stay flat.
We have seen an estate paying an Employee metric against a 9,000 person population for a module only 200 people ever touched, bought that way in 2011 because the discount looked better on the day.
Enabled is not licensed, and the error runs in both directions. EBS installs the full stack, so licensing is a paper boundary rather than a technical one, and usage accrues through responsibility assignments, enabled module flags and interface reads long before procurement hears about it.
Across the reviews, estates averaged 3 to 5 modules enabled or touched by interfaces with no license line behind them, each a six figure audit exposure, and 2 to 4 fully licensed modules with zero active responsibilities paying 22 percent support on shelf.
Custom schemas and middleware reading module tables triggered usage claims in a third of the audits we defended. The reconciliation that matters is four way, licensed, used, enabled and interfaced, and most estates only ever compare the first two.
The eight families, and where the shelf forms
| Family | Representative modules | Dominant metric | Where the shelf forms |
|---|---|---|---|
| Financials | General Ledger, Payables, Receivables, Fixed Assets, Cash Management | Application User | Rarely. The family estates genuinely use |
| Procurement | Purchasing, iProcurement, Sourcing, Procurement Contracts, iSupplier | Application User or Supplier | Sourcing and Contracts, bought in a suite deal and never rolled out |
| Projects | Costing, Billing, Management, Portfolio Analysis | Application User | Portfolio Analysis, where the PMO never adopted it |
| HCM | Core HR, Payroll, Self Service HR, Learning Management, iRecruitment | Employee | Learning Management and iRecruitment, displaced by a talent platform |
| Supply Chain | Inventory, Order Management, WMS, Advanced Supply Chain Planning | Application User or Order Line | Advanced Supply Chain Planning, the classic planning shelf |
| Manufacturing | Work in Process, Bills of Material, Quality, Configurator | Application User | Configurator and Quality, licensed for one plant, never extended |
| CRM | TeleService, Field Service, Marketing, Incentive Compensation | Application User | Marketing and Incentive Compensation, replaced by Salesforce |
| Analytics and governance | Daily Business Intelligence, Internal Controls Manager, Advanced Collections | Varies, sometimes revenue based | Frequently. Lines that survive renewals nobody reads |
The Employee metric is where the arithmetic changes. Application User is the EBS default, a named individual authorized to use a module regardless of how often they log in, so authorization not activity is what Oracle counts, and one person across four modules is four licenses.
HCM and self service modules count on Employee: Core HR at 100 to 170 dollars per employee, Payroll at 80 to 130, Learning Management at 40 to 90, counted against the total workforce the module serves and reconciled against HR records, not login logs.
Transaction and volume metrics price Internet Expenses, Order Lines and shipment volumes on throughput, and some industry and governance modules price on revenue or cost of goods sold, repricing as the business grows.
Ask one question before signing any line: if headcount doubles and usage does not, what happens to this line? If the answer is that it doubles, negotiate the metric, not the discount.
The modules bought and never deployed
- Sourcing and Procurement Contracts: added to hit a procurement transformation narrative, then never staffed, while category managers keep running events in spreadsheets.
- Advanced Supply Chain Planning and Demand Planning: the planning shelf, where data quality was never good enough to trust a constrained plan so planners went back to Excel.
- Learning Management and iRecruitment: displaced by a dedicated talent suite, usually within three years, while the EBS lines stayed on support.
- Marketing and Incentive Compensation: the CRM family shows the most complete abandonment, because Salesforce or a commissions tool took the workload.
- Configurator, Advanced Collections and Internal Controls Manager: licensed for one product line or one controls program, then quietly dropped when the sponsor left or the program ended. Prove shelf with three artifacts pulled on the same date: a responsibility assignment extract showing no active user holds the module functions, a twelve month transaction count from the base tables showing zero or seeded rows, and an interface inventory confirming no middleware reads the module APIs.
The Oracle CIO complete playbook
The reconciliation, the support termination sequence, and the proactive gap licensing that reprice an EBS estate.
Get the white paper →The unlicensed usage, and the database underneath
EBS installs every module in the technology stack, so unlicensed usage accrues without anyone deciding on it. Responsibility sprawl is the main channel: a super user responsibility that includes unlicensed module functions creates countable authorization for every person who holds it.
Implementation partners enable module flags for setup convenience during a project and never disable them at the end.
Custom code and middleware querying module tables has been argued as use by Oracle License Management Services in audits we defended, where the code exercises module functionality rather than only reading data.
And the defensible position requires documenting what each interface touches and why it is not module use, built before the audit rather than during it.
There is a second exposure underneath the module list and it is the expensive one: EBS ships with a restricted use database grant that covers EBS workloads only, and a reporting schema or data warehouse feed on the same instance can push you into needing a full Oracle Database license.
In EBS the module list is the visible license; the database underneath is the one that decides the settlement, so reconcile both or you have done half the work.
Older estates sometimes hold legacy concurrent or floating entitlements that behave differently from named Application Users, rare, valuable and easy to lose in a consolidation, so identify them before any restructure, mechanics we cover in managing EBS concurrent licensing.
- 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 license reviews, 2024 to 2025
Across roughly 15 to 20 Oracle EBS license reviews Fredrik Filipsson ran between 2024 and 2025, the gap between the module list on the order form and the modules actually in use was wide in both directions, and the standard advice made it worse.
The standard advice is to run a usage report once a year and true up whatever it finds. We disagree, because annual true ups systematically overpaid:
Modules enabled or touched by interfaces with no license line behind them, each a six figure audit exposure, in the average estate.
How far below Oracle's opening audit list positions negotiated proactive purchases landed for the same modules.
Estates bought modules at near list under audit pressure while paying 22 percent support on 2 to 4 fully shelved modules nobody reconciled: the report told them what they owed and never what they could stop paying for.
The buyer side move is a quarterly responsibility and interface sweep, support termination on provable shelf at the next renewal window respecting the contract grouping.
And proactive gap licensing at negotiated rates, because in an audit Oracle negotiates against a quantified liability and outside one it negotiates against your willingness to walk, which are very different rooms.
Third party support is more credible on EBS than almost any other Oracle product, because the release is mature and the patch stream matters less each year, buying roughly half the annual support bill and a genuine alternative to say out loud in a renewal.
Against the loss of new patches and regulatory payroll updates.
And if the estate is heading to Fusion, reconcile first: Oracle sizes a Fusion Cloud proposal from the footprint it believes you run, perpetual EBS licenses do not convert to subscription credit as a matter of right.
And a clean defended position is leverage while a messy one is a discovery exercise Oracle gets to run for you.
Compare the target side in the Fusion module list and the transition playbook.
Your first five moves
- Reconcile four ways, not two: classify every module as licensed and used, licensed shelf, or used unlicensed, comparing the ordering documents against responsibility assignments, module flags and interface reads.
- Sweep quarterly, not annually: extract responsibility assignments and module flags every quarter, because the annual true up tells you what you owe and never what you can stop paying for.
- Prove shelf with three dated artifacts before you ask for anything: a responsibility extract, a twelve month transaction count, and an interface inventory, pulled on the same date and kept as the file that defends a support termination.
- License genuine gaps proactively at negotiated rates, never at audit list price, capturing the 40 to 60 percent first mover discount over an audit settlement.
- Reconcile the database grant underneath the modules: a reporting schema or warehouse feed on the EBS instance can breach the restricted use grant. The Oracle practice runs the position with you.
Frequently asked questions
How many modules does Oracle E-Business Suite have?
Over a hundred separately licensed modules across eight families: Financials, Procurement, Projects, HCM, Supply Chain, Manufacturing, CRM, and Analytics and governance.
The family is a planning grouping and does not appear on an order form; the module is the license unit, and audits price at module level. In our reviews, estates ran 12 to 30 modules with genuine daily activity against entitlement lists carrying 20 to 45 lines.
Does owning a module family license all its modules?
No. Every line on your ordering document is the entire entitlement, and a module not named on a line is a module you do not have, however logically it belongs to a family you bought. Owning Purchasing does not license iProcurement; owning Core HR does not license Payroll.
Audits price at module level precisely because families do not exist as entitlements, so reconcile against the named lines, not the family logic.
What does the Employee metric count in EBS?
Every person the module serves, including part time staff and often contractors, whether or not they ever log in.
HCM and self service modules license on Employee, so a 4,000 person company licensing Core HR pays against 4,000 people, not the 60 in the HR department, and audits reconcile against HR records, not login logs.
Grow headcount 15 percent and the Employee lines grow automatically, while Application User lines stay flat.
Why is support 72 percent of the cost of an EBS module?
Because the discount you win applies once and support applies every year, compounding at a 3 to 4 percent uplift most contracts permit.
On a 200 user Financials module at 60 percent discount, roughly 368,000 dollars of net license carries about 927,000 dollars of support across ten years, so support is 72 percent of the ten year total.
A dormant module still costs its share, because Oracle calculates support on the net license fee whether the module runs or not.
How do you prove an EBS module is genuinely shelf?
With three artifacts pulled on the same date and kept: a responsibility assignment extract showing no active user holds a responsibility including the module functions, a transaction count from the module base tables over a rolling twelve months showing zero or only seeded rows.
And an interface inventory confirming no middleware or custom schema calls the module APIs or reads its tables.
That file is what defends a support termination decision if you later make one.
What happens to the EBS module list if you move to Fusion?
It becomes the basis of the Fusion quote, which is why you reconcile it first. Oracle sizes a Fusion Cloud proposal from the footprint it believes you run, so an inflated EBS entitlement list produces an inflated subscription.
Perpetual EBS licenses do not convert into subscription credit as a matter of right; anything you get is negotiated, usually as a discount posture or support bridge. A clean, defended EBS position is leverage; a messy one is a discovery exercise Oracle runs for you.
