EBS User Metrics and Counting Rules in Oracle Audits

How is EBS licensed by users?

EBS is licensed by named users, which means each individual authorized to use a given application module must hold a license regardless of how often they actually use it. This is different from a concurrent metric, where you license the peak number of simultaneous sessions. Under the named user metric the question is never how many people are logged in at once. It is how many people are authorized at all, and that figure includes leavers who were never deprovisioned and accounts created for one off tasks.

The wider compliance picture, including how application metrics sit alongside database and middleware licensing, is set out in the Oracle license compliance guide. EBS user counting is one of the areas auditors examine most closely, because the gap between authorized and active users is usually large.

Who counts as a named user in EBS?

A named user is any individual authorized to access the licensed module, so an occasional or seasonal user counts exactly the same as someone who uses the system every day. This is where most EBS undercounts begin. Teams report the number of people who logged in last month and treat that as the user count, when the metric actually captures everyone with an active account and the right responsibilities assigned. Dormant accounts, shared logins, and access granted for a project that ended all sit inside the licensable figure until they are removed.

The corollary is that disciplined access management directly reduces your license requirement. Every authorized account you cannot justify is a license you are paying for or an exposure you are carrying. The same dynamic appears across the application estate, as covered in EBS in an Oracle audit.

What are application user minimums?

Application user minimums are contracted floors that set the smallest number of users you can license for a given module, so your licensed figure cannot drop below that floor even if your real user count is lower. Many EBS modules carry these minimums, and they mean a module with only a handful of genuine users may still require licensing to the contracted minimum. The minimums are contract dependent, so the figure that binds you is the one in your signed agreement, not a general rule.

Knowing your minimums matters in both directions. They prevent you from claiming a count below the floor, and they stop Oracle from asserting a higher minimum than your contract supports. Reconciling your real user list against the contracted minimums is the step that turns a vague exposure into a precise, defensible number.

A worked example of an EBS count

Consider a Financials module with 600 active accounts in the system. Review shows 180 belong to leavers who were never deprovisioned, 40 are duplicate or test accounts, and 30 are shared service accounts that should map to a single licensed identity. After cleanup, 350 genuine named users remain. If the contracted minimum for the module is 300, the defensible figure is 350, well below the 600 an uncleaned count would have reported.

How do you clean the count before reporting?

You clean the count by deprovisioning leavers, removing duplicate and test accounts, mapping shared logins to identifiable individuals, and reconciling the result against your contracted minimums, all before any figure leaves your organisation. Cleanup that happens after you have reported a number is far harder to defend, so the order matters. The same evidence discipline applies to interfaces and automated accounts, which carry their own counting rules covered in PeopleSoft licensing and audit exposure.

Your next step

An accurate EBS user count protects you from paying for access you do not use and from a finding built on an uncleaned list. An independent buyer side review reconciles your authorized users against your contracted metrics and minimums and reports the lowest defensible figure. Read the pillar guide for the full compliance framework.