Oracle EBS Named User Plus Licensing

What Is Named User Plus in Oracle EBS?

The Named User Plus (NUP) metric licenses each individual who accesses Oracle software—directly or indirectly. For Oracle E-Business Suite, this means every employee, contractor, agent, customer, or automated process that interacts with EBS data is potentially a licensable user. Oracle's definition is deliberately broad: it is not limited to concurrent users, active users, or employees in specific roles.

The "Plus" in Named User Plus refers to the requirement that the license count must meet or exceed a minimum threshold. For most Oracle EBS products, that minimum is 25 Named User Plus licenses per Processor license equivalent. This minimum floor is critical—organizations with small active user counts can still face large license obligations if their server infrastructure implies a higher Processor-based minimum.

Oracle's EBS application suite covers modules such as Financials, HR, Supply Chain, Manufacturing, and CRM. Each module carries its own licensing requirements, but they all share the same Named User Plus metric definition. The question is not who logs in, but who has been authorized to access the system—a distinction Oracle exploits aggressively during audits.

Who Counts as a Named User Plus in EBS?

Oracle's licensing policy requires that you count every individual who could access the software, regardless of how often—or whether—they actually do. This means that simply having an active account in EBS, even if the user last logged in two years ago, makes that person a Named User Plus for licensing purposes.

Beyond direct human users, Oracle's indirect access rules extend the Named User Plus count to individuals who interact with EBS data through third-party applications, custom integrations, or middleware. If a sales rep uses Salesforce to view data that originates in Oracle EBS Financials, Oracle's position is that the sales rep is a Named User Plus of the EBS Financials product—even if they have never directly logged into EBS.

Common user categories Oracle counts during audits include:

• Employees with active EBS accounts—including back-office staff, approvers, and managers who only occasionally access the system
• Contractors and temporary workers with system access provisioned during engagements
• Users of integrated applications that read or write to EBS data via APIs or database links
• Employees who submit expense reports or approve timesheets via Oracle Self-Service applications connected to EBS HR or Financials
• Customers or partners accessing Oracle iSupplier Portal or iStore if those modules are deployed

Each of these categories carries significant compliance risk. Organizations routinely undercount because they focus on active daily users rather than the full authorized population Oracle requires.

Named User Plus Minimums: The Processor Floor

Oracle imposes minimum license counts for Named User Plus deployments based on the number of Processors running the software. The standard minimum is 25 Named User Plus licenses per Processor. This minimum applies regardless of actual user counts—if you have a 4-processor server running Oracle EBS, you must license at least 100 Named User Plus, even if only 40 people use the system.

The Processor count itself is determined by Oracle's Core Factor Table. Each processor type has a core factor (typically 0.25 to 1.0), and the formula is: Number of Cores x Core Factor = Processor licenses. For Intel x86 processors (the most common EBS deployment architecture), the core factor is typically 0.5, meaning a 16-core Intel server requires 8 Processor licenses and thus a minimum of 200 Named User Plus licenses.

This minimum floor creates a structural compliance trap for organizations that deployed EBS on large shared servers. A company that migrated EBS to a 32-core virtual machine thinking it would reduce costs may actually face a Named User Plus minimum of 400 users—far exceeding its actual user base of 150 employees. The minimum is enforceable regardless of virtualization, partitioning, or actual utilization.

Server Configuration	Total Cores	Core Factor (Intel)	Processor Licenses	NUP Minimum
2-socket, 8 cores each	16	0.5	8	200
2-socket, 16 cores each	32	0.5	16	400
4-socket, 12 cores each	48	0.5	24	600
Single-socket, 8 cores	8	0.5	4	100

Authorized Users vs. Active Users: Oracle's Key Distinction

One of the most consequential aspects of Oracle EBS Named User Plus licensing is Oracle's insistence on counting authorized users, not active or concurrent ones. Oracle's definition states that a Named User Plus is "an individual authorized to use the programs, regardless of whether the individual is actively using the programs at any given time."

This means user account cleanup and provisioning hygiene directly affect your license compliance position. Organizations that maintain large numbers of dormant accounts, terminated employees not yet de-provisioned, or contractor accounts from completed projects face inflated Named User Plus counts that can be significantly larger than the active user base.

Oracle's License Management Services (LMS) team specifically scripts for this during audits. The USMM (Usage and Software Management Module) tool Oracle deploys collects data on all accounts in the EBS system directory, not just active sessions. De-provisioning inactive users before an audit, however, must be done carefully—Oracle has challenged retroactive cleanup as a compliance tactic rather than a business practice.

For a comprehensive breakdown of EBS licensing rules across all metrics, see our Oracle EBS Licensing Guide.

Indirect Access and Third-Party Integration Risk

Indirect access is the most dangerous dimension of Named User Plus compliance for EBS deployments. Oracle's position—consistently upheld in its license agreements—is that users of non-Oracle applications who access EBS data through any technical means are Named User Plus licensees of the relevant EBS product.

Common indirect access scenarios that create Named User Plus exposure include:

• CRM integration: Sales teams using Salesforce, Microsoft Dynamics, or SAP CX that syncs with Oracle EBS Order Management or AR modules
• BI and analytics tools: Business intelligence platforms like Tableau, Power BI, or MicroStrategy connecting directly to EBS database schemas
• Custom portals: Internal employee self-service applications built on EBS data without Oracle front-end licenses
• Payroll and HR integrations: Third-party payroll processors accessing EBS HRMS data via API or database link
• EDI and B2B connections: Supplier portals, EDI gateways, or partner integrations reading EBS inventory or purchasing data

Oracle audit teams identify indirect access by examining database connection logs, network topology diagrams, and integration documentation during the audit process. The resulting Named User Plus claims can be extraordinarily large—in one case, an EBS customer faced a claim for 40,000 additional Named User Plus licenses because an employee portal served the entire workforce with EBS Financials data in the background.

Our Oracle compliance review service specifically maps indirect access vectors before Oracle's auditors do, allowing you to structure your license position defensibly.

Named User Plus vs. Full Use Application User License

Oracle EBS can be licensed under Named User Plus or, for certain applications, under the Application User metric. The Application User metric is specific to EBS application modules and is defined differently—it counts users licensed to use a specific application module rather than the underlying technology stack. For organizations with large EBS user populations, Application User licensing is often significantly cheaper than Named User Plus.

The distinction matters because Named User Plus licenses the Oracle technology platform (Database, Application Server) as well as the EBS application layer. Application User licensing, by contrast, covers only the EBS application usage and does not include technology stack rights. Organizations running Oracle Database on separate Processor licenses may find Application User licensing for EBS modules more cost-effective, but must verify the right to mix metrics with their specific Oracle contract.

Audit Risk: What LMS Looks for in EBS NUP Counts

Oracle's LMS audit process for EBS Named User Plus follows a well-defined script. Auditors typically request a user count export from EBS security tables, cross-referenced against HR records to identify all current employees, contractors, and external users. They then map each user account to the EBS modules they are provisioned to access.

Key LMS audit triggers for Named User Plus include:

• Discrepancy between licensed user count and HR headcount
• Evidence of third-party application integrations in network documentation
• Database connection logs showing non-Oracle application access to EBS schemas
• Self-service modules deployed to broad employee populations without corresponding NUP licenses
• Recent mergers or acquisitions that added EBS users without license amendment

The consequence of an EBS NUP audit finding is not just back-license fees—Oracle typically pursues the gap from the date of non-compliance, plus support fees (typically 22% of license value per year), plus interest. A gap of 500 Named User Plus licenses on a module priced at $800 per user can quickly become a $400,000+ claim inclusive of multi-year support fees.

Strategies to Manage and Reduce Named User Plus Exposure

Organizations can take several proactive steps to manage EBS Named User Plus exposure without disrupting operations. The starting point is always a thorough internal inventory: map every EBS account, every provisioned module access, every integration point, and every automated process that touches EBS data.

Effective reduction strategies include regular user de-provisioning programs aligned with HR offboarding processes, architecture reviews that consolidate integrations and eliminate redundant database connections, and contractual negotiations to convert some NUP obligations to Application User or Processor metrics where the economics favor the buyer. See our Oracle licensing white papers for detailed methodology on NUP reduction programs.

If your organization is already facing an Oracle audit or has received an LMS notification, the time to act is immediately—before you provide Oracle with data that locks in their claim. Our Oracle audit defense service has successfully challenged EBS Named User Plus claims and reduced settlement figures by an average of 60% from Oracle's initial position.

For organizations approaching EBS contract renewals, NUP counts are also a negotiating lever. Accurate counts, properly documented, allow you to rightsize licenses rather than accepting Oracle's inflated renewal quantities. Our Oracle contract negotiation team has deep experience structuring EBS renewal agreements that protect against future NUP exposure. Read more in our Oracle Audit Defense Guide.

Oracle Licensing Experts is an independent advisory firm. Not affiliated with Oracle Corporation. Oracle, Java, and Oracle E-Business Suite are registered trademarks of Oracle Corporation.