What Is the Oracle EBS Application User License?
The Oracle EBS Application User license is a metric specifically designed for Oracle E-Business Suite application modules. Unlike the general Named User Plus metric, which licenses access to the underlying Oracle technology platform, the Application User metric licenses use of a specific EBS application product—for example, Oracle Financials, Oracle HR, or Oracle Order Management.
The Application User definition in Oracle's licensing terms is: "an individual authorized to use the applicable Oracle application programs that are installed on a single server or multiple servers." This per-person metric is counted on the same basis as Named User Plus—authorized users, not concurrent or active ones—but applies only to EBS application layer usage, not to the Oracle Database or Fusion Middleware stack underneath it.
This distinction matters enormously for cost. Application User license list prices are typically lower than Named User Plus prices for equivalent EBS modules, and the metric does not grant rights to the Oracle Database technology stack independently. Organizations that have properly separated their technology and application licenses often find Application User pricing reduces EBS licensing costs by 30 to 50 percent compared to an equivalent Named User Plus position.
Application User vs. Named User Plus: The Critical Difference
The core distinction between Application User and Named User Plus in Oracle EBS licensing is scope of rights. Named User Plus is a full-use metric: it grants rights to the Oracle program (including the underlying technology components) for any use case consistent with the license terms. Application User is a restricted metric: it grants rights only for the specific EBS application module it is attached to.
This means that an organization licensing EBS Financials under Application User does not automatically have rights to use Oracle Database independently for other purposes—a Named User Plus or Processor license for Oracle Database would still be required if the database is used beyond the scope of EBS. Most organizations running EBS have Oracle Database licensed separately under Processor, making Application User an efficient way to license EBS application users without duplicating technology stack costs.
| Metric | Covers Application Layer | Covers Technology Stack | Minimum Count | Typical Use Case |
|---|---|---|---|---|
| Application User | Yes — specific module | No | Varies by module | Large EBS user populations |
| Named User Plus | Yes — full use | Yes — full stack | 25 per Processor | Small deployments, mixed use |
| Processor | N/A — infrastructure | Yes | By Core Factor | Large server, small user base |
Which EBS Modules Support Application User Licensing?
Not all Oracle EBS modules are available under the Application User metric. Oracle's price list designates specific products as available for Application User licensing, and the availability changes periodically. As of 2026, the core EBS suite modules—Financials, HR, Supply Chain, Manufacturing, and CRM—are generally available under Application User licensing.
Modules that are licensed under Application User include Oracle Payables, Oracle Receivables, Oracle General Ledger, Oracle Fixed Assets, Oracle Cash Management, Oracle Purchasing, Oracle Order Management, Oracle Inventory Management, Oracle HRMS, Oracle Payroll, and Oracle Projects. Each carries its own per-user price point that differs from the equivalent Named User Plus price.
It is important to verify the specific metric availability for each module in your Oracle price list or ordering document, as Oracle has occasionally restricted Application User availability for certain products. Our Oracle EBS Licensing Guide details current metric availability by module.
Are You Using the Right EBS Metric?
Many organizations overpay for EBS because they licensed under Named User Plus when Application User would have been significantly cheaper. Our compliance review maps your current position and identifies the optimal metric structure for your deployment.
Schedule a Compliance Review →Application User Minimums and the 10-User Floor
Oracle imposes minimum user counts for Application User licensing, though the specific minimums are set at the product level rather than via a Processor-based formula. The standard minimum for most EBS application modules is 10 Application Users. This means that even if only 6 people use Oracle Payables, you must license at least 10 Application Users for that module.
This minimum floor is significantly more favorable than the Named User Plus minimum (25 per Processor), particularly for organizations running EBS on large servers. A company running Oracle Financials on a 16-processor server would face a Named User Plus minimum of 400 users, compared to just 10 Application Users under the alternative metric—a potentially enormous cost difference depending on list prices and negotiated discounts.
Note that Oracle has different minimum rules for certain specialized modules, particularly those in the CRM, Projects, and Supply Chain areas. Always verify the applicable minimum for each specific product before committing to Application User licensing in a contract negotiation.
What Application User Licensing Does NOT Cover
The Application User metric has several important exclusions that organizations frequently miss during license reviews. Understanding these gaps is essential to avoiding compliance exposure.
Technology stack components are not covered by Application User licenses. If your organization uses Oracle Database features independently of EBS—for example, using Oracle Database Vault, Oracle Advanced Security, or Oracle Partitioning for non-EBS data—those features require separate Named User Plus or Processor licenses.
Oracle Middleware components like Oracle WebLogic Server, Oracle Identity Manager, or Oracle SOA Suite, when used outside of the EBS application context, are not covered by Application User licenses. EBS customers typically receive rights to use Fusion Middleware components that are embedded in the EBS application stack, but extending those components to non-EBS use cases requires separate licensing.
Indirect access remains a risk under Application User licensing. If third-party applications access EBS application data, Oracle's position is that users of those applications require Application User licenses for the relevant EBS modules—the same indirect access exposure that applies under Named User Plus. The metric does not protect you from indirect access claims; it only changes the per-unit cost of the exposure.
Review our Oracle compliance review service for a systematic approach to mapping all EBS access vectors and ensuring your Application User count is both complete and defensible.
Transitioning from Named User Plus to Application User
Organizations that originally licensed EBS under Named User Plus and want to convert to Application User licensing must do so through a contractual amendment. Oracle does not automatically allow metric swaps, and the conversion will typically require Oracle's sales team approval and a formal order document.
The business case for conversion is usually compelling when a large user population is in play. For an organization with 2,000 EBS Financials users, the difference between Named User Plus pricing and Application User pricing can represent millions of dollars at list price, with similar savings preserved at negotiated discount levels. However, the conversion must be negotiated carefully—Oracle may attempt to impose conditions on the conversion that offset some of the savings, such as requiring additional support commitments or restricting metric conversion for certain modules.
Our Oracle contract negotiation team has executed Application User conversions for multiple large EBS customers. We understand Oracle's internal approval process, the commercial levers available to buyers, and the contractual language required to protect your position. See our white papers for a detailed guide to EBS metric optimization at renewal.
Application User Licensing in Oracle Audits
During Oracle LMS audits, Application User counts are verified through EBS security reports that identify all accounts authorized to access specific application modules. Oracle's audit scripts extract this data directly from EBS security tables, cross-referenced against the specific product licenses in your contract.
Audit risk under Application User licensing is concentrated in two areas: first, users authorized for modules beyond what is licensed (for example, an employee provisioned with access to both Oracle Payables and Oracle Purchasing when only Payables is licensed); and second, indirect access through third-party integrations that Oracle claims extends Application User obligations to non-EBS users.
Organizations approaching an Oracle EBS audit should conduct a pre-audit license position review that maps provisioned application access against contractual entitlements. This is particularly important when the EBS deployment has grown organically over many years and user provisioning has not been systematically aligned with license counts. Our Oracle Audit Defense Guide covers audit preparation for EBS Application User positions in detail.
Oracle Licensing Experts is an independent advisory firm. Not affiliated with Oracle Corporation. Oracle and Oracle E-Business Suite are registered trademarks of Oracle Corporation.