Oracle EBS application modules. The complete 2026 map.

Oracle E Business Suite ships as separately licensed modules across Financials, Procurement, Projects, HCM, Supply Chain, Manufacturing, and CRM. The audit risk is not the modules you bought. It is the ones that are enabled, installed, or touched by interfaces without a license behind them.

What modules make up the Oracle EBS application map?

The E Business Suite catalog groups into eight families, each licensed per module against the applications price list published under Oracle corporate pricing. The family is the planning unit; the module is the license unit.

Why does the family versus module distinction matter?

Because audits price at module level. Owning Purchasing does not license iProcurement, and owning Core HR does not license Payroll. Each line on the order form is the entire entitlement.

Which license metrics apply across the module list?

Application User is the default metric: a named individual authorized to use the module, regardless of actual login frequency. Authorization, not activity, is what Oracle counts.

• Application User: most Financials, SCM, Manufacturing, and CRM modules; counted per authorized person per module.
• Employee: HCM and self service modules; counted against total workforce, not users, which multiplies fast.
• Transaction metrics: Expense Reports, Order Lines, and invoice volumes price some modules by throughput.
• Enterprise metrics: revenue or cost of goods based pricing appears on some industry and EPM modules.

What does the Employee metric really count?

Every person on the payroll the module processes, including part time staff and often contractors, whether or not they ever log in. A self service module licensed per Employee scales with headcount, and audits reconcile against HR records.

How do unlicensed modules get used without anyone deciding to?

EBS installs every module in the technology stack; licensing is a paper boundary, not a technical one. Usage accrues through responsibility assignments, enabled module flags, and integrations long before procurement hears about it.

• Responsibility sprawl: a super user responsibility that includes unlicensed module functions creates countable authorization.
• Module flags: implementation partners enable modules for setup convenience and never disable them.
• Interface reads: custom code and middleware querying module tables has been argued as use by Oracle LMS in audits we defended.

Are custom schemas reading EBS tables really a license event?

Oracle has claimed so where the custom code exercises module functionality rather than just reading data. The defensible position requires documenting what each interface touches and why it is not module use. Build that file before the audit, not during.

How do you turn the module list into negotiating leverage?

The module inventory is the leverage. A reconciled map of licensed, used, enabled, and interfaced modules lets you terminate shelf support, license real gaps on your timetable, and enter any support renewal conversation with the facts.

1. Extract responsibility assignments and module flags from the estate quarterly.
2. Reconcile against the order forms; classify each module as licensed and used, licensed shelf, or used unlicensed.
3. Document every interface that touches module tables and its function.
4. Terminate support on provable shelf at the next renewal window.
5. License genuine gaps proactively at negotiated rates, never at audit list price.

What does proactive gap licensing save versus an audit settlement?

In our file, negotiated proactive purchases landed 40 to 60 percent below the list price positions Oracle opened with in audit settlements for the same modules. The discount for moving first is the largest single number in EBS compliance economics.

Where the common advice on EBS module compliance is wrong

The standard advice is to run a usage report once a year and true up whatever it finds. We disagree. In roughly 15 to 20 EBS license reviews Morten Andersen ran in 2024 to 2025, annual true ups systematically overpaid: estates bought modules at near list under audit pressure while paying 22 percent support on 2 to 4 fully shelved modules nobody reconciled. The buyer side move is a quarterly responsibility and interface sweep, support termination on provable shelf, and proactive gap licensing at negotiated rates. Oracle prices the same module very differently when you are not in a corner.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Pull the full responsibility assignment and module flag extract from EBS.
2. Build the four way reconciliation: licensed, used, enabled, interfaced.
3. Document the function of every integration touching module tables.
4. Terminate support on modules you can prove were never used.
5. Price genuine gaps proactively before any audit letter arrives.
6. Repeat the sweep quarterly; module drift is continuous.

White Paper · Oracle

Oracle E-Business Suite Licensing

Read it free.

Read the white paper

Frequently asked questions

How many modules does Oracle E Business Suite have?

Well over a hundred separately licensed modules across eight families: Financials, Procurement, Projects, HCM, Supply Chain, Manufacturing, CRM, and EPM. Each module is its own price list line and entitlement; the family is only a planning grouping.

What license metrics does Oracle EBS use?

Application User is the dominant metric, counting authorized named users per module. HCM and self service modules typically use the Employee metric against total workforce, and some modules price per transaction volume such as Expense Reports or Order Lines.

Does enabling an EBS module without using it create license liability?

It creates audit exposure. EBS installs all modules technically, and Oracle counts authorization and enablement signals, not just logins. Enabled flags and responsibilities that include unlicensed module functions are the most common findings in our reviews.

Do interfaces and custom code count as EBS module usage?

Oracle has claimed module use where middleware or custom schemas exercise module functionality through its tables. The defense is contemporaneous documentation of what each interface touches. A third of audits we defended included an interface based claim.

Can you drop support on unused EBS modules?

Yes, with care. Oracle's matching service level and repricing rules constrain partial terminations, but provable shelf modules can come off support at renewal. In our reviews estates carried 2 to 4 shelved modules paying 22 percent support for nothing.

Is it cheaper to license a module gap before or after an audit?

Before, by a wide margin. Proactive negotiated purchases in our 2024 to 2025 file landed 40 to 60 percent below the list price positions Oracle opened with in audit settlements for identical modules.