Concurrent User, Concurrent Device, and Professional User metrics predate the modern price list, yet they still govern the estates that hold them. What the old paper entitles, how audits misread it, and when a conversion offer deserves a refusal.
Concurrent User and Concurrent Device licenses from the 1990s remain valid Oracle E Business Suite entitlements, and their original definitions still govern the estates that hold them. Oracle withdrew those metrics from sale; it never revoked them.
Old paper is frequently stronger than its modern replacement. A concurrency metric can lawfully cover a named population several times its size, which is exactly why conversion offers keep arriving.
This guide is the entitlement archaeology: what legacy metrics entitle, how audits misread them, and when a conversion deserves a no. Background sits in the Oracle knowledge hub, the Oracle practice, the Oracle contracts guide, and the audit response playbook.
The right for a stated maximum number of simultaneous users or devices to use the licensed programs, however many individuals exist. A 300 Concurrent User contract lawfully supports any named population whose peak simultaneous use stays at or under 300.
| Era | Metric family | What it measures | The trap today |
|---|---|---|---|
| Through the late 1990s | Concurrent User, Concurrent Device | Peak simultaneous use or devices | No modern tooling measures it for you |
| Around 2000 | Professional User, Custom Applications Suite | Named individuals, suite wide or bundled | Broad module rights later paper lost |
| From 2002 | Application User, per module | Named individuals per module | One person can consume several licenses |
| Alongside, ongoing | Employee, Order Line, Expense Report, revenue based | Business volumes, not users | The count moves with the business |
| Today | Mixed estates | Several definitions at once | Each vintage governs its own quantity |
Oracle revises metric definitions over time and versions them, which is why one metric name can mean different things on different contracts. Current definitions sit on the Oracle applications price list; yours sit in your ordering document, and yours win for your licenses.
Never accept an audit position, or write an internal report, that quotes a definition newer than your paper.
Badly, unless you control the measurement. Standard collection reads named accounts and responsibilities, which measures Application User style definitions. Applied to concurrent paper it counts the wrong unit and overstates the position, sometimes by multiples.
Turn on session level accounting and build your own record. EBS sign on audit captured at the session level, sampled across at least a full quarter including period close, produces a defensible peak figure with a documented method.
Do it before any audit letter arrives. A measurement created during a dispute is worth a fraction of one filed quarterly for two years.
State early, in writing, that the licenses are governed by the definitions in the referenced ordering documents and that any measurement must follow that text. Then run the sequence from the audit defense readiness checklist rather than improvising under deadline.
White Paper · Oracle EBS
Oracle E Business Suite Licensing
The EBS metrics and negotiation levers. Read it free.
By rebuilding the document chain, because entitlement is the sum of thirty years of orders, amendments, and migrations, not whatever the last renewal quote says. The register is tedious to build and decisive to hold.
Ask Oracle for its install base and license inventory records, then treat the answer as Oracle's claim rather than your baseline. In our reviews the vendor record and the customer record disagreed more often than they matched, and the party holding original documents wins those arguments.
A 1997 license granted to one subsidiary does not automatically serve today's group. Check the customer definition clause on each vintage before assuming enterprise coverage, especially after restructuring. The Oracle contracts guide covers the general mechanics.
Divestitures cut the other way. Paper granted to the parent rarely follows a carve out without Oracle's consent, and consent is a negotiation. Price it into the deal before signing, not after separation day.
More than the support renewal suggests, because its value is what it would cost to replace, not what it costs to keep. Run two calculations before any conversation about giving it up.
Price the covered population on today's metrics at today's list, then compare that to the support you pay on the legacy lines. In concurrency heavy estates the replacement figure is routinely several times the carrying cost, and that multiple is your negotiating asset.
Legacy lines usually carry support calculated from decades old net fees. A conversion recalculates from the replacement position, so the annual stream can rise even when quantities look flat. Model the stream over five years on both paths; the crossover point is the price of the offer.
As a license migration: the old licenses terminate, replacement licenses on current metrics issue, and the support stream is recalculated on the new position. The paperwork says modernization. The economics usually say repricing.
Illustration: how a conversion manufactures a shortfall
An estate holds 300 Concurrent User licenses, carries 850 named accounts, and measures peak concurrency at 180. It is compliant with headroom.
The offer converts each concurrent license into two named licenses, producing 600 Application Users, and invites the estate to buy the remaining 250 at list. Compliant before the offer, short after it. The shortfall was created by the metric change, not by usage.
It replaces a definition Oracle cannot easily measure with one its scripts count natively, and it moves your support base onto current pricing. Conversion pitches typically arrive wrapped inside a Fusion or cloud proposal; the commercial sequencing for that wider conversation is the EBS negotiation playbook.
There is a middle path worth proposing: a definition amendment that modernizes measurement language while preserving quantities, discount, and support base. Oracle resists it, which tells you what the full migration is really worth to them.
As leverage, provided you arrive knowing what it entitles. A verified register lets you resist repricing, keep the concurrency headroom, and trade a conversion only for value you priced yourself.
Mixed estates are normal: concurrent licenses on core Financials sitting beside Application User buys from later projects. Track each quantity under its own definition and never blend them into one count. A blended spreadsheet is how legacy rights get surrendered by accident.
Modern classification questions, from self service boundaries to leaver hygiene, belong in the EBS compliance guide. And settle the metric question before any infrastructure move; the counting change at cutover is mapped in the EBS cloud licensing guide.
Refuse while the old metric covers you and nothing forces a change. Consider one only when the legacy position is unmeasurable, the estate is shrinking, or Oracle pays for the simplification it wants. The table gives the short version.
| Your situation | Decision | Why |
|---|---|---|
| Peak concurrency comfortably under the ceiling | Refuse | The conversion would create the licenses you then buy |
| No session data exists to prove the position | Fix measurement first | Never convert to escape homework |
| Estate shrinking or modules retiring | Price conversion against termination | Shrink the support base, do not reprice it upward |
| Conversion tied to a Fusion or OCI deal | Price it as consideration | Your old paper is the concession, so charge for it |
| Audit pressure applied to force conversion | Hold the definition | Findings on the wrong metric collapse against the text |
The common advice is to convert old metrics to current ones for simplicity, cleaner audits, and easier administration. We disagree. Among the legacy holdings Fredrik Filipsson examined through 2024 and 2025, every conversion offer reviewed raised the measured unit count, and most repriced the support stream in the same signature. The simplicity is real, but it is Oracle's simplicity: definitions its scripts can count, and a support base at current pricing. The buyer side rule is that old paper converts only when you have measured both positions yourself and the deal pays you for the optionality you surrender, not before.
Primary sources: Oracle applications price list, Oracle lifetime support policy for applications, Oracle E Business Suite product page, Oracle contracts and licensing hub.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Oracle retired the concurrent metrics from the price list, not from your contract. The paper you hold is the paper that governs.
Yes. They are perpetual entitlements that remain enforceable on their original definitions, and paying support keeps them current. Oracle withdrew the metric from sale, which is not the same as revoking it.
A stated maximum number of devices using the programs simultaneously, measured at the front end of any multiplexing. Shift workers sharing one terminal consumed one device, which made the metric attractive for factories and warehouses.
A named user metric from the era around 2000 that priced broad suite access per person rather than per module. Estates holding it often carry wider module rights than the same spend would buy today, which is worth verifying before any conversion.
The one in your ordering document. Metric definitions are versioned over time, and the text in force at your purchase governs your licenses. Insist that measurement follow that text.
Only if you have measured both positions and the deal pays for what you surrender. Conversions raise the measured unit count and reopen the support base, so the default answer is no.
The stream is recalculated on the replacement licenses, which typically strips legacy discounts. Support arithmetic, not license fees, is usually the real cost of a conversion.
Enable sign on audit at the session level and sample at least one full quarter, including period close. File the method with the peak figure; a dated internal record beats any reconstruction produced under audit pressure.
No. Premier Support for EBS 12.2 runs to at least 2037, and perpetual licenses do not expire. Any urgency attached to a conversion offer is commercial, not technical.
Redress runs legacy entitlement work inside the Vendor Shield subscription, buyer side only. The team reads your original paper before it reads Oracle's summary of it.
Continue with the Oracle services page, the module reference in the EBS module catalog, and the gated E Business Suite white paper.
The Oracle account team pushes Fusion at every EBS renewal. The buyer side data shows most EBS estates have two to five more years of defensible runway. Run the math before signing the Fusion contract.
The buyer side moves that keep your Oracle estate honest at renewal.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →
Independent buyer side advisory. No Oracle reseller relationship. No sales kickback. We sit on your side of the table on every EBS renewal decision.
EBS metric mapping, integration account redlines, right size playbooks, support uplift caps, and the Fusion versus EBS decision data from every Oracle engagement we run.
