Contents
Key takeawaysHow JD Edwards is licensedNo read only user typeApplication usersThe employee metricConnected devicesSurplus and shortfallCounting like an auditorWhat our reviews foundReplies to the account teamWhat to do nextFAQJD Edwards EnterpriseOne is licensed per component on five metrics, and most of them count something other than a person at a screen. The metric printed on your ordering document decides the bill, whatever job titles people use in meetings.
- Five metrics, no tiers. Application user, employee, connected device, expense report and UPK developer; professional, casual and read only are not Oracle metrics.
- Authorization is the test. An account counts until its access is removed on a date you can prove, whether or not anyone logged in.
- Entitlements are per component. Surplus on Financials does nothing for a shortfall in Distribution, and one new role can raise two counts at once.
- The employee metric counts people who never log in. Contractors and agents the programs track are included, and quantities frozen at the original order go stale with each acquisition.
- Devices count too. Scanners, weighbridges and terminals feeding transactions without a person at the keyboard fall under the connected device metric.
- Count from roles. In our reviews, user lists built from the sign on table overstated counts by 15 to 30 percent.
- Overcounting repeats every year. Support is charged on the licensed quantity, so each extra seat keeps billing until you terminate it formally.
How is JD Edwards EnterpriseOne licensed?
JD Edwards EnterpriseOne is licensed component by component, and each component carries one of five metrics: application user, employee, connected device, expense report or UPK developer. Most of them count something other than a person at a screen. The metric printed against each line of your ordering document decides what you owe.
The words used in meetings rarely match that paper. Teams talk about power users and casual users, while the contract talks about authorized individuals, tracked populations and devices, one component at a time.
| Metric | What it counts | Typical minimum | Where the count hides |
|---|---|---|---|
| Application user | Each individual authorized to use the component | About 5 per component | Dormant accounts and shared logins |
| Employee | Everyone the programs track, agents and contractors included | The whole population | Acquisitions and outsourced staff |
| Connected device | Devices exchanging data with the programs with no human interaction | About 50 devices | Scanners, weighbridges, shop floor terminals |
| Expense report | Reports processed in a rolling twelve month period | About 1,000 reports | Seasonal volume and rejected resubmissions |
| UPK developer | People authorized to build simulations and documentation | 1 developer | Training teams and implementation partners |
The list prices behind each metric are in our JD Edwards pricing models guide. Minimums, and even which metrics Oracle offers, change by price list vintage, so your own ordering document is the only reference that counts.
Where do the minimums bite?
They bite at the small end. A two person treasury team on a component still bills about five application users, and a site with 20 scanners buys about 50 connected devices. A small expense rollout pays for about 1,000 reports a year, so a pilot rarely costs what the per unit arithmetic suggests.
What if your orders predate the current price list?
Older orders can carry metrics Oracle no longer sells, such as concurrent users on pre Oracle JD Edwards paper. That is usually a better position than the customer realizes, because a concurrent count covers only the people signed in at the same moment. Read our analysis of concurrent licensing on older paper before you agree to convert anything.
Employee and Revenue: The Metrics That Grow Without You
Is there a casual or read only user type in JD Edwards?
No. Professional, casual and read only tiers are not Oracle metrics for JD Edwards. They come from other vendors and from some pre acquisition JD Edwards contracts, and asking Oracle for a view only price wastes a round of the negotiation.
Three rules replace the ladder of user types most people expect:
- Reporting access is use. Someone who runs inquiries against a licensed component is an application user of it, even if they never enter a transaction.
- Self service falls under the employee metric. Employees using self service functions are covered through the employee count on that component. There is no cheaper user class for them.
- External suppliers are a named exception. Oracle's license definitions state that use of the JD Edwards Supplier Self Service programs by your external suppliers is included with your application user licenses.
What you can negotiate is the quantity, the split of users across components and the audit language in the order.
Why we would not spend negotiating time on an inquiry user price
A common suggestion is to press Oracle for a discounted inquiry or read only user, since a large share of your population only looks at data. We disagree. The metric does not exist on current paper, and the request tells the account team you have not read your own order.
Spend the effort on the count instead. Removing authorizations people do not use lowers the number under rules Oracle already applies, and quantity and component split can then be negotiated on the corrected base.
The JD Edwards licensing brief
The metric map, minimums by vintage and our counting method in one download.
Get the white paper →Who counts as a JD Edwards application user?
Oracle defines an application user as an individual authorized by you to use the licensed application programs, whether they run on one server or several. Authorization is the test the auditor applies. Whether the person logged in during the sample period does not decide it.
- One person, one user. Two accounts held by the same individual are one application user.
- Shared logins multiply. Two individuals sharing one account are two application users, and the shared account hides both of them from a simple account list.
- Roles decide components. A Financials user granted a Manufacturing role becomes an application user of both components, and both counts rise.
Do inactive accounts still count?
Yes. An account no one has opened for two years counts until the authorization is removed and you can prove the date. Leavers, restructures and finished projects leave these accounts behind, because the leaver process often stops at the corporate directory and never reaches JD Edwards security.
Why can one extra role cost more than it looks?
The entitlement is bound to the component. Internal teams think in terms of access to JD Edwards, while the contract thinks in access to Financials, Distribution or Manufacturing. A role granted for a month end task can put a person on a second component's count and keep them there.
Give temporary grants an expiration date in the Role Relationships application (P95921). The role then lapses on its own, and the record shows exactly when the person stopped being authorized.
What does the JD Edwards employee metric count?
The employee metric counts the population the licensed programs track, whether or not those people ever log in. Oracle's definition covers full time, part time and temporary employees, plus agents, contractors and consultants who have access to, use or are tracked by the programs.
On payroll, HR, and health and safety components, that is the whole workforce by definition, including outsourced staff performing services for you. A count of badge holders is undercounted by construction. Nothing done technically changes the number, so the contract wording on agents, contractors and tracked populations is where the negotiation happens.
| Line | People | Running total |
|---|---|---|
| Employees licensed on the original HR and Payroll order | 4,000 | 4,000 |
| Joined through two acquisitions | +900 | 4,900 |
| Left with a divested business unit | −350 | 4,550 |
| Contractors set up in the programs for time entry | +280 | 4,830 |
| Shortfall against the order | 830 |
A directory count would show 4,550 people and put the gap at 550, missing the 280 contractors the programs track. Had the divestment been the larger change, you would instead be paying support on people who left with the business.
Why do employee quantities go stale?
Nothing forces an update. The quantity is set at signature and stays there while the business buys and sells companies. In about one in three of the JD Edwards environments we reviewed, employee quantities were still frozen at the original order headcount, sometimes two acquisitions out of date.
What employee metric wording should you ask for?
- A tracked population per component. A written definition of who each component tracks keeps contractors who never appear in the programs out of the count.
- A grace period for acquisitions. A set period to license acquired employees stops a deal that closes mid term from creating an instant shortfall.
- A reduction right on divestment. Support should fall with the headcount, instead of billing people who left with a sold business.
- A stated count date and data source. The audit then measures the same population you measured.
Oracle does not grant these by default. Each is easier to win in a new purchase than in an audit settlement.
Do scanners and shop floor devices need JD Edwards licenses?
Often they do. Oracle's connected device metric covers each unique device that sends data to or receives data from the application programs without requiring human interaction. Shop floor scanners, weighbridges and handhelds feeding transactions with no human at the keyboard fit that description, with a typical minimum of about 50 devices.
In our reviews these devices sat on no one's license inventory at all. Operations buys them and an integration team connects them, while IT asset management tracks servers and people. An auditor can trace transactions arriving in JD Edwards back to the device that sent them, so the devices need their own inventory pass.
Does a surplus on one JD Edwards component offset a gap on another?
No. Each metric grants use of one licensed component only. Two hundred spare Financials seats do nothing for a sixty seat gap in Distribution, because Oracle bills the gap at list and ignores the surplus.
Support makes the mistake more expensive. It runs at roughly 22 percent of net license fees and is charged on quantity, not usage, so every spare seat keeps billing each year until you formally terminate it.
| Line | Calculation | Amount |
|---|---|---|
| Distribution gap at an assumed list price | 60 users x $5,000 | $300,000 |
| First year support on the gap | 0.22 x $300,000 | $66,000 |
| Support on spare Financials seats, at an assumed net $2,500 each | 0.22 x (200 x $2,500) | $110,000 a year |
| Spare seat support over three years | 3 x $110,000 | $330,000 |
The unit prices are invented, so use your own order. At any price, the internal view that the two components net out to 140 spare seats is worth nothing in a settlement.
How do you stop paying support on seats you do not need?
You terminate the licenses, in writing. Oracle's support policies require every license in a license set to sit at the same support level, so you cannot keep some Financials users on support and drop the others.
Termination triggers Oracle's repricing policy. Support on the licenses left on that order is repriced at current list less the standard discount, capped at what the whole order cost before and never below what the remaining licenses already paid. That can absorb most or all of the saving, so model it first with our note on Oracle support costs.
How do you count JD Edwards users the way an auditor will?
Start from the roles that grant access to each licensed component. The sign on records carry every account ever created, while the role map carries the authorizations an auditor will test, and that difference is where most overstated counts come from.
- Export role relationships. Pull the user and role pairs, with effective and expiration dates, from the Role Relationships table (F95921) for each production environment.
- Map roles to components. Use the application security defined in Security Workbench to decide which licensed components each role opens.
- Collapse to people. Merge the accounts one person holds in the user profiles (F0092), and split any shared account into the individuals who use it.
- Take out removals you can prove. Expired roles, and accounts disabled in user security (F98OWSEC) before the count date, come out with the date as evidence.
- Check use before the count date. On Tools release 9.2.1.2 or later, Object Usage Tracking shows which applications each user runs. Use does not set the count, but it shows which authorizations to remove.
| Metric | Where to look | What to watch for |
|---|---|---|
| Employee | HR master records, contractor lists from procurement, outsourcing contracts | Acquired staff, contractors entered for time or safety records |
| Connected device | Integration logs, device management inventory, operations asset register | Scanners, weighbridges, terminals on the shop floor |
| Expense report | Processed report volume over a rolling twelve months | Seasonal peaks and rejected reports submitted again |
| UPK developer | Named authors of simulations and documentation | Training teams and implementation partners |
Do the count before any hosting or platform change as well, since the same metrics travel with you. Our JD Edwards cloud migration guide covers the migration question every JD Edwards customer eventually faces, and our guide to running an internal Oracle license audit covers staffing and timing.
What have we seen in recent JD Edwards license reviews?
Across roughly 20 to 30 JD Edwards environments we reviewed in 2024 and 2025, the licensed quantity and the quantity the evidence supported were different numbers in almost every case. The gap ran both ways: overcounted users paying support every year on one side, uncounted devices building audit exposure on the other.
- User lists from the wrong table. Lists taken from the sign on table instead of the roles that grant access overstated counts by 15 to 30 percent.
- Stale employee quantities. About one environment in three still carried the headcount from the original order.
- Devices off the books. Scanners, weighbridges and handhelds feeding transactions appeared on no license inventory.
- Surplus treated as cover. Spare seats on one component were counted internally against a shortfall on another. That is not how the entitlement works or how Oracle counts, and it was the most expensive internal habit we found.
Run the count on Oracle's definitions before Oracle does.
The customers who came out well counted on Oracle's definitions first and terminated surplus formally so support fell with it. They licensed devices before an auditor found them, and updated employee quantities each time the workforce changed instead of leaving the order two acquisitions out of date.
What will Oracle's account team say about your JD Edwards counts?
Oracle's team will start from its own data and definitions. These are the lines we hear most, with replies that hold up.
- "Every account in the system is a licensed user." Reply that an application user is an individual. Duplicate accounts collapse to one person, and accounts with a role expiration or disable date before the count date are out, with the records attached.
- "We cannot credit your Financials surplus against Distribution." Accept it, since that is the contract, and ask for the Distribution purchase and the Financials termination to be priced together, with the repricing shown line by line.
- "Your employee quantity has to reflect today's headcount." Agree the tracked population component by component, take out divested staff, and ask for the acquisition grace period in writing.
- "An enterprise wide metric would end the counting." Oracle's metric list includes enterprise measures based on revenue or cost of goods sold, and those grow with results outside IT's control. Compare any such offer with the cost of your corrected count.
The sequence for cutting cost once the count is right is in our JD Edwards cost reduction guide.
What to do next
- Gather every order. Pull each signed JD Edwards ordering document, including those from acquired companies, and list the metric and quantity for every component.
- Count users from roles. Build the application user count from role relationships per component, merge duplicate accounts and split shared ones.
- Remove unused access with a date. Expire roles and disable accounts people no longer need, before any count date, so the system holds the evidence.
- Reconcile the employee metric. Compare the licensed quantity with the tracked population, contractors and outsourced staff included, and correct it in both directions.
- Inventory connected devices. Walk the integrations with operations and list every device posting to JD Edwards without a person at the keyboard.
- Decide what to terminate. Stop netting surplus against shortfall, pick the surplus to terminate, and model the support repricing before you send notice.
- Get help before Oracle asks. If a renewal or an audit letter is coming, our Oracle practice runs the count with you.
Frequently asked questions
What metrics does Oracle use to license JD Edwards?
Five, on the current component price list: application user, employee, connected device, expense report and UPK developer. Each is a contract definition, whatever job titles suggest. One contract can mix them, for example application users on Financials and employees on Payroll, and your ordering document says which applies where.
Is there a casual or read only user license for JD Edwards?
No. Those tiers belong to other vendors and to some pre acquisition JD Edwards paper. Anyone running inquiries on a licensed component is an application user of it, and self service users sit under the employee metric. Put your negotiating effort into quantity, component split and audit language instead of a tier Oracle does not sell.
Do inactive JD Edwards accounts need licenses?
Yes, until the authorization is removed with a provable date, even if the account has been dormant for two years. The best evidence sits inside JD Edwards: an expiration date on the role relationship or a disabled flag in user security, recorded before the count date. An email saying access was removed carries far less weight.
What are the JD Edwards license minimums?
Roughly five application users per component, 50 connected devices and 1,000 expense reports, with UPK at one developer. Minimums and metric availability vary by price list vintage, so check your own ordering document. The floors matter most for pilots and small business units.
Can spare licenses on one JD Edwards component cover a shortfall on another?
No. Each entitlement covers one component, so two hundred spare Financials seats cannot cover a sixty seat Distribution gap. The fix is two separate actions: buy the missing Distribution licenses, and terminate the surplus Financials licenses in writing if you want their support to stop, after modeling Oracle's repricing rule.
Who counts under the JD Edwards employee metric?
Everyone the licensed programs track: full time, part time and temporary staff, plus agents, contractors and consultants. The quantity follows that population however few people sign on, so an HR team of a handful of users can still need thousands of licenses. Build the count from HR records and contractor lists together, since either source alone falls short.
Do external suppliers need JD Edwards licenses?
For JD Edwards Supplier Self Service, no. Oracle's license definitions include use of those programs by your external suppliers in your application user licenses. Supplier staff given accounts on other components, such as Distribution inquiries, count as application users of those components.