E-Business Suite is licensed per Application User and by custom metrics for certain modules, but the audit exposure lives in the restricted-use Oracle Database bundled underneath. EBS counts authorised users — not active ones — and ships with a database that may be used only to run EBS. This sub-guide of the Oracle applications licensing pillar maps the Application User metric, component-vs-suite pricing, and the restricted-use boundary that most EBS findings cross.
E-Business Suite is licensed primarily by the Application User metric — every individual authorised to use a given module, regardless of whether they log in — with a layer of custom metrics for specific modules (for example, $ in revenue for some financials components, expense reports for iExpense, or electronic orders for order management). Representative Application User list prices run around $4,595 per module plus 22% annual support. Critically, EBS bundles a restricted-use licence of Oracle Database Enterprise Edition and Oracle Fusion Middleware that may be used only to run E-Business Suite. The user metric is simple; the restricted-use boundary is where the money is.
By authorisation, not activity. An Application User is anyone you have authorised to use the module, so the count includes dormant accounts, shared logins, contractor IDs, and leavers who were never deprovisioned. Oracle's auditors do not take your declared number at face value — they reconcile it against the application's own responsibility and FND_USER tables, HR headcount, and Active Directory. The single most common EBS under-licensing finding is a declared user count that has drifted below the authorised reality because access lists were never maintained.
| Who gets counted | Counted as a user? | Why |
|---|---|---|
| Active named employee | Yes | Authorised and using |
| Leaver, account not disabled | Yes | Still authorised in FND_USER |
| Shared / training login | Yes | Each human behind it is a user |
| Service / integration account | Often yes | Depends on access granted |
| Read-only self-service (iExpense etc.) | Custom metric | May fall under a different metric |
We reconcile FND_USER and responsibility data against your declared counts before an auditor does.
It depends on footprint. Component pricing licenses individual modules per Application User — economical when only finance, or only procurement, is in scope. As deployment widens across financials, supply chain, HR, and projects, per-component costs compound and a Custom Application Suite or broader bundle at a blended rate becomes cheaper. The decision is not academic: buying the wrong shape locks in either shelfware (a suite where only two modules are used) or runaway per-user cost (components stacked across a wide estate). Model both against the actual responsibility matrix, the same way our Oracle licensing guide recommends for the technology layer.
| Approach | Best when | Risk |
|---|---|---|
| Component (per module) | Narrow, deep usage of a few modules | Cost compounds as footprint widens |
| Custom Application Suite | Broad usage across many modules | Shelfware if only a few are used |
| Mixed (suite + add-on components) | Wide core plus a few specialised modules | Boundary disputes at audit |
The EBS metric reconciliation checklist and the restricted-use boundary map, from 340+ engagements.
Run E-Business Suite — and nothing else. The Oracle Database Enterprise Edition and Fusion Middleware that ship with EBS are granted for restricted use: they exist to host the application, not to serve as a general-purpose database platform. The breach pattern is almost always well-intentioned. A team points a BI tool at the EBS schema for "just one report," a developer adds a custom data mart in the same instance, or an Apps DBA enables Partitioning or Diagnostic Pack to fix a performance problem. Each of those converts a bundled, restricted entitlement into a full-use liability for the database and any option touched.
| Action | Restricted-use status | Exposure |
|---|---|---|
| EBS application reads/writes | Permitted | None |
| Third-party BI tool on EBS schema | Breach | Full-use Database EE by processor |
| Custom data mart in same instance | Breach | Full-use Database EE by processor |
| Partitioning / Diagnostic / Tuning Pack | Outside grant | Each option by processor at list |
Because the exposure lands in the same DBA_FEATURE_USAGE_STATISTICS views any Oracle database records, the EBS database is audited exactly like any other Enterprise Edition instance. The full mechanics of that options exposure are in our Oracle Database options guide, and the middleware equivalent is in WebLogic & Fusion Middleware licensing.
It is the moment to reset, not just re-platform. Because E-Business Suite is covered by Oracle's Applications Unlimited support commitment, there is no support cliff forcing a move — which means you control the timing and can use it as leverage. When you do move to Oracle Fusion Cloud Applications, convert owned EBS entitlements and unused support into cloud credits rather than writing them off, and retire the restricted-use exposure that has accumulated instead of carrying it into the new subscription. Treating the migration as a clean break is how a forced project becomes a negotiated one.
We rebuild your Application User position and audit the restricted-use database before Oracle does. When the number is set, our Oracle contract negotiation team takes it down. $1.8B+ documented savings · 68% average audit-claim reduction · buyer-side only since 2016.
Weekly compliance intelligence for IT leaders.
