Oracle ERP Licensing Calculator: Modules

Oracle ERP sells under three product lines. E Business Suite (EBS) on perpetual processor or Application User metrics. Fusion Cloud ERP on a per user per month subscription. JD Edwards EnterpriseOne on perpetual user types or processor.

The calculator below maps the metric, the user definition, the typical list price, and the multi year cost profile for each line. Read it alongside the Oracle knowledge hub and the Fusion cloud applications guide.

Most ERP cost surprises come from one of three places. The wrong user metric. An unscoped module bundle. A renewal uplift on a fully deployed estate. The calculator addresses all three.

Key Takeaways

What every Oracle ERP buyer needs to know before the renewal

Three product lines. EBS, Fusion Cloud ERP, JD Edwards. Each carries a separate metric and a separate price book.
EBS Application User. 5,800 USD per named user for the Financials, Procurement, or Project Costing module. 25 user minimum.
Fusion Cloud ERP. Subscription. 175 USD per user per month for the Financials Cloud, with Project, Procurement, Risk Management priced separately.
JD Edwards user types. Enterprise User at 5,000 USD, Application User at 1,250 USD, Self Service User at 230 USD. Choose the lowest valid metric.
Database underneath. EBS and JDE need Oracle Database licensed separately. Fusion includes the database in the subscription.
Support arithmetic. 22 percent of net license fee per year. Uncapped uplift can reach 8 to 12 percent annually.
Right size before the renewal. Count active named users by module. Drop the inactive ones before the renewal date locks them in.

Three Oracle ERP product lines, side by side

The first ERP licensing decision is which Oracle product line is in scope. EBS, Fusion, and JD Edwards each carry different metrics and different price books.

EBS, Fusion Cloud ERP, JD Edwards at a glance

Product line	Commercial model	Primary metric	List price benchmark
E Business Suite	Perpetual license	Application User	5,800 USD per Financials user
Fusion Cloud ERP	SaaS subscription	Hosted user per month	175 USD per Financials user per month
JD Edwards EnterpriseOne	Perpetual license	Tiered user types	5,000 USD Enterprise User

Where each product line still fits in 2026

EBS. Stable mid market or large enterprise running on premises. No cloud migration urgency. Database EE often already deployed.
Fusion Cloud ERP. Enterprise customers committed to a multi tenant SaaS path. Often the target state after an EBS extended support window.
JD Edwards. Manufacturing, distribution, and asset intensive industries. Continued Oracle investment through 2034 Premier Support commitment.

E Business Suite licensing math

EBS licenses on perpetual Application User counts by module, with optional processor licensing for very high concurrent user environments. The math sits on three numbers.

EBS metric definitions

Application User. A named individual with access to the module, whether they log in monthly or not. Service accounts and batch users count where they access the module logic.
Processor. The server processor count multiplied by the core factor, for shared services or very high concurrency.
Site License. Unlimited use within a defined entity boundary, available on negotiation.

EBS module price benchmarks

Module	Metric	List per user	25 user minimum
Financials	Application User	5,800 USD	145,000 USD
Procurement	Application User	5,800 USD	145,000 USD
Project Costing	Application User	4,595 USD	114,875 USD
Human Resources	Employee record	185 USD per record	1,000 employee minimum
Supply Chain Planning	Application User	4,595 USD	114,875 USD

EBS user counting pitfalls

Shadow service accounts. Integration users running posting jobs count as Application Users in audit.
Mobile users. EBS mobile apps require the underlying module license. The mobile app is not a separate metric.
Read only users. Read access to Financials data still requires a Financials Application User license.
Database underneath. The EBS technology stack uses Database EE. Database is licensed separately on processors.

Fusion Cloud ERP subscription math

Fusion Cloud ERP runs on a hosted user per month subscription. The price is published in the Oracle Cloud Applications price book, with module specific rates.

Fusion metric definitions

Hosted User. A named individual or service account with access to the module, counted monthly.
Hosted Employee. Used in HCM and certain Project modules, counted by employee record.
Hosted Revenue. Used in some Risk Management cloud modules, scaled by company revenue band.

Fusion Cloud ERP price benchmarks

Module	Metric	List per user per month	Annual at 1,000 users
Financials Cloud	Hosted User	175 USD	2.10M USD
Procurement Cloud	Hosted User	120 USD	1.44M USD
Project Management Cloud	Hosted User	65 USD	780K USD
Risk Management Cloud	Hosted User	90 USD	1.08M USD
Supply Chain Planning Cloud	Hosted User	200 USD	2.40M USD

Fusion bundling and discount mechanics

Module bundle. Financials plus Procurement plus Project commonly bundled at 12 to 22 percent off list.
Enterprise commit. 3 to 5 year commitments unlock 28 to 42 percent discount tiers on large estates.
Migration credit. EBS to Fusion migration paths sometimes carry credit for residual EBS support paid.
Universal Credits overlap. OCI Universal Credits separate from Fusion subscription. Do not let Oracle bundle without clear unit price separation.

JD Edwards EnterpriseOne licensing math

JD Edwards uses a tiered user type model. Choosing the right user type per role drives the math. Misallocation runs cost up by 3x to 4x.

JD Edwards user type tiers

Enterprise User. Full functional access across all licensed modules. 5,000 USD per user list.
Application User. Access to specific modules only (Financials, HR, Manufacturing). 1,250 USD per user list.
Self Service User. Read only with limited transaction entry (expense, time, leave). 230 USD per user list.
Mobile Application User. Mobile only access to specific transactions. 60 USD per user list.
Processor. Optional processor metric for high concurrency. 7,500 USD per processor on the Foundation product.

JD Edwards user classification mistakes

Over assigning Enterprise User. Roles needing only Financials get the full Enterprise grant. 4x the necessary cost.
Self Service to Application drift. A self service expense submitter who gains AP voucher entry rights crosses into Application User territory.
Module bundling. A user with three licensed modules pays per module unless on the Enterprise User tier.
Restricted Use Database. JDE Foundation includes restricted use Database EE for the JDE application only, not for ad hoc query against JDE schema.

Worked example: 2,400 user mid market customer

A regional manufacturing group runs JD Edwards EnterpriseOne across 2,400 named users. The user roles map to Enterprise, Application, and Self Service tiers, with restricted use Database EE underneath.

Current position on wrong metric

The customer originally licensed 2,400 Enterprise Users at 5,000 USD list, with a 35 percent discount giving 7.8M USD upfront and 1.72M USD per year support.

Right sized position on correct user types

User type	Count	List per user	Net at 35 percent discount	Line total
Enterprise User	320	5,000 USD	3,250 USD	1.04M USD
Application User (Financials)	680	1,250 USD	813 USD	553K USD
Self Service User	1,400	230 USD	150 USD	210K USD
Total license	2,400	--	--	1.80M USD
Annual support at 22 percent	--	--	--	396K USD

Five year cost compare

Scenario	Year 1 license	Annual support	5 year TCO
Wrong metric, all Enterprise User	7.80M USD	1.72M USD	16.40M USD
Right metric, tiered user types	1.80M USD	396K USD	3.78M USD
Saving	6.00M USD	1.32M USD	12.62M USD

Seven Oracle ERP commercial levers

The seven levers procurement carries

Right metric assignment. Tier user types correctly before the order. The cost gap between Self Service and Enterprise User is 22x.
Module scope tightening. Drop modules no role actually uses before the renewal locks them in.
Migration credit. Extract EBS support credit on the Fusion migration order.
Cloud commit trade. Multi year Fusion commitment unlocks 28 to 42 percent discount tiers.
Support cap. Negotiate annual support uplift cap at 4 to 6 percent on the EBS or JDE estate.
Database separation. Hold Database license separate from ERP. Do not bundle.
Inactive user purge. Run the user audit 90 days before the renewal. Drop inactive users from the renewal count.

What to do next

The checklist takes an Oracle ERP estate from current state to a right sized renewal.

Inventory active users by module. Pull from EBS, Fusion, or JDE workspace audit reports.
Reclassify roles to the right user type. Self Service, Application, Enterprise, or hosted user. Document the role definition.
Map service accounts. Identify integration users, batch service accounts, and reporting extracts that consume license.
Separate the database line. EBS and JDE Database EE on a separate metric and separate price book.
Build the renewal model. Three scenarios: current state, right sized, target state. Compare annual and 5 year TCO.
Open the negotiation. Lead with the right sized count. Trade multi year commit for unit price reduction and uplift cap.
Document the renegotiated terms. User type definitions, module scope, support cap, database boundary, in the renewal order.

Frequently asked questions

How many Application Users do we actually have on EBS?

Count every named individual with access to the licensed module, plus every service account that runs posting jobs, integration extracts, or batch processes inside that module. Read only users still consume an Application User license.

The EBS user audit query inside System Administrator gives the base count. The audit will typically add 8 to 18 percent for service accounts, integration users, and inactive but provisioned users still on the count.

Is Fusion Cloud ERP always cheaper than EBS?

Not always. Fusion subscription costs scale linearly with the user count, with no perpetual end state. A 5 year Fusion TCO on 1,000 Financials users runs around 10.5M USD at list, before any negotiated discount. An EBS perpetual deployment for the same population runs around 5.8M USD upfront plus 1.28M USD per year support.

Break even sits at year 4 to 5 depending on the discount achieved. The decision turns on operational model, not just total cost.

Does the database license come with EBS or do we license it separately?

EBS includes restricted use rights to Database EE for the EBS application only. The restriction means the database supports EBS schemas and EBS reports. Any ad hoc query against the EBS schema from a separate tool, any data warehouse build using EBS data, or any third party reporting against EBS tables requires full Database EE license.

Most large EBS estates run full Database EE for this reason. Validate the scope before assuming restricted use covers the deployment.

What user type does a financial controller need on JD Edwards?

A controller running monthly close, journal entry, AP voucher entry, and Financials reporting needs an Application User license for the Financials module at 1,250 USD list, not an Enterprise User at 5,000 USD. The Enterprise User tier is only needed when the role spans Financials plus Manufacturing plus Distribution or three or more modules.

Misclassifying controllers as Enterprise Users is the single largest JDE overpayment pattern we see on the buyer side.

How do we move from EBS to Fusion without paying twice?

Three levers. First, negotiate migration credit from Oracle that offsets residual EBS support paid during the Fusion ramp period. Second, build a phased migration plan where EBS license drops are timed to Fusion go live. Third, lock the Fusion price for the full 5 year subscription rather than a 1 year list price that resets at renewal.

Oracle typically grants 12 to 30 percent migration credit depending on the EBS support spend and the Fusion subscription size.

How does Redress engage on Oracle ERP advisory?

Redress runs Oracle ERP advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program. The output is a user classification map, a module scope assessment, a database boundary review, a Fusion migration cost model, and a renegotiated commercial position.

The engagement is led by Oracle commercial professionals on the buyer side. We have run Oracle ERP advisory across pharma, banking, manufacturing, distribution, and public sector customers running ERP estates from 1M to 50M USD per year.

How Redress engages on Oracle ERP advisory

Redress runs Oracle ERP advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program.

Read the related Fusion cloud applications guide, the database pricing 2026, the database licensing guide, the ULA decision framework, the contract renewal strategy, the contract negotiation service, the Java licensing, the benchmarking page, the about us page, and the contact page.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Oracle ERP Licensing Calculator. The math before the renewal.