Oracle EBS User Licensing Models Explained

The Two EBS Licensing Metrics: NUP vs. Processor

Oracle E-Business Suite can be licensed under two metrics: Named User Plus (NUP) or Processor. Understanding when each applies and which is more favorable for your specific deployment requires careful analysis of user counts, server infrastructure, and module configuration. This guide focuses on the NUP metric and the user-count rules that govern it, since NUP complexity drives the majority of EBS compliance findings. For the full overview, see our Oracle EBS Licensing Guide.

What Is a Named User Plus in EBS?

Oracle's Named User Plus definition in the EBS context licenses every individual who is authorized to access the EBS application — not merely those who actively use it. The licensing obligation arises from the authorization, not the usage frequency or intensity. This is a critical distinction that Oracle enforces consistently in audits.

A Named User Plus is defined as an individual authorized to use the programs that are installed on a single server or on multiple servers, regardless of whether the individual is actively using the programs at any given time. For EBS, this means anyone with an active account in the FND_USER table.

Who Counts as a Named User Plus in EBS?

User Type	Requires NUP License?	Notes
Full EBS application users	Yes	Core operational staff with EBS responsibilities
Self-service portal users	Yes	iExpenses, Self Service HR, iProcurement users
Timesheet/approval-only users	Yes	Minimal access does not exempt from licensing
Dormant / inactive accounts	Yes (Oracle position)	Disable and remove to eliminate exposure
System/service accounts	Typically No	Non-human accounts not used by individuals
Indirect access users (3rd party)	Contested	Contract language dependent — seek expert review

NUP Minimums Per Processor: The Hidden Multiplier

One of the most misunderstood aspects of Named User Plus licensing in EBS is the minimum user requirement per Processor. Oracle sets a floor on the number of NUP licenses required based on the number of Processors (cores, adjusted for the Core Factor Table) in your EBS server environment.

For most EBS applications, Oracle requires a minimum of 10 Named User Plus licenses per Processor. This means:

• A server with 8 physical cores (Intel x86 at 0.5 Core Factor) = 4 Processors required = minimum 40 NUP licenses
• If your actual user count is 25, you still owe 40 NUP licenses — the minimum overrides your actual count
• As you add servers to your EBS environment (for HA, DR, or scale-out), the NUP minimum scales with the additional Processor count

This minimum is separate from the Processor metric itself. If you license EBS under NUP, you pay for NUP licenses but must still count Processors to establish the floor. Organizations that undercount Processors to lower their NUP minimum face a compounded audit finding.

Self-Service Users: The Largest Source of EBS License Exposure

The single most prevalent EBS licensing compliance gap is the undercount of self-service users. When an organization deploys EBS self-service capabilities — employee self-service HR, iExpenses, iProcurement, or Manager Self Service — every employee who accesses those portals requires a Named User Plus license.

The scale of this exposure can be dramatic. An EBS deployment licensed for 500 core business users that rolls out iExpenses to the entire 8,000-person workforce has created a 7,500-NUP licensing gap overnight — even though each self-service user only logs in once a month to submit an expense report.

Common Self-Service EBS Applications and Their License Implications

• Oracle iExpenses: Expense report creation and submission. Every employee who submits expenses requires a NUP license — including those who access via a mobile interface.
• Oracle Self Service Human Resources (SSHR): Employee-facing HR portal for personal data updates, benefits elections, and direct reports management. Each employee with SSHR access requires a NUP license.
• Oracle iProcurement: Requisition creation portal for non-procurement staff. All requestors require NUP licenses even if they never process an order themselves.
• Oracle Manager Self Service: Line manager access to approve timesheets, performance reviews, and salary actions. Each manager requires a NUP license for the EBS modules underlying those approval workflows.
• Oracle Time and Labor: Time entry and approval. Employees who record time against Oracle Time and Labor, including those using punch-in/out terminals interfacing with EBS, typically require NUP licenses.

Indirect Access: When Third-Party Users Require EBS Licenses

Indirect access is one of the most contested areas in Oracle EBS licensing. When a third-party application — a business intelligence tool, an HR system, a custom application — reads data from or writes data to EBS, Oracle has historically argued that the users of the third-party application require EBS Named User Plus licenses.

The logic Oracle applies: if the third-party application provides the user with the functional benefit of EBS data, the user is effectively "using" EBS, even if they never see an EBS screen. This argument has been applied to everything from reporting tools that query EBS financial data to integration platforms that synchronize EBS HR data with a third-party payroll system.

The indirect access doctrine is not absolute. Its application depends critically on:

• The specific language in your Oracle contract regarding indirect access
• Whether the access goes through Oracle's published APIs or directly to database tables
• Whether the functionality being accessed is "EBS functionality" or merely EBS data

Every organization with third-party integrations touching EBS should have their contracts reviewed by independent experts before an audit. Our Oracle compliance review service specifically addresses indirect access risk quantification.

Dormant Accounts: Low-Value, High-Risk

Oracle's audit scripts extract all accounts from FND_USER, including accounts for employees who left the organization months or years ago. Oracle's position is that any account with EBS access constitutes a license requirement regardless of the last logon date. Dormant accounts are an indefensible finding — they provide zero business value while creating a license liability.

Best practice is to implement a formal joiner/mover/leaver process that disables EBS accounts at the point of employee departure and removes application responsibilities from users who change roles. A quarterly account hygiene review is the minimum acceptable standard for any organization with EBS audit risk. For detailed guidance on audits and remediation, see our Oracle EBS Licensing Audit guide.

NUP vs. Processor: Which Is More Favorable?

The choice between NUP and Processor licensing for EBS is not purely mathematical — it has risk and compliance dimensions that must be considered alongside the cost comparison.

Factor	Named User Plus	Processor
Best for	Fewer than ~100 users per Processor	Large or hard-to-count user populations
Self-service user risk	High — every user counts	Lower — user count doesn't drive license
VMware risk	Lower — NUP minimum still applies	Very High — all physical cores must be licensed
Indirect access risk	High — 3rd party users may count	Lower — user count doesn't directly drive license
Minimum floor	10 NUP per Processor	Core Factor × physical cores

For organizations running EBS on VMware with a large user population, Processor licensing can appear attractive — but the VMware core counting rules create enormous exposure. Most organizations are better served by understanding both metrics and choosing based on their specific infrastructure and user profile. For detailed analysis and white papers on this topic, see Oracle Licensing White Papers. Our Oracle license optimization service evaluates both metrics against your actual deployment. Not affiliated with Oracle Corporation.