Oracle E-Business Suite Licensing Guide

What Is Oracle EBS Licensing?

Oracle E-Business Suite (EBS) is Oracle's flagship on-premises ERP platform — a collection of integrated business applications covering Financials, Human Resources, Supply Chain, Manufacturing, Projects, and CRM. Unlike Oracle Database licensing, which applies consistent metrics across deployments, EBS licensing operates on a product-by-product basis with two primary metrics: Named User Plus (NUP) and Processor.

The EBS licensing framework has been layered with application-specific user minimums, module-level bundle packages, and a critical distinction between Full Use and Application Specific Full Use (ASFU) licenses that creates significant compliance risk for organizations that have expanded their EBS deployments over time. Not affiliated with Oracle Corporation.

The Two Core EBS License Metrics

Every EBS deployment must be licensed under one of two metrics. Which metric applies — and which is more economical — depends on user counts, server infrastructure, and which EBS modules you deploy.

Named User Plus (NUP)

The Named User Plus metric licenses EBS by the number of individuals authorized to access the application. "Named" means identified individuals — not concurrent users. If someone has credentials to log in, they consume a Named User Plus license. Key rules:

• Minimum NUP counts per Processor apply (typically 10 NUP per Processor for most EBS products). A server with 4 licensed Processors mandates at least 40 NUP even if you have only 15 real users.
• Users who access EBS indirectly through integrations, APIs, or middleware typically require licenses unless a specific carve-out exists in your contract.
• Self-service users (expense submissions, timesheet approvals, HR self-service) count as Named Users even if their interaction is minimal.

Processor Metric

The Processor metric licenses based on physical processor cores running EBS, multiplied by the Core Factor Table coefficient. Intel/AMD x86 cores carry a 0.5 factor — 32 physical cores require 16 Processor licenses. Processor licensing is chosen when user counts are large or hard to track, but carries its own risks: all physical cores on a host running EBS must be licensed unless Oracle-approved hard partitioning is used. VMware and Hyper-V do not qualify.

Full Use vs. Application Specific Full Use (ASFU)

This is the most misunderstood dimension of EBS licensing, and it creates significant audit exposure for organizations that acquired licenses under an EBS bundle deal.

Full Use (FU) licenses allow you to use the licensed product for any purpose and deploy it independently of other products. Application Specific Full Use (ASFU) licenses are restricted — they can only be used in conjunction with the specific Oracle application they were bundled with. An ASFU license for Oracle Database acquired as part of an EBS deal cannot be used to run non-EBS workloads, even on a different server.

Oracle audits routinely identify customers running ASFU-licensed Oracle Database instances for workloads unrelated to EBS — a compliance finding that typically requires a retroactive upgrade to Full Use licenses at list price.

Oracle EBS Module Licensing

EBS is structured as 200+ discrete application modules, each licensed separately or as part of a bundle. Understanding which modules require separate licenses versus which are included in a bundle is essential for managing costs and audit exposure. See our detailed breakdown: Oracle EBS Module Licensing Guide.

Product Family	Key Modules	Typical Metric
Financials	GL, AP, AR, Fixed Assets, Cash Management	NUP or Processor
Human Resources	Core HR, Payroll, Self Service HR, Time & Labor	NUP (often per employee)
Supply Chain	Inventory, Purchasing, Order Management, iProcurement	NUP or Processor
Manufacturing	WIP, BOM, MRP, Cost Management, Quality	NUP or Processor
Projects	Project Costing, Project Billing, Grants Accounting	NUP

EBS Support Costs: The 22% Annual Fee

Oracle charges 22% of net license value annually for Oracle Software Support on EBS. On a $5M net license value, that is $1.1M per year — compounding with annual escalation clauses of 3-5%. After ten years, cumulative support fees typically exceed the original license cost by a wide margin.

Support covers security patches, tax/regulatory updates, bug fixes, and My Oracle Support access. It does not cover new features, custom code, or performance consulting. For mature EBS deployments, third-party support providers offer equivalent coverage at 50% of Oracle's fee. See our detailed analysis: Oracle EBS Support Costs guide and our Oracle support cost reduction service.

EBS Licensing in Virtualized Environments

The majority of EBS deployments run on VMware ESXi or similar platforms — and Oracle's licensing rules for these environments are highly unfavorable. Oracle's position is that soft partitioning (VMware, Hyper-V, KVM, and all major hypervisors) does not limit the number of cores that must be licensed under the Processor metric. All physical cores on a VMware host running EBS must be licensed, regardless of vCPU allocation to the EBS virtual machine.

The only partitioning technologies Oracle recognizes for limiting Processor license requirements are Oracle VM Server for x86 and SPARC hard partitioning. Every other virtualization solution is treated as soft partitioning. This is one of the highest-value areas to address in a proactive Oracle compliance review.

Common Oracle EBS Audit Findings

Oracle's License Management Services (LMS) team audits EBS environments using SQL scripts that extract user counts, module access patterns, responsibility assignments, and server configuration. The most frequent findings are:

• Self-service user undercount: Employees with self-service portal access (iExpenses, Self Service HR, iProcurement) who were never counted in the NUP license position.
• Unlicensed modules: Modules activated during implementation but never formally licensed — discovered when LMS maps responsibilities to products not in the customer's license order.
• Processor undercount on VMware: EBS customers licensing only the vCPUs allocated to their EBS VM rather than all physical cores on the host.
• Indirect access: Third-party applications querying EBS data, with Oracle arguing the users of those applications require EBS licenses.
• ASFU misuse: Oracle Database ASFU licenses used for non-EBS workloads.

For full audit preparation and defense guidance, see our Oracle EBS Licensing Audit guide and the broader Oracle Audit Defense Guide.

EBS vs. Oracle Fusion Cloud: The Migration Licensing Question

Many organizations are evaluating migration from Oracle EBS to Oracle Fusion Cloud ERP. The licensing implications are substantial: Fusion Cloud operates on a subscription model (per-employee or per-user per month) rather than perpetual licenses, and existing EBS perpetual licenses do not transfer automatically to cloud subscription credits. During the 18–36 month migration period when both systems run in parallel, double-licensing exposure is a real risk. See our detailed comparison: Oracle EBS vs. Fusion Cloud Licensing.

User Licensing in EBS: Who Counts?

For a detailed breakdown of every user category that requires a Named User Plus license — including direct users, self-service users, workflow users, and the indirect access question — see our dedicated guide: Oracle EBS User Licensing Models.

Research and White Papers

For detailed analysis of specific EBS licensing scenarios, contract negotiation tactics, and audit response strategies, our research library is at Oracle Licensing White Papers. For documented client outcomes, see our case studies. Our Oracle license optimization service is the starting point for most EBS engagements.