Oracle EBS modules by family, and what each license line costs. Where the unused licenses pile up.

Oracle E-Business Suite sells over a hundred modules across eight families, and each module is its own license. Your cost depends on the metric behind each line and on the modules you pay support for but never use.

How many modules does Oracle E-Business Suite have, and how are they licensed?

Oracle E-Business Suite carries over a hundred separately licensed modules, grouped into eight families. Each module is its own line on your ordering document, and Oracle audits price findings at module level. The family is a planning grouping that never appears on an order form.

Owning Purchasing does not license iProcurement, and owning Core HR does not license Payroll. A module that is not named on a line is a module you do not have, however naturally it seems to belong to a family you bought. The wider rules for the suite are in our EBS licensing guide.

Why do options and prerequisites matter on the order?

Some modules are sold as options of a parent program. Oracle's current EBS price list shows Sourcing, Procurement Contracts and iSupplier Portal as options under Purchasing, so each needs Purchasing underneath it and a line of its own.

Options also sit in the same license set as their parent for support purposes. That grouping decides what you can terminate later, which the section on dropping support covers.

Which license metrics apply to Oracle EBS modules?

Most EBS modules are licensed per Application User, and the HCM and self service modules per Employee. A smaller group prices on transaction volume or on company financials. Over ten years, the metric on each line matters more than the discount you win on the day you sign.

• Application User. Oracle defines it as an individual authorized to use the licensed programs, whether or not that person is actively using them at any given time. One person with access to four modules therefore needs four licenses.
• Employee. All full time, part time and temporary employees, plus agents, contractors and consultants who access, use or are tracked by the programs. Oracle reconciles the count against HR records, not login logs.
• Order Line and shipment volumes. Order entry line items processed in a 12 month period, including lines the Configurator generates automatically. Busier order desks pay more, whatever the headcount.
• Expense Report. Reports processed by Internet Expenses in a 12 month period, listed at $6 per report with a minimum of 1,000.
• Revenue or cost of goods sold. Some industry and governance modules price on company financials, so they reprice as the business grows.
• Module specific counts. Learning Management counts Trainees, Incentive Compensation counts Compensated Individuals and Field Service counts Field Technicians.

How does the Employee metric change your cost as the company grows?

The Employee metric counts the whole workforce a module serves, whether or not those people ever log in. A 4,000 person company licensing Core HR pays for 4,000 people, even when only the 60 people in the HR department use the system.

Oracle's current list price for Human Resources is $185 per Employee, with a 100 employee minimum, so those 4,000 people come to $740,000 at list. Grow the workforce 15 percent to 4,600 and the line needs 600 more Employees: $111,000 at list, plus $24,420 a year of support. Your Application User lines stay flat through the same growth.

We have reviewed a company paying an Employee metric against a 9,000 person population for a module only 200 people ever touched. It was bought that way in 2011 because the discount looked better on the day. Metrics almost never get renegotiated downward, so that choice still sets the bill.

What do Oracle EBS modules cost at list price?

Oracle's EBS global price list dated September 10, 2026 puts the core Financials, Purchasing and Order Management lines at $4,595 per Application User. The HCM modules run from $40 to $225 per Employee. Annual support is 22 percent of the license fee.

Advanced Supply Chain Planning, Daily Business Intelligence and Internal Controls Manager do not appear on that list, so the only price reference for them is your own ordering documents. Keep those documents together, because they are also your proof of what you own.

Why is support 72 percent of the ten year cost of an EBS module?

The discount applies once, while support applies every year. Oracle charges 22 percent of the net license fee annually, and most contracts permit a 3 to 4 percent uplift each year on top of that.

Say you license 200 Application Users of Financials at the $4,595 list price and win a 60 percent discount. The table uses a 3 percent annual uplift.

A deeper discount lowers the support base, and that is the best reason to push hard on price. The same logic works against you on anything you do not deploy. A module no one runs still carries its share of support, calculated on the net license fee whether the module runs or not.

What does a dormant module cost you?

A dormant module costs its full support fee every year until you terminate it. Take a Sourcing line for 40 users bought at 55 percent off. At the current $9,195 list price, the net license is $165,510 and year one support is $36,412.

Over ten years at a 3 percent uplift, that line pays about $417,000 in support for software no one opens. Two or three lines like it pay for a full time employee. The license fee is already spent, but the support can still be stopped.

Which EBS modules are most often bought and never deployed?

Planning, sourcing, talent and CRM modules are the lines most often bought in a suite deal and never rolled out. The pattern repeats closely enough that these are the first modules to check on any EBS contract.

• Sourcing and Procurement Contracts. Added to support a procurement transformation story, then never staffed. Category managers keep running sourcing events in spreadsheets.
• Advanced Supply Chain Planning and Demand Planning. 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 over the work.
• Configurator, Advanced Collections and Internal Controls Manager. Licensed for one product line or one controls program, then left idle when the sponsor moved on or the program ended.

How do you prove a module is shelf?

You prove it with three records pulled on the same date and filed together. A statement that a module is unused carries little weight with Oracle, while dated evidence from the system itself does.

Can you stop paying support on an EBS module you do not use?

Yes, but only by terminating the licenses, and the contract grouping sets the terms. Oracle's technical support policies define a license set as a program with its options and self service modules, such as Purchasing with its options, or Human Resources with Self Service Human Resources. Every license in a set must sit at the same support level.

• No partial support. You cannot keep a module and simply stop supporting it. You terminate its licenses with a termination letter.
• Repricing. Oracle then reprices support on the remaining licenses on that order at list support minus the standard discount. The new fee cannot exceed what you paid before for the whole order, terminated licenses included, plus annual adjustments, and cannot fall below what you paid for the licenses you keep. On an order bought at a deep discount, the saving can shrink close to zero, so get the repriced figure in writing before you send the letter and time the termination for that order's renewal date.
• Reinstatement. Coming back later costs 150 percent of the last annual support fee, prorated back to the lapse, as our guide to dropping Oracle support and reinstatement explains.

How does unlicensed EBS usage build up?

Unlicensed usage builds up because EBS installs every module in the technology stack. The line between licensed and unlicensed exists only on paper, so use accrues through responsibility assignments, enabled module flags and interface reads long before procurement hears about it.

• Responsibility sprawl. The main channel. A super user responsibility that includes unlicensed module functions creates countable authorization for every person who holds it.
• Partner setup. Implementation partners enable module flags for convenience during a project and do not disable them at the end.
• Custom code and middleware. Custom schemas and middleware reading module tables triggered usage claims in a third of the audits we defended. Oracle License Management Services, now called Global Licensing and Advisory Services, argued use where the code exercised module functionality rather than only reading data.

The protection against the third channel is a document built before any audit, recording what each interface touches and why that is not module use. A record that predates the audit carries more weight than one written in response to it.

What does the restricted use database license in EBS cover?

EBS ships with a restricted use license for Oracle Database Enterprise Edition that covers EBS workloads only. Oracle's Applications Licensing Table says it may be used only to run the licensed applications. The grant also includes Internet Application Server Enterprise Edition, with WebLogic Server Basic, and a limited set of other products.

Three kinds of change fall outside the grant, and each has its own license consequence.

• Reporting and warehouse feeds. A reporting schema or a data warehouse feed on the same instance can push you into needing a full Oracle Database license.
• Database changes. The same table says adding or changing tables, columns, stored procedures or triggers requires full Database Enterprise Edition licenses for the actual users or processors.
• Application tier changes. Custom Forms, Reports, Workbooks and Java programs need Internet Application Server Enterprise Edition licenses for the users or processors where the changes run.

An application specific full use database license bought with a partner application is tied to that application, so it does not solve the problem either. The module list is the license you can see, while the database underneath usually decides the settlement.

What about older concurrent user entitlements?

Older EBS contracts sometimes carry legacy concurrent or floating user entitlements that behave differently from named Application Users. They are rare, valuable and easy to lose in a consolidation. Identify them before any restructure, using our guide to managing EBS concurrent licensing.

How do you check which EBS modules you actually use?

You check with a four way reconciliation of what you licensed, what people use, what is enabled and what interfaces touch. Most companies compare only the first two, which is why errors in both directions survive for years. The EBS data dictionary holds the evidence for all four.

Place every module in one of three groups from the results: licensed and used, licensed but shelf, or used without a license. The first group needs nothing. The second is support you can stop paying, and the third is a gap you want to license on your own timing.

What have we seen in recent Oracle EBS license reviews?

Across roughly 15 to 20 Oracle EBS license reviews we ran in 2024 and 2025, the gap between the order form and actual use was wide in both directions. Mid market and large companies ran between 12 and 30 modules with daily activity, against entitlement lists carrying 20 to 45 lines.

• Used without a license. On average, 3 to 5 modules were enabled or touched by interfaces with no license line behind them. Each was a six figure audit exposure.
• Licensed and idle. 2 to 4 fully licensed modules had zero active responsibilities and were still paying 22 percent support.
• Timing of gap purchases. Where buyers licensed real gaps before an audit, negotiated prices for the same modules landed 40 to 60 percent below Oracle's opening audit positions.

The difference between entitlement and use 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.

Why a yearly usage report and true up is the wrong routine

The usual advice is to run a usage report once a year and true up whatever it finds. We disagree, because in our reviews annual true ups consistently overpaid. Companies bought modules at close to list under audit pressure while paying support on shelved modules that no one reconciled.

The report told them what they owed and never what they could stop paying for. A quarterly sweep of responsibilities, module flags and interfaces finds both. Terminate support on proven shelf at the next renewal, within the license set rules, and license real gaps at negotiated rates before anyone asks.

In an audit, Oracle negotiates against a quantified liability. Outside one, it negotiates against your willingness to walk away.

What will Oracle say about your EBS modules, and how should you answer?

Expect pushback on shelf terminations and on usage findings alike. These are the lines we hear most often on EBS, with replies that hold up.

• "Sourcing is part of your Purchasing license set, so you cannot drop it." The support policies allow you to reduce a license set by terminating licenses with a letter. Ask for the repricing of the remaining lines on that order in writing before you decide.
• "The module is installed, so you are using it." EBS installs every module. Point to the responsibility extract, the transaction count and the interface inventory, all pulled the same day.
• "Your reporting tool reads Payables tables, so it needs a license." Show what the interface reads and that it exercises no module functionality, then ask Oracle to name the contract term it relies on.
• "License the gap now at the audit price, or the finding escalates." Offer to license the confirmed gap at the discount on your last comparable order. Audit list price is an opening number.
• "Your EBS investment will be recognized in the Fusion deal." Ask for the credit amount, what it applies to and when it expires, written into the ordering document.

Which contract terms should you ask for on your next EBS order?

• A price hold on named modules. The same discount for added users or listed modules for a fixed period, so a gap found later is priced at your rate.
• A cap on the support uplift. A written annual cap removes the uplift argument from every renewal.
• A fixed Employee count date. State when the Employee count is measured and which contractor groups sit outside it because they neither use nor are tracked by the programs.
• Repricing shown in advance. A worked repricing calculation attached to any renewal quote where you plan a termination.

How do third party support and a Fusion move change the module list?

Third party support cuts the cost of the modules you keep, and a Fusion proposal is sized from the modules Oracle believes you run. Either way, the reconciled module list comes first.

Is third party support realistic for EBS?

Third party support is more credible on EBS than on almost any other Oracle product. The release is mature, and the patch stream matters less each year. It saves roughly half the annual support bill and gives you a real alternative to raise in a renewal.

The trade is the loss of new patches and Oracle's regulatory payroll updates. If you run EBS Payroll, price how you will handle tax and legislative changes before you switch. Our third party support guide covers the provider options.

How does the EBS module list shape a Fusion quote?

Oracle sizes a Fusion Cloud proposal from the footprint it believes you run, so an inflated EBS entitlement list produces an inflated subscription. Reconcile first, then compare the target side in the Fusion module list and our guide to moving from on premises Oracle applications to Fusion Cloud.

Perpetual EBS licenses do not convert into subscription credit as a matter of right. Anything you get is negotiated, usually as a discount or a support bridge. A clean, documented EBS position strengthens your hand, while a messy one is a discovery exercise Oracle gets to run for you.

When should you start work before an EBS support renewal?

Start twelve months before the support renewal date on the order that holds your largest modules. Terminations, repricing checks and gap purchases each take time, and each depends on the one before it.

What to do next

1. Reconcile four ways. Compare the ordering documents against responsibility assignments, module flags and interface reads, and place every module in one of the three groups.
2. Sweep every quarter. Extract responsibility assignments and module flags quarterly, so new sprawl is caught in weeks rather than at the next audit.
3. Build the evidence before you ask. Pull the responsibility extract, twelve month transaction count and interface inventory on the same date, and keep them as the file behind any support termination.
4. License real gaps early. Buy confirmed gaps at negotiated rates before an audit, never at audit list price.
5. Check the database under the modules. Confirm that no reporting schema, warehouse feed or custom table breaches the restricted use grant.
6. Bring in the Oracle practice. Our Oracle team can run the reconciliation and the renewal negotiation with you.

Frequently asked questions