Oracle JD Edwards Licensing: User Types

Q: How does JD Edwards World differ from EnterpriseOne licensing?

JD Edwards World is the older IBM AS/400 based product. It licenses on a different price book with concurrent user metrics rather than named user metrics. World customers typically have grandfathered terms from pre Oracle acquisition. EnterpriseOne is the current product, licensed under the user type tiers described in this article. Oracle Premier Support for World extends through 2034.

JD Edwards EnterpriseOne licenses on five user type tiers plus a processor metric on the Foundation product. The user types are Enterprise User, Application User, Self Service User, Mobile Application User, and Tools User (the last for development environments).

Choosing the right tier per role drives the cost math. The gap between a Self Service User at 230 USD and an Enterprise User at 5,000 USD is 22x. Most JDE estates we audit on the buyer side carry 30 to 60 percent overpayment from misclassified user tiers.

Read this alongside the Oracle ERP licensing calculator and the Oracle knowledge hub for the full Oracle ERP context.

Key Takeaways

What every JD Edwards customer needs to know

Five user types. Enterprise, Application, Self Service, Mobile Application, Tools. Each carries a different price.
Enterprise User at 5,000 USD. Full functional access across all modules. Premium price for full grant.
Application User at 1,250 USD. Module specific access. Right tier for most functional roles.
Self Service User at 230 USD. Limited transaction entry. Right tier for ESS, MSS, and procurement self service roles.
Mobile Application at 60 USD. Mobile only access to specific transactions.
Processor metric. Foundation at 7,500 USD per processor for very high concurrency or anonymous user environments.
Database restricted use. Foundation includes restricted use Database EE for JDE application only. Full Database EE required for ad hoc query.

Five JDE user type tiers, side by side

The user type assignment is the single most important JDE licensing decision. The tier defines the rights, the price, and the audit exposure.

JDE user type price book

User type	List per user	Rights	Typical role
Enterprise User	5,000 USD	Full access across all licensed modules	Power user spanning 3 plus modules
Application User	1,250 USD per module	Specific module access only	Financial controller, AP clerk, planner
Self Service User	230 USD	Limited transaction entry, read access	Expense submission, time entry, leave request
Mobile Application User	60 USD	Mobile only specific transactions	Field service, warehouse pick
Tools User	2,500 USD	Development environment access	JDE developer, technical analyst

JDE user tier counting rules

Named individual basis. Each user is named, no shared accounts.
Highest tier consumed. A user with access to both Self Service and Application User functions counts as Application User.
Across modules. A user accessing two licensed modules at the Application User tier requires two Application User licenses, one per module, unless on the Enterprise User tier.
Inactive provisioned users. If a user has rights provisioned in the application but has not logged in for 90 plus days, they still count in the audit. Drop unused accounts before the renewal.

Module mapping and license entitlement

JD Edwards EnterpriseOne ships as a suite of functional modules. The Application User license is module specific, while the Enterprise User license spans all licensed modules.

JDE EnterpriseOne functional modules

Financial Management. General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets, Cash Management.
Project Management. Project Costing, Project Billing, Contract Management.
Supply Chain Execution. Inventory Management, Procurement, Sales Order, Warehouse Management.
Supply Chain Planning. Forecasting, Requirements Planning, Production Planning, Capable to Promise.
Manufacturing. Discrete, Process, Shop Floor, Quality, Engineering Change.
Asset Lifecycle Management. Maintenance, Capital Asset Management, Equipment Cost Analysis.
Human Capital Management. Payroll, Human Resources, Self Service, Time and Labor.

Module bundle vs Enterprise User

Scenario	Best fit tier	Math
Role uses 1 module	Application User	1,250 USD
Role uses 2 modules	Application User x 2	2,500 USD
Role uses 3 modules	Application User x 3 or Enterprise User	3,750 USD vs 5,000 USD (break even at 4 modules)
Role uses 4 plus modules	Enterprise User	5,000 USD vs 5,000 USD plus
Self service only	Self Service User	230 USD

Database EE underneath JDE

JD Edwards EnterpriseOne requires a database. Oracle Database is the most common choice, but JDE also supports IBM DB2 and Microsoft SQL Server. The Oracle Database licensing depends on whether the customer holds Foundation, full Database EE, or restricted use rights.

JDE Foundation restricted use Database EE

Foundation grants restricted use. The JDE Foundation product includes restricted use Database EE for the JDE application only.
Restricted to JDE schema. Database queries through the JDE application, JDE One View Reporting, JDE Composed Pages, and JDE BIP Reports are in scope.
Out of scope. Ad hoc SQL query against the JDE schema from a third party tool, ETL extracts to a data warehouse, custom reports built outside JDE Composed Pages, and any BI tool query against JDE tables fall outside restricted use.
Compliance posture. Most large JDE estates run full Database EE for the reporting and analytics environment. Validate the scope before assuming restricted use covers the deployment.

Database EE options often needed with JDE

Partitioning Option. Used for very large JDE F4111 (Item Ledger) and F0911 (Account Ledger) tables. Licensed separately on Database EE processors.
Advanced Compression. Used in archive and history environments. Licensed separately.
Diagnostics Pack. Used by JDE DBA team for AWR reports. Licensed separately, often triggers compliance on shared environments.
Tuning Pack. Used by JDE DBA team for SQL tuning advisor. Licensed separately.

Common JDE licensing pitfalls

Most JDE compliance gaps fall into recurring patterns. The audit history makes the pattern repeatable. Knowing the pattern in advance is the defense.

The seven recurring JDE pitfalls

Tier inflation. Roles needing one or two modules licensed as Enterprise User.
Tier drift. Self Service users gain AP voucher entry rights, crossing into Application User territory.
Service account exposure. Integration users, batch users, and ETL extract accounts treated as system users, counted as Application Users in audit.
Inactive user retention. Provisioned users no longer with the company remain in the audit count.
Database scope drift. Restricted use Database EE assumed to cover BI reporting, data warehouse extracts, and ad hoc query.
Diagnostics Pack inadvertent use. DBA team runs AWR reports on a database without separately licensing Diagnostics Pack.
Multi tenant SaaS or hosted use. Deploying JDE in a hosted or shared environment without the required commercial use rights.

Worked example: 1,400 user manufacturing customer

A North American manufacturing group runs JD Edwards EnterpriseOne for finance, distribution, and HR across 1,400 named users. The starting position licenses all 1,400 as Enterprise User. The classification review right sizes the estate.

Current state on wrong tier

Line	Count	List per user	Total
Enterprise User	1,400	5,000 USD	7.00M USD
Annual support at 22 percent	--	--	1.54M USD

Right sized on correct tiers

User type	Count	List per user	Total
Enterprise User	240	5,000 USD	1.20M USD
Application User (Financials)	360	1,250 USD	450K USD
Application User (Manufacturing)	260	1,250 USD	325K USD
Self Service User	540	230 USD	124K USD
License total	1,400	--	2.10M USD
Annual support at 22 percent	--	--	462K USD

Five year cost compare

Scenario	Year 1 license	5 year support	5 year TCO
Current state, all Enterprise User	7.00M USD	7.70M USD	14.70M USD
Right sized, tiered classification	2.10M USD	2.31M USD	4.41M USD
5 year saving	4.90M USD	5.39M USD	10.29M USD

Seven JDE licensing levers procurement carries

The seven JDE levers

User tier classification. Right tier for each role. Self Service, Application, Enterprise.
Module scope tightening. Drop modules that no role uses.
Service account treatment. Document integration users explicitly to avoid audit reclassification.
Inactive user purge. Drop provisioned but inactive users 90 days before the renewal.
Database boundary documentation. Separate restricted use Database EE from full Database EE.
Diagnostics Pack discipline. Control which DBAs can run AWR.
Renewal commercial cap. Negotiate annual support uplift cap at 4 to 6 percent and proportional pricing on partial drop.

What to do next

The checklist takes a JDE estate from current state to a right sized renewal.

Inventory active users. Pull the JDE Address Book and login audit, filter to active users.
Map roles to modules. Document which functional modules each role actually uses in production.
Assign the right tier. Self Service for ESS or MSS, Application User for one or two modules, Enterprise User for four plus.
Document service accounts. Integration users, batch users, ETL extract accounts. Identify count and purpose.
Validate Database boundary. Distinguish restricted use from full Database EE deployment.
Build the right sized model. Current state, right sized, target state. Compare 5 year TCO.
Open the renewal negotiation. Lead with the right sized count. Lock support cap and partial drop terms.

Frequently asked questions

How is an Enterprise User different from an Application User?

An Enterprise User has full access to every licensed module in the JDE installation, at 5,000 USD per user list. An Application User has access to a specific module, at 1,250 USD per user list per module.

The break even sits at four modules. A user accessing three modules is cheaper as 3x Application User (3,750 USD) than as Enterprise User (5,000 USD). Tier inflation is the single largest JDE overpayment pattern we see.

Do service accounts count as licensed users?

Yes. Integration users, batch posting users, ETL extract accounts, and reporting service accounts that access JDE application logic count as licensed users in audit. They typically classify as Application Users on the module they access. Some customers attempt to argue these as system accounts, but the JDE licensing terms count them.

The buyer side discipline is to document each service account, identify the module accessed, and provision the right tier. Service accounts that span multiple modules may push to the Enterprise User tier.

What is restricted use Database EE under JDE Foundation?

JDE Foundation grants restricted use rights to Database EE for the JDE application only. Database queries through JDE Composed Pages, JDE One View Reporting, JDE BIP Reports, and the JDE application itself are in scope.

Out of scope are ad hoc SQL queries from a third party tool, ETL extracts to a data warehouse, and BI tool queries against JDE tables. Most large JDE estates run full Database EE on the reporting environment to cover those use cases.

Can we drop modules from JDE on a partial cancellation?

Module drops are possible under the Oracle Master Agreement repricing clause, but the default OMA position is to reprice the remaining lines at original list when any line is dropped. This default makes a partial drop punitive. The buyer side negotiation is to convert the repricing clause to proportional pricing on partial drop.

Negotiate proportional pricing during a major renewal event when leverage is highest. With proportional pricing in place, JDE module drops save money cleanly.

How does JD Edwards World differ from EnterpriseOne licensing?

JD Edwards World is the older IBM AS/400 (IBM i) based product. It licenses on a different price book with concurrent user metrics rather than named user metrics. World customers typically have grandfathered terms from pre Oracle acquisition. EnterpriseOne is the current product, licensed under the user type tiers described in this article.

Most large enterprise World customers run hybrid estates with EnterpriseOne for new functionality. Oracle Premier Support for World extends through 2034.

How does Redress engage on JD Edwards advisory?

Redress runs JD Edwards advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program. The output is a user tier classification map, a module scope assessment, a database boundary review, a service account map, and a right sized renewal model.

The engagement is led by Oracle commercial professionals on the buyer side. We have run JDE advisory across manufacturing, distribution, construction, asset intensive, and process industry customers running JDE estates from 500K to 25M USD per year.

How Redress engages on JD Edwards advisory

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

Read the related Oracle ERP licensing calculator, the 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 JD Edwards Licensing Explained. User types, metrics, common pitfalls.