Contents
Key takeawaysHow JD Edwards is pricedThe employee metricLeavers and application usersConnected devicesThe database underneathA worked billSupport to 2037Checking your positionWhat we have seenAnswering the account teamContract terms and timelineWhat to do nextFAQJD Edwards is priced per component on five metrics, each with a minimum. The metric on your ordering document decides whether headcount growth costs money automatically, and there is no professional, casual or read only tier under Oracle paper.
- Five component metrics, no user ladder. Application users, employees, connected devices, expense reports and UPK developers each carry their own floor, from 5 users per component to all employees.
- The employee metric follows the workforce. It counts everyone the programs track, contractors and agents included, so an acquisition raises the requirement with no new deployment.
- Authorized means licensed. A dormant account counts as an application user until it is disabled, which makes leaver seats the fastest saving.
- Devices are a licensable line. Scanners, weighbridges and shop floor terminals posting to JD Edwards fall under the connected device metric, with a 50 device minimum.
- Cleanup comes before the renewal. Correcting users and modules cut maintenance bases by 15 to 30 percent in our reviews, before any concession was requested.
- There is no forced migration. Premier Support for EnterpriseOne 9.2 runs through at least 2037, so Fusion and third party support are choices on your timetable.
How is JD Edwards priced?
JD Edwards EnterpriseOne is priced per component on five metrics: application users, employees, connected devices, expense reports and UPK developers. Each metric carries its own minimum. The metric printed on your ordering document for each component decides whether headcount growth raises the bill without anyone installing anything.
The list prices below are approximate figures from Oracle's JD Edwards component price list. Your own order is the reference that counts, because metrics, minimums and availability differ by price list vintage.
| Metric | What it counts | Minimum | Approximate list price |
|---|---|---|---|
| Application user | Each individual authorized to use the licensed programs | 5 per component | About $4,595 per user for Financials or Distribution Management |
| Employee | Everyone the programs track, contractors, consultants and agents included | All employees | About $185 for HR, $225 for Payroll, $50 for Health and Safety |
| Connected device | Devices exchanging data with the programs with no human interaction | 50 devices | Per device, varies by module |
| Expense report | Reports processed in any rolling twelve month period | 1,000 reports | About $6 per report |
| UPK developer | People authorized to build simulations and documentation | 1 developer | About $17,500 per developer |
Annual support runs at roughly 22 percent of the net license fee. Oracle bills it on every component on the contract, whether that component still runs a business process or not.
Why is there no professional, casual or read only user?
Buyers often expect a ladder of user types priced by how much each person does in the system. JD Edwards under Oracle paper has no such ladder. Those tiers belong to pre Oracle JD Edwards contracts and to other vendors, and asking Oracle for a view only price wastes a round of the negotiation.
If your oldest orders predate Oracle, read our note on JD Edwards concurrent licensing before you agree to convert anything to a modern metric. The counting rules for each metric are set out in our JD Edwards user types guide.
Where do the minimums bite?
The floors matter most for small deployments. A component used by three people still bills five application users. A distribution site with 30 scanners posting to JD Edwards still buys 50 connected devices, and a business that files 400 expense reports a year still pays for 1,000.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
What does the JD Edwards employee metric count?
Everyone the licensed programs track counts, whether or not they ever log in. A payroll or HR component tracks the whole workforce, so the whole workforce counts. Oracle's definition also reaches agents, contractors and consultants, and the minimum is all of your employees.
That definition has two consequences. A headcount taken from badge holders or the corporate directory undercounts by design, because it misses contractors and outsourced staff the programs still track. And an acquisition raises the licensed requirement on the day the new people join, with no new deployment.
| Line | Calculation | At list |
|---|---|---|
| Employees joining after the deal | 600 people | |
| HR | 600 x $185 | $111,000 |
| Payroll | 600 x $225 | $135,000 |
| Health and Safety | 600 x $50 | $30,000 |
| License shortfall | 600 x $460 | $276,000 |
| Added annual support | 22 percent of $276,000 | $60,720 |
Why does the employee count drift in both directions?
Employee quantities tend to stay at the headcount on the original order. When the workforce has grown past that number, the gap is audit exposure that builds every year. When it has shrunk through divestments or outsourcing, you are paying support on people who no longer exist, so reconcile in both directions before any renewal.
Oracle JD Edwards Licensing Brief
Metric definitions, minimums, database grant boundaries and a renewal sequence for JD Edwards customers, in one download.
Get the white paper →Why do leavers still count as JD Edwards application users?
They count because an application user is anyone authorized to use the programs, not anyone who used them recently. An account that has sat dormant for two years is still a licensed user at audit until someone disables it and can show the date. Restructures that remove people from the business rarely remove their JD Edwards authorization.
Oracle counts who is allowed in, so the fastest saving in most JD Edwards reviews is the list of people who left.
How do roles and shared accounts change the count?
- Entitlements are per component. A Financials user given a Manufacturing role becomes a user of both components, and both counts rise.
- Surplus does not transfer. Spare Financials seats do nothing for a shortfall in Distribution Management, and Oracle bills the gap.
- Users are people. Two accounts held by one person are one user, and two people sharing one login are two.
- Reporting access is use. Someone running inquiries against a licensed component is a user of it, even if they never enter a transaction.
Do scanners and shop floor terminals need JD Edwards licenses?
Often they do. The connected device metric covers devices that send data to or receive data from the programs with no human interaction. Warehouse scanners feeding transactions, weighbridges and shop floor terminals all fit that description, and the metric has a minimum of 50 devices.
This is the line least likely to appear on your own license inventory. IT asset teams track servers and people, while the devices are bought by operations and connected by an integration team. An auditor starts from the data flowing into JD Edwards and works back to the source, so the device census belongs in every review.
Is the database included in JD Edwards pricing?
No. The database underneath JD Edwards is licensed separately, often on an application specific full use (ASFU) grant that permits use only in support of JD Edwards. A reporting schema or a second workload on the same instance takes the database outside that grant and into full technology licensing.
Customers who bought Oracle Technology Foundation for JD Edwards EnterpriseOne hold restricted use licenses instead. Oracle's licensing documentation sets these limits:
- Database. Oracle Database Standard Edition 2 may be used only with the licensed JD Edwards programs.
- Middleware. WebLogic Server Standard Edition carries the same restriction, so check it against middleware you already license elsewhere before you buy Technology Foundation.
- Reporting. BI Publisher may report on the JD Edwards schema only, and new reports for other applications fall outside the license.
What does a JD Edwards license and support bill look like?
Take a hypothetical manufacturer with 1,500 employees on HR, Payroll and Health and Safety, 400 application users across two core components, and modest expense and UPK use. The figures are at list. Your support is 22 percent of the net fee you paid, so scale the result by your discount.
| Component | Metric and quantity | Unit price | License at list |
|---|---|---|---|
| Financials | 240 application users | $4,595 | $1,102,800 |
| Distribution Management | 160 application users | $4,595 | $735,200 |
| HR | 1,500 employees | $185 | $277,500 |
| Payroll | 1,500 employees | $225 | $337,500 |
| Health and Safety | 1,500 employees | $50 | $75,000 |
| Expense reports | 2,000 reports a year | $6 | $12,000 |
| UPK developer | 1 developer | $17,500 | $17,500 |
| Total | $2,557,500 | ||
| Annual support | 22 percent of list | $562,650 |
Application users make up $1,838,000 of the $2,557,500, which is why the user reconciliation comes first. Modules also carry support at sites that stopped running the process years ago, and that support buys nothing.
What is cutting leaver seats worth, and what can erase the saving?
Suppose 100 of the 400 users in the example belong to people who have left. At list that is $459,500 of licenses and $101,090 of annual support. The license fee is already spent, so the saving is the support, and you only get it by formally terminating those licenses.
Oracle's support policies then reprice the remaining licenses on that order at current list support less the standard discount, capped at what you paid before for the whole order. On a deeply discounted order that can absorb the entire saving. Model it first with our notes on Oracle support costs and on dropping and reinstating support.
How long will Oracle support JD Edwards EnterpriseOne?
Oracle has committed Premier Support for JD Edwards EnterpriseOne 9.2 through at least 2037, and its support FAQ says December 2037. New functionality arrives as updates to the 9.2 code line, so you get new features without an upgrade project.
For EnterpriseOne, the commitment removes the forced migration deadline. A move to Fusion should be decided on business merits, and the third party support comparison should be priced against more than a decade of committed Oracle patches.
Why we disagree with starting a Fusion project to beat the support deadline
A common piece of advice is to start the Fusion business case now, because on premises JD Edwards is living on borrowed time. For EnterpriseOne 9.2 we think that is backwards. The deadline that advice assumes is at least December 2037, and a proposal built on urgency loses its main argument once you say so.
Fix the counts first, renew on the corrected base, and decide the platform on your own timetable. The sequence for users, modules, employees and devices is worked through in our JD Edwards cost optimization guide. Where cloud hosting does fit, our cloud migration licensing analysis covers the license questions.
What about JD Edwards World?
World is on a different path. Premier Support for World A9.4 ended in April 2022, and Extended Support moved to Sustaining Support in April 2025. World customers face the deadline that EnterpriseOne customers do not, so their Fusion or third party support decision has a date attached.
How do you check your own JD Edwards license position?
Build the count from the system tables and the HR record, then compare it with the quantities on every ordering document. The tables named below exist in every EnterpriseOne installation, and together with HR and operations records they are the data an auditor will ask for.
- User profiles. Export F0092 as the master list of users, then join it to F98OWSEC to see which profiles are enabled or disabled.
- Component access. Join F95921 to see which roles each user holds, and map those roles to the licensed components.
- Leavers. Compare enabled users against the HR leaver list and against the address book record in F0101 for contractors.
- Employee metric. Count everyone the HR, Payroll and Health and Safety components track, including contractors and agents, and compare the total with the licensed quantity.
- Connected devices. Ask operations and the integration team for every scanner, weighbridge and terminal that posts to JD Edwards.
- Database. List every schema, reporting tool and feed on the JD Edwards database instance and check each against the grant.
Our guide to internal Oracle license audits covers how to run the exercise without prompting a formal review.
What have we seen in recent JD Edwards license reviews?
Across the roughly 20 to 30 JD Edwards customers we reviewed between 2024 and 2025, licensed quantities were higher than actual use in most cases. Three patterns recurred.
- Leaver seats. Application user counts carried 20 to 35 percent of seats attached to people who had left or moved roles, never reduced after restructures.
- Frozen employee quantities. Employee metric quantities sat at the original order's headcount years after the business had made two acquisitions.
- Dead modules. Components stayed licensed, and on support, at sites that had stopped running the process.
Correcting users and modules cut the maintenance base by 15 to 30 percent in those reviews, before any renewal concession was requested.
What will the Oracle account team say, and how should you answer?
- "JD Edwards is legacy, so plan your move to Fusion now." Point to Oracle's own commitment of Premier Support for EnterpriseOne 9.2 through at least 2037, and say the platform decision will follow your business case.
- "You can reduce licenses, but the rest will be repriced." Ask for the repricing calculation in writing for the exact licenses you plan to terminate, and compare it with the support you save.
- "Move to enterprise wide pricing and you never count users again." Ask for a quote on your corrected current metrics first, then compare both over the full term, including your expected acquisitions.
- "Enabled accounts are authorized users." That is the definition, so disable leavers before any data is collected and keep the dated evidence.
Which contract terms should you ask for at renewal?
| Term to ask for | Why it matters |
|---|---|
| A cap on annual support increases for the term | Support on the corrected base is the number you will pay every year after the renewal. |
| Written relief from repricing when you terminate unused licenses | Without it, the policy can absorb the support you save by removing leaver seats and dead modules. |
| A named list of legal entities covered by the employee metric | It fixes whose headcount counts and gives a starting point after an acquisition. |
| An agreed period before acquired employees count | It gives time to decide whether the new business transfers to your JD Edwards payroll at all. |
| Legacy metrics preserved on any conversion | Pre Oracle terms are often cheaper than the modern metric that replaces them. |
| The database grant wording confirmed on the order | You need to know in writing which reporting tools and schemas the grant allows. |
When should you start preparing for the support renewal?
| Before renewal | What to do |
|---|---|
| 12 months | Pull every ordering document and export the user, role and employee data. |
| 6 months | Disable leavers, list dead modules, count devices and review the database grant. |
| 3 months | Model terminations against repricing and send Oracle your corrected quantities. |
| 1 month | Agree the contract terms above and confirm the support invoice matches the corrected base. |
What to do next
- Reconcile application users. Match enabled accounts against active staff and disable the dormant ones, keeping the dates.
- Recount the employee metric. Use the contract definition, include contractors and agents, and check for both shortfall and surplus.
- Inventory connected devices. List every scanner, weighbridge and terminal against the 50 device floor.
- Check the database grant. Confirm that nothing but JD Edwards touches an ASFU or restricted use instance.
- Model terminations. Price the support saving on leaver seats and dead modules after repricing, before you notify Oracle.
- Plan against 2037. Decide Fusion, third party support and the renewal term on your own timetable. Our Oracle practice can run the review with you.
Holding an Oracle quote or renewal? Our Oracle contract negotiation team works only for buyers, for a fixed fee or 25 percent of what we save you.
Frequently asked questions
How is Oracle JD Edwards licensed?
Per component, on five metrics. Application users cost about $4,595 for Financials or Distribution Management, employee metric components about $185 to $225, expense reports about $6 and UPK developers about $17,500. Each metric has a floor, from 5 users per component to all employees. Support adds roughly 22 percent of the net fee every year.
Who counts under the JD Edwards employee metric?
All employees, plus the contractors, consultants and agents the licensed programs track, whether or not they log in. The count therefore comes from HR and payroll records rather than the user list. For a quick check, compare your licensed quantity with the headcount in your latest annual report, then add contractors and outsourced staff.
What is the fastest JD Edwards licensing saving?
Removing leavers. In our reviews 20 to 35 percent of application user seats belonged to people who had left or moved, and dead modules carried support at sites that no longer ran the process. The saving is the support on those licenses, so it only arrives once you terminate them formally and have modeled Oracle's repricing.
Do warehouse scanners need JD Edwards licenses?
Often yes. Devices that send data to or receive data from JD Edwards with no person at the keyboard fall under the connected device metric, with a 50 device minimum. Price is per device and varies by module. Where a scanner is always worked by a signed in operator, get Oracle's position in writing on which metric applies before you count it.
How long will Oracle support JD Edwards?
Oracle commits Premier Support for EnterpriseOne 9.2 through at least December 2037, with new features delivered as updates to 9.2. JD Edwards World is different: Premier Support for A9.4 ended in April 2022. EnterpriseOne customers can therefore set their own migration date and use the commitment when a proposal is framed around urgency.
Is the database included with JD Edwards?
No. It is licensed separately, commonly as an ASFU grant or through the restricted use licenses in Oracle Technology Foundation for JD Edwards EnterpriseOne. Both limit the database to JD Edwards use. Adding a data warehouse feed or another application's schema to that instance creates a full technology license requirement, so review the instance before any integration project.
Does JD Edwards have a read only or self service user license?
Not under current Oracle metrics. Someone who only runs inquiries on a component is an application user of it, and employee self service is covered by the employee metric on the relevant HR component. Read only and casual tiers appear only in some pre Oracle contracts, which is a reason to keep those terms.
Can you cut JD Edwards support by terminating unused licenses?
Yes, but Oracle's rules shape the result. All licenses in a license set must stay on the same support level, so you terminate licenses rather than drop support on some. Remaining licenses on that order can be repriced, and reinstating lapsed support later costs 150 percent of the last annual fee, prorated over the lapsed months, plus a full year of support.