The bottom line on Oracle EBS licensing
Bottom LineOracle EBS licensing is two licences pretending to be one: the application modules, sold per Application User, and the technology stack beneath them — Oracle Database, WebLogic, and Forms — sold separately on Processor or Named User Plus. Most overspend comes from over-provisioned Application User counts and full-use database options enabled under restricted-use rights. With Premier Support committed to at least 2037, you can right-size on your own timeline, not Oracle's.
Oracle E-Business Suite is one of the most over-licensed estates we see. The application looks like a single product, but the bill is built from per-module user counts, separately licensed database technology, and contractual minimums that override your real usage. This guide takes apart each layer so you can see exactly what you are paying for — and what you can stop paying for.
Key takeaways
- EBS is licensed on two tracks. Application modules sell per Application User; the underlying Oracle Database, WebLogic, and Forms are licensed separately on Processor or Named User Plus — most EBS audit findings come from the second track being missed.
- Module list prices run high. EBS modules list from roughly $4,595 per Application User (Inventory) up to about $5,765 (Financials), plus 22% annual Premier Support; a fully provisioned Financials and Procurement user lists near $11,000 (Oracle Applications Global Price List, 2026).
- Minimums override your real usage. Oracle Database Enterprise Edition carries a 25 Named User Plus per-processor minimum, and EBS modules carry their own ordering-document minimums — when the minimum exceeds your headcount, you pay the minimum (Oracle licensing rules, 2026).
- Premier Support runs to at least 2037. Oracle's ninth consecutive annual extension keeps EBS 12.2 fully supported through at least 2037 under Continuous Innovation, with release 12.2.15 shipped October 2025 (Oracle EBS blog, 2026) — no deadline forces a change.
- EBS estates are over-provisioned 20–35%. Across our engagements, authorised Application User counts exceed people who actually log in by 20–35% on average — companies pay 22% support every year on licences for users who left or never used the module (Oracle Licensing Experts benchmark, 2026).
What to do this quarter, by seat
CIO Strategy
- Reject any "EBS is end-of-life" framing — Premier Support is committed to at least 2037, so licence decisions are commercial, not forced.
- Commission an independent entitlement-versus-deployment baseline across application modules and the technology stack before any renewal or audit.
- Separate the application licence question from the database licence question — they are governed by different metrics and different rules.
CFO Capital
- Treat the 22% annual support line as the real cost of EBS — every over-provisioned licence compounds that cost for the life of the estate.
- Require a right-sizing pass before each support renewal; removing dormant Application Users is the highest-return action available.
- Quantify the residual value of perpetual EBS entitlements before any cloud or Fusion conversation puts them at risk of write-off.
SAM / ITAM Manager Compliance
- Build a per-module Application User reconciliation: authorised users versus active logins, terminated employees flagged for removal.
- Scan for database options and management packs — Diagnostics, Tuning, Advanced Compression, Partitioning — enabled under restricted-use rights.
- Confirm every technology-stack component runs within its restricted-use grant and document the entitlement position before any 45-day audit notice.
VP Procurement Negotiation
- Benchmark every module quote against negotiated norms of $2,500–$3,500 per Application User, not Oracle's list price.
- Negotiate price holds and capped support uplift into the ordering document, where they are contractually binding — not in email.
- Use the 2037 support runway to your advantage: you have no deadline, so make Oracle compete for every renewal and net-new line.
The EBS licensing framework, question by question
How does Oracle E-Business Suite licensing actually work?
Oracle E-Business Suite is Oracle's on-premise ERP, financials, supply chain, procurement, and HR application suite, currently at release 12.2. It is licensed on two distinct tracks that customers routinely conflate: the application modules, sold per named user, and the technology stack — Oracle Database, WebLogic, and Forms — that runs beneath them, licensed separately. Treating EBS as one product is the first and most expensive mistake.
The application track uses the Application User metric, where each module is licensed independently by authorised headcount. The technology track is governed by Oracle Database and middleware rules, with their own metrics, minimums, and audit exposure. Understanding which track a given cost belongs to is the foundation of every optimisation and every successful audit defence on an EBS estate.
Draw your EBS estate as two layers on one page — modules on top, technology stack below — and assign every licence you own to one layer. The licences nobody can place are exactly where your audit risk and your savings both live.
What is the Application User metric and how does Oracle count it?
The Application User metric is Oracle's named-user model for E-Business Suite: it counts every individual authorised to access a licensed module, regardless of how often — or whether — they actually log in. It is not a concurrency metric. Because each module is licensed separately, one person using both Financials and Procurement consumes two Application User licences, and that multiplication is where most EBS budgets quietly inflate.
The metric rewards discipline and punishes drift. Authorised access granted years ago to employees who have since left, changed roles, or never used the module still counts — and still attracts 22% support every year. A clean Application User position requires reconciling the authorised list against real logins on a recurring basis, not just at audit time.
Across 600+ Oracle engagements, authorised EBS Application User counts exceed the population that actually logs in by 20–35% on average. At list pricing, every 100 dormant Financials users represents roughly $575,000 of licence value carrying $126,000 of annual support — paid for nothing (Oracle Licensing Experts benchmark, 2026).
How much does Oracle EBS licensing cost per user in 2026?
EBS application modules list from roughly $4,595 per Application User for modules such as Inventory up to about $5,765 for Financials, with annual Premier Support charged at 22% of net licence value on top (Oracle E-Business Suite Applications Global Price List, 2026). A fully provisioned Financials-and-Procurement user lists near $11,000 before support. List price, however, is a negotiating anchor, not a market price.
On real enterprise deals, negotiated pricing commonly lands at $2,500 to $3,500 per Application User, depending on volume and deal timing. The lesson is blunt: never accept a module quote at list, and never let Oracle bundle modules you cannot map to active users. The discount you negotiate on the licence repeats every year in the support line that follows it.
Time net-new EBS purchases to Oracle's fiscal quarter and year-end (Oracle's fiscal year ends 31 May), when discount authority is deepest. Pair the order with a documented price hold for future modules so Oracle cannot reset to list when you expand.
Do I license the Oracle Database and technology stack separately under EBS?
Yes — and this is the single most misunderstood point in EBS licensing. The Oracle Database, WebLogic Server, and Forms beneath E-Business Suite are licensed separately from the application modules, on Processor or Named User Plus. EBS ships with a Restricted Use License: limited technology rights that let the database run the application only, not full-use database functionality.
The moment anyone uses the database for something beyond running EBS — a custom schema, a reporting data mart, a third-party application sharing the instance — restricted-use rights no longer cover it, and a full-use licence is required. This boundary is exactly where Oracle's audit teams concentrate, because crossing it is easy, undocumented, and expensive to remediate after the fact.
Database options and management packs — Diagnostics Pack, Tuning Pack, Advanced Compression, Partitioning — are frequently enabled by default and are not covered by EBS restricted-use rights. An option discovered active in an audit becomes a back-licence claim plus back support, not a footnote. Map them before Oracle does.
What are Oracle's EBS license minimums — and why do they inflate the bill?
Oracle enforces contractual minimums that override your actual user count. Oracle Database Enterprise Edition carries a minimum of 25 Named User Plus per processor, and EBS application modules carry their own minimums set in the ordering document — often 10 users per module, with some modules such as Financials Hub requiring far higher counts (Oracle licensing rules, 2026). When the minimum exceeds your real headcount, you pay the minimum regardless.
The Named User Plus metric counts each distinct individual or device authorised to access the software, and the Processor Metric counts licensable cores using Oracle's Core Factor Table. For a small or lightly used module on a multi-core server, the per-processor minimum can require you to license dozens of users you do not have — which is why minimums, not headcount, often set the floor on an EBS bill.
"List every minimum that applies to my EBS modules and technology stack — per-module user minimums and per-processor NUP minimums — and show where each is documented in my ordering documents." Get the minimums on paper before you size anything.
Where does Oracle's LMS find compliance gaps in an EBS audit?
Oracle's LMS (License Management Services) is the team that conducts Oracle compliance audits, and on EBS estates it targets three things: database options and management packs enabled without a full-use licence, Application User counts that have drifted above entitlement, and technology-stack usage that exceeds restricted-use rights. All three are common, and all three are findable in a single scan.
An Oracle audit typically opens with a 45-day notice and a request to run Oracle's measurement scripts. The strongest defence is to have already run your own baseline — entitlements versus deployment, module by module, option by option — so you control the narrative and the numbers before Oracle's tools produce theirs. Audit defence is won in the preparation, not the negotiation.
A global distributor faced a seven-figure EBS audit claim built largely on Diagnostics and Tuning packs enabled under restricted-use rights. We disabled the unused packs, reconciled Application User counts down by 28%, and closed the claim for a fraction of the original demand. See related Oracle licensing case studies with hard numbers.
How do I right-size and cut my Oracle EBS licensing cost?
Right-size before you renew. Reconcile authorised Application User counts against people who actually log in, terminate licences for departed users, retire modules nobody uses, and confirm no full-use database options are enabled under restricted-use rights. Because Premier Support is billed at 22% of net licence value every year, removing over-provisioned licences before a renewal compounds the saving for the entire remaining life of the estate.
The sequence matters. Clean up the entitlement position first, document it, then take it into the renewal — never the other way round. Oracle prices the renewal off your current support base, so every dormant licence you remove first is a permanent reduction, while every licence you carry into the renewal is one you keep paying for indefinitely.
Run the right-sizing pass at least 120 days before the support anniversary. Oracle's repricing and reinstatement rules make late terminations far weaker; the customers who save the most start the reconciliation a full quarter ahead of renewal.
Which EBS metric fits your deployment?
Application User / NUP
Defined population · internal usersA known, countable set of internal employees uses the modules. Per-user licensing is cheapest — but only if you keep the authorised list reconciled to active users and remove leavers promptly.
Processor
Uncountable / external usersExternal, customer-facing, or high-concurrency access where headcount cannot be counted. Processor licensing caps the cost — verify the Core Factor and license only the cores actually running EBS.
Right-size in place
Over-provisioned · stable estateAuthorised counts have drifted well above active use. Reconcile users, retire unused modules, disable unlicensed options, and cut the support base before the next renewal.
Remediate exposure
Options on · stack undocumentedFull-use database features run under restricted-use rights and the stack position is undocumented. Baseline entitlements versus deployment now, before Oracle's LMS issues a notice.
Decision matrix: the right EBS metric is set by two axes — whether your user population is countable, and whether your current position is clean or carries hidden technology-stack exposure.
Comparing the EBS licensing metrics
| Metric | How Oracle counts it | Strengths | Cautions |
|---|---|---|---|
| Application User | Per module, every authorised individual; not concurrent | Cheapest for defined internal populations; transparent and auditable | Licensed per module, so multi-module users multiply; dormant users still cost 22% support |
| Named User Plus | Each distinct authorised individual or device; per-processor minimums apply | Cost-effective for small, known user bases on the technology stack | 25 NUP per processor minimum on Database EE can exceed real users; counts include devices |
| Processor | Licensable cores via the Core Factor Table | Caps cost for external or uncountable, high-concurrency access | Expensive on large core counts; must verify Core Factor and isolate EBS cores |
Oracle EBS licensing glossary
- Oracle E-Business Suite (EBS)
- Oracle's on-premise ERP, financials, supply chain, procurement, and HR application suite, at release 12.2, with Premier Support committed through at least 2037.
- Application User
- Oracle's EBS named-user metric counting every individual authorised to access a licensed module, regardless of usage frequency, licensed separately per module.
- Named User Plus (NUP)
- An Oracle metric counting each distinct individual or device authorised to access the software, subject to per-processor minimums.
- Processor Metric
- An Oracle licensing metric based on the cores running the software, calculated using Oracle's Core Factor Table.
- Core Factor Table
- Oracle's published multiplier table converting physical processor cores into licensable processors for the Processor metric.
- Restricted Use License
- Limited technology rights bundled with EBS that let Oracle Database, WebLogic, or Forms run the application only — not full-use database functionality.
- Premier Support
- Oracle's full support tier — updates, fixes, certifications, regulatory changes — charged at roughly 22% of net licence value per year.
- Continuous Innovation
- Oracle's model of shipping EBS 12.2 application and technology updates as suite-wide patch sets with no major version upgrade or re-implementation.
- Management Pack
- A separately licensed Database add-on such as Diagnostics Pack or Tuning Pack, frequently enabled by default and a common EBS audit finding.
- CEMLI
- Customisations, Extensions, Modifications, Localisations, and Integrations layered on standard EBS that shape its cost and migration profile.
- LMS
- Oracle License Management Services — the team that conducts Oracle compliance audits, including of E-Business Suite estates.
- Custom Application Suite (CAS)
- An EBS licence type permitting customer-built applications to run on the licensed EBS technology foundation under defined terms.
Oracle EBS licensing: frequently asked questions
What licensing metrics does Oracle E-Business Suite use?
Oracle E-Business Suite is licensed primarily on two application metrics — Application User and Named User Plus — while the underlying technology stack of Oracle Database, WebLogic, and Forms is licensed separately on Processor or Named User Plus. Application User counts every individual authorised to use a module, not concurrent usage, and each module is licensed independently.
How much does Oracle EBS licensing cost per user in 2026?
Oracle EBS application modules list from roughly $4,595 per Application User for modules such as Inventory up to about $5,765 for Financials, plus annual Premier Support at 22% of net licence value (Oracle E-Business Suite Applications Global Price List, 2026). A fully provisioned Financials and Procurement user lists near $11,000. Negotiated pricing commonly lands at $2,500 to $3,500 per user.
What is the Application User metric in Oracle EBS?
Application User is Oracle's named-user metric for E-Business Suite that counts every individual authorised to access a licensed module, regardless of how often they log in. It is not a concurrent metric. Because each module is licensed separately, a person who uses Financials and Procurement consumes two Application User licences, which is why over-provisioned access drives most EBS overspend.
Do I license the Oracle Database separately under E-Business Suite?
Yes. The Oracle Database, WebLogic Server, and Forms that run beneath E-Business Suite are licensed separately from the application modules, on Processor or Named User Plus. EBS includes only restricted-use technology rights tied to the application; any full-use database feature, option, or management pack must carry its own licence, and unlicensed options are the most common EBS audit finding.
What are Oracle's EBS license minimums?
Oracle enforces contractual minimums that override your actual user count. Oracle Database Enterprise Edition carries a minimum of 25 Named User Plus per processor, and EBS application modules carry their own minimums set in the ordering document — often 10 users per module, with some modules such as Financials Hub requiring far more. When the minimum exceeds your real users, you pay for the minimum.
How long will Oracle support E-Business Suite 12.2?
Oracle has committed Premier Support for E-Business Suite 12.2 through at least 2037 under its Continuous Innovation model — the ninth consecutive annual extension since 2018 — with the latest release, 12.2.15, shipped in October 2025. There is no end-of-life forcing an upgrade or migration, so EBS licensing decisions can be made on commercial terms, not deadline pressure.
How can I reduce my Oracle EBS licensing and support cost?
Right-size before you renew. Reconcile authorised Application User counts against people who actually log in, terminate licences for departed users, retire unused modules, and confirm no full-use database options are enabled under restricted-use rights. Because support is billed at 22% of net licence value every year, removing over-provisioned licences before a renewal compounds the saving for the life of the contract.
Does Oracle audit E-Business Suite customers?
Yes. Oracle's License Management Services audits EBS estates and focuses on three areas: database options and management packs enabled without a full-use licence, Application User counts that have drifted above entitlement, and technology-stack usage beyond restricted-use rights. The strongest defence is an internal baseline of entitlements versus deployment built before Oracle issues a 45-day audit notice.
How we built this guide
This guide reflects Oracle Licensing Experts engagement data from E-Business Suite advisory work across manufacturing, distribution, financial services, and public-sector enterprises, combined with current Oracle pricing and support positions verified in mid-2026. Benchmarks branded "Oracle Licensing Experts benchmark" derive from our buyer-side engagements and are stated as ranges to protect client confidentiality. Every external figure is attributed to a primary or authoritative source below.
- Oracle — E-Business Suite Applications Global Price List (Application User module list prices, metrics): oracle.com applications price list (2026).
- Oracle — Application Licensing Table (EBS licence definitions and metrics): oracle.com application licensing table (2026).
- Oracle — EBS 12.2 Premier Support extended through at least 2037, Continuous Innovation: blogs.oracle.com/ebs (2026).
- Oracle — E-Business Suite Continuous Innovation on Release 12.2 roadmap (release 12.2.15, October 2025): oracle.com EBS roadmap (2026).
- Oracle — E-Business Suite Premier Support overview: oracle.com EBS support (2026).
Download the PDF edition
Take the full Oracle EBS Licensing Guide — the metric comparison, decision matrix, and audit-defence checklist — as a shareable PDF for your IT asset and procurement teams.
Request the PDF & a briefing →Keep building your Oracle applications position
Free weekly Oracle briefing
Audit alerts, E-Business Suite and Fusion roadmap intelligence, and negotiation tactics — from former Oracle insiders.
Stop paying support on licences you don't use
Get an independent, buyer-side baseline of your Oracle E-Business Suite estate — modules, users, and the technology stack — before your next renewal or audit. We find the over-provisioning Oracle never points out.