Oracle EBS concurrent user licensing: what your old contract covers, and why the audit count gets it wrong.

A Concurrent User license covers peak simultaneous use, so 300 licenses can lawfully serve 850 named accounts. Audit scripts count the accounts, and a dated record of your peak is what stops that count becoming a finding.

What does an Oracle EBS Concurrent User license entitle?

A Concurrent User license covers peak simultaneous use of E-Business Suite, whatever the number of people who hold accounts. A contract for 300 Concurrent Users supports any named population whose peak simultaneous use stays at or under 300.

Take a company with 300 Concurrent User licenses, 850 named accounts and a peak of 180 simultaneous users, measured across a full quarter that includes period close. It is compliant with 120 seats of headroom. A workforce three times the seat count can lawfully share the grant.

Why is the current Oracle glossary the wrong reference?

Oracle's current License Definitions and Rules still contain a metric called Concurrent User, but it means something else. Today it covers individuals who may use the programs at the same time and who are your customers or prospective customers. Employees and business partners are excluded.

An EBS order from the late 1990s that licensed your own staff on Concurrent Users was written under a different definition. Read through the modern glossary, your staff could appear to fall outside the grant. Point to the definition printed in, or incorporated by, the order you signed.

How does Concurrent Device differ?

Concurrent Device applies the same concurrency test to devices connected at one time. Shared workstations, terminal servers and warehouse scanners each need a reading against your own wording, so check the paper before relying on any summary of this metric.

Why do Oracle audit scripts misread concurrent licenses?

The standard EBS data collection counts named accounts, and concurrent paper does not license named accounts. On the company above, the script reports 850 users against a grant of 300. That looks like a shortfall of 550 licenses, when the measured peak of 180 leaves the company comfortably inside its entitlement.

The extract is built for Application User, the current EBS metric, which counts every individual authorized to use a module whether or not they are using it. For that metric a list of accounts and responsibility assignments is the right input. For a concurrency grant it measures nothing the contract prices.

That gap becomes a finding only when the customer cannot produce its own peak figure. Our Oracle audit guide covers the review sequence, and hidden Oracle audit risks covers other places the collection overstates use.

How does a misread turn into a conversion offer?

Companies that have run for twenty years on the same EBS paper keep receiving conversion offers. The old licenses still work and support has not ended. The offers arrive because the old paper holds headroom that Oracle can only recover if you give up the metric.

1. The misread creates exposure. The script sets the account total beside the license count, and the difference is framed as unlicensed use.
2. The exposure creates urgency. A finding priced at current list for 550 users is a large number on a letter.
3. The conversion resolves the urgency. Oracle offers to settle by moving you to Application User or another current metric that prices your whole population, with support recalculated on the replacement licenses.

A dated concurrency record breaks this chain at the first step. With your peak on file and your own definition in the room, the script output becomes a spreadsheet to reconcile. The conversion conversation goes back to being an optional trade.

How do you measure peak concurrency in Oracle EBS?

Turn on Sign-On Audit, add the self service session data, and sample at least a full quarter that includes period close. File the peak with its method and date before any audit letter arrives, because a record made in normal operation is far harder to dispute than one rebuilt under pressure.

Which EBS settings and tables hold the session data?

• Sign-On:Audit Level profile. The values are None, User, Responsibility and Form. User level records who signs on, log on and log off times, and the terminal. The higher levels add responsibilities and forms opened.
• The audit tables. Sign-On Audit writes to FND_LOGINS, FND_LOGIN_RESPONSIBILITIES and FND_LOGIN_RESP_FORMS. The Signon Audit Users report gives a first view of who signed on and when.
• Self service sessions. Oracle's own documentation notes that most Sign-On Audit reports are specific to the Forms interface. Sessions in OAF and JTF based pages are recorded in ICX_SESSIONS, and Page Access Tracking adds page level detail.
• The purge programs. Purge Signon Audit Data deletes audit rows created before a date you set, and Purge Inactive Sessions clears old rows from ICX_SESSIONS. Check whether either is scheduled, and archive the rows before they run, or your quarter of evidence disappears.

Test the audit level in a non production instance first. My Oracle Support note 1938090.1 describes deadlocks and locks on FND_LOGINS after the Sign-On:Audit Level profile was set on 12.2 systems, so involve your applications DBA before switching it on in production.

How do you turn session rows into one peak figure?

Session rows are start and end times. The peak is the highest number of distinct licensable units active at the same moment. Your counting rule decides the answer, so write it down before you run the numbers.

• Close abandoned sessions. Users who shut the browser without logging out leave sessions with no end time. Cap each at the ICX: Limit Time value, the same limit the Disable Inactive Sessions program uses to end abandoned sessions, or the peak inflates.
• Count individuals or devices as your paper says. On Concurrent User paper, one person with two open sessions is one user. On Concurrent Device paper, count what the definition counts.
• Separate automated activity. Concurrent requests and interface accounts that run without a person at a keyboard should be reported on their own line. Tie any exclusion to the wording of your definition, and document the reason.
• Sample the busy days. Month end and quarter end close drive the peak in finance heavy EBS installations.

Which documents decide what an old EBS contract covers?

Your entitlement is the sum of every document Oracle and your company have signed, read in date order. For an EBS customer from the 1990s that can mean thirty years of paper. The current price list and the last renewal quote describe none of it.

• Original ordering documents. They state the metric, the quantity and often the definition itself.
• The master agreement in force at each purchase. An order placed under an older master agreement uses that agreement's definitions.
• Amendments. They can widen or narrow the entities allowed to use the licenses, or change a metric on a single line.
• Migration documents. Every past migration redefined something, often the metric on a group of lines. They belong in the main file.
• Support renewal invoices. These are useful as evidence of what Oracle has continued to support, though an invoice does not define what you own.

How do you write the entitlement register?

Build one row per license line from the chain. Record the metric, the quantity, the definition version that applies and the entity scope, with a reference to the source document. Store the register and the scanned documents where an audit response team can reach both within a day.

When Oracle's audit team presents its own entitlement summary, compare it line by line with the register. Challenge every row that cites a newer definition than your order.

Should you accept an Oracle offer to convert EBS concurrent licenses?

Accept only when your concurrency record and entitlement register are complete, the replacement cost test says the terms are worth it, and the timing is yours. No technical deadline forces the decision. Oracle announced in March 2026 that Premier Support for EBS 12.2 runs through at least 2037.

A support renewal continues your existing base. A conversion is the one event that reopens it. Support is recalculated on the replacement licenses, legacy discounts typically disappear in the process, and the concurrency headroom goes with the old metric. Any urgency attached to an offer is commercial.

How do you run the replacement cost test?

Ask what the same entitlement would cost if you bought it today, then compare that with what the conversion takes away. The hypothetical below uses Oracle's September 10, 2026 EBS price list, where Financials is $4,595 per Application User with $1,010.90 a year of support.

The discount and the legacy support figure are illustrations, and your own numbers will differ. The direction usually holds, because Application User prices all 850 authorized people while the concurrent grant only ever had to cover a peak of 180. Clean dormant accounts before any count, because Application User counts people who are authorized, active or not.

Why we do not recommend converting early to tidy up the paper

A common suggestion is to convert legacy metrics early so that compliance is simpler and a later cloud move is easier. We disagree, because the simplicity is paid for in headroom and discounts you cannot buy back.

The old paper has no expiry date. Keep it, measure it, and convert only when Oracle wants something from you, such as a larger cloud commitment, and will pay for the metric with price.

What will the account team say, and how should you answer?

• "Your user count is well above your license count." Answer with the metric language from your order and the dated peak record. Do not defend the account count, because the contract never priced it.
• "Legacy metrics are no longer supported." Ask for the policy reference in writing. Your latest support renewal invoice, which lists the legacy lines Oracle is still supporting, says otherwise.
• "The conversion credit is only available this quarter." Say you will review it on your own timetable. Your licenses are just as valid next quarter, and similar credits tend to reappear at the next quarter end.
• "Converting settles the audit." Ask for the finding to be closed on its merits first, then discuss any conversion as a separate commercial proposal with its own pricing.

What contract terms should you ask for if you do convert?

• A support cap. New support no higher than the current support on the lines being replaced, so the conversion cannot raise the base.
• Carried discount. The legacy discount percentage applied to the replacement licenses and to any later additions of the same product.
• A defined count. The Application User quantity set from your cleaned account list, with the list attached.
• A closed audit. A written statement that the review is closed with no findings for the converted lines.
• A complete migration document. Every old line with its metric and quantity, so the chain can be rebuilt later.

What have we seen on legacy EBS concurrent contracts?

Three patterns recur in the legacy EBS contracts we review. Each one hands the audit team an advantage the paper never gave it.

1. No concurrency register. The company has never measured its peak, so the script's account count stands unopposed.
2. A scattered document chain. Orders, master agreements and migration papers sit across decades of storage, and entitlement gets argued from the renewal quote instead of the orders.
3. Conversions accepted under audit pressure. Companies trade the old paper at the one moment its price is guaranteed to be worst.

Under audit pressure, a reconstruction is an argument. A dated record is a fact.

All three are fixed in the same order. Find the paper and measure the peak first, and only then put a price on any change to the contract. The wider EBS material, including Application User and Employee metrics, sits in the Oracle knowledge hub and our EBS licensing guide.

What to do next

1. This quarter. Set Sign-On:Audit Level to at least User after testing, archive the audit rows before any purge, and capture ICX_SESSIONS for self service users.
2. After the first full quarter. Calculate the peak with a written counting rule, and file it with the method, the date and an owner.
3. In parallel. Assemble the document chain in date order: orders, master agreements, amendments and migration paperwork, stored where the audit response team can reach it in a day.
4. From the chain. Write the entitlement register with metric, quantity, definition version and entity scope for each line.
5. Before any conversion talk. Run the replacement cost test so the discussion starts from what the entitlement is worth to you.
6. When script output arrives. Reply with the definition and the register, and hold back raw data until the scope is agreed. Our Oracle practice can run the defense and the conversion pricing with you.

Frequently asked questions