EBS module licensing is per module, which means each Oracle E Business Suite module you install or configure needs its own license, and an installed module nobody licensed is one of the most common application audit findings.
How is EBS licensed by module?
Oracle E Business Suite is licensed module by module, not as a single suite. Financials, Purchasing, Order Management, Human Resources, and each other product is a separately licensed program with its own metric, so your entitlement is the sum of the modules you bought, not a blanket right to the whole application. A finding starts wherever an installed or configured module is not on that list.
Because EBS ships as an integrated stack, modules can be present without being deliberately licensed. The buyer move is to maintain a clear map of licensed modules against installed and configured modules, so the scope is something you assert rather than something an auditor discovers.
What metrics apply to EBS modules?
EBS modules are licensed mostly on Application User or on a module specific metric. Application User counts named individuals authorised to use the module, and some modules use metrics tied to their business, such as expense reports, employees, or revenue. The metric is set in the ordering document, so two customers running the same module can owe very different counts depending on what they signed.
Getting the metric right is half the compliance battle. A module licensed by Application User is undercounted when authorised users grow past the purchased number, and that drift is exactly what an audit measures.
EBS scope, where modules hide
| Source of scope | Why it is a risk | Buyer move |
|---|---|---|
| Configured but unused module | Configuration can count as use | Decommission properly and document it |
| Shared responsibilities | One login touches several modules | Map responsibilities to licensed modules |
| Self service access | Employees count as users | Confirm the metric covers self service |
| Custom code and interfaces | Indirect use of a module | Trace interfaces to the module they touch |
How does indirect use widen EBS scope?
Indirect use widens scope when a person or system that is not a named user still drives the module through an interface. A custom application, a bot, or a third party system that reads from or writes to an EBS module can count as use of that module, which means the user population is larger than the named logins suggest. Oracle looks closely at interfaces precisely because they hide users.
The defense is to trace every interface to the module it touches and confirm the metric covers that access. This is contract dependent, so the precise treatment of indirect use should be read against your agreement rather than assumed from policy.
How do you remove an EBS module from scope?
You remove a module from scope by decommissioning it properly and recording that you did. Disabling responsibilities, removing the configuration, and documenting the date and method gives you evidence that the module is no longer in use. Simply ceasing to use a module without removing access leaves it installed and configured, which an auditor can still count.
Proper decommissioning is one of the cleanest savings in an application estate. Shedding modules nobody uses, with documentation, both reduces the license footprint and removes support cost that runs at roughly 22 percent of fees with annual escalation.
What is the buyer move on EBS module scope?
The buyer move is to keep an accurate module map, confirm the metric on each licensed module, trace indirect use through interfaces, and decommission anything unused with evidence. EBS audits reward customers who can hand over a clean scope statement and punish those who let the integrated stack blur the line between licensed and installed.
We position as an independent buyer side advisory with deep Oracle licensing expertise. On EBS, that expertise turns a sprawling application estate into a defined, defensible scope before any audit letter arrives.
A worked example
Consider an anonymized manufacturer running Oracle E Business Suite. Over years of projects, two modules had been configured for pilots that never went live, and a custom warehouse system fed Order Management through a service account. The preliminary finding counted both pilot modules and treated the warehouse population as indirect users at list price. No client names, sector level example only.
The buyer side defense documented that the pilot modules had been decommissioned, traced the warehouse interface to a defined and already licensed user group, and produced a clean module map. The settled scope reflected the modules genuinely in use rather than everything the auditor could find installed.
Where to go next
This piece links up to the Oracle License Compliance Guide. Keep reading across the cluster:
Download the Oracle License Compliance Guide for the full framework, or get a quote.