Oracle's application estate — E-Business Suite, PeopleSoft, JD Edwards, Siebel — is licensed by user and custom metrics, but the largest audit findings come from the technology stack bundled underneath. Every application licence carries a restricted-use grant of Oracle Database Enterprise Edition and Fusion Middleware that may only run the licensed application. In our 340+ engagements, the moment that database is used for custom reporting, an integration, or an Enterprise Edition option, the restriction breaks and a full-use liability appears that dwarfs the application itself.
Oracle applications are licensed by metric — most commonly the Application User (every individual authorised to use the programs, whether or not they log in) and a set of custom metrics such as $ in revenue, employees, expense reports, or electronic orders for specific modules. Representative E-Business Suite Application User list prices run around $4,595 per module plus the standard 22% annual support, but the headline metric is rarely where audit money is lost. Each application licence bundles a restricted-use licence of the technology underneath — Oracle Database Enterprise Edition and Oracle Fusion Middleware (WebLogic) — that you may use only to run the licensed application. Step outside that boundary and you owe full-use licences for the database, the middleware, and any Enterprise Edition options that were activated.
This is a pillar guide. It maps the application metrics, the restricted-use trap, the support economics of Oracle's acquired product lines, and the migration leverage most customers leave on the table. Three companion deep-dives go further: Oracle E-Business Suite licensing (the Application User metric and component-vs-suite pricing), Oracle PeopleSoft & JD Edwards licensing (acquired-product metrics and Applications Unlimited support), and Oracle WebLogic & Fusion Middleware licensing (the standalone-middleware trap). For the broader picture, start from our Oracle licensing guide, the Named User Plus metric explainer, and the Oracle Fusion Cloud applications migration analysis.
Oracle's three on-premise application suites grew from different acquisitions, so each carries its own metric vocabulary. The table below maps the products to their principal licence metrics. Treat it as the starting inventory for any audit-readiness review — the first question in an Oracle applications audit is always "on what metric, and how is it counted?"
| Product line | Principal metrics | Common custom metrics |
|---|---|---|
| E-Business Suite (EBS) | Application User | $M revenue, expense reports, electronic orders, POs |
| PeopleSoft (HCM, FSCM) | Application User, Employee | $M revenue, hosted named user |
| JD Edwards EnterpriseOne | Application User, Employee | $M revenue, module-specific |
| Siebel CRM | Application User | Component, $M revenue |
| Underlying Database EE | Restricted-use (bundled) | Processor / NUP if used beyond the app |
| WebLogic / Fusion Middleware | Restricted-use (bundled) | Processor if run standalone |
The Application User metric counts authorised individuals, not concurrent or active ones. A leaver who was never deprovisioned, a service account, and a shared "training" login all count. Oracle's auditors reconcile your declared user count against HR headcount, Active Directory, and the application's own responsibility tables — so an unmaintained access list is one of the quickest routes to an under-licensing finding. The Named User Plus rules that govern the technology layer use a similar "authorised, not active" definition.
We rebuild the authorised-user position from the application's own tables, not the spreadsheet you last updated three years ago.
Because it is the largest entitlement most customers do not know they are constrained by. When you buy E-Business Suite, PeopleSoft, or JD Edwards, Oracle includes a restricted-use grant of Oracle Database Enterprise Edition and Oracle Fusion Middleware. That grant is generous in one direction — you do not separately license the database that stores application data — and a trap in the other: it may be used solely to support the licensed application. The instant the same database instance serves a custom data mart, a third-party BI tool reads from it directly, an integration writes to a custom schema, or an Enterprise Edition option such as Partitioning or Diagnostic Pack is activated, the restriction is broken and full-use licences are owed.
| Activity inside the application database | Restricted-use status | Exposure created |
|---|---|---|
| Running the licensed application (EBS, PeopleSoft, JDE) | Permitted | None |
| Custom schemas / data marts in the same instance | Breaks restriction | Full-use Database EE by processor |
| Third-party BI / ETL reading the app database directly | Breaks restriction | Full-use Database EE by processor |
| Partitioning, Advanced Compression, Diagnostic/Tuning Pack | Outside the grant | Each option by processor at list |
| WebLogic hosting non-Oracle applications | Breaks restriction | Full WebLogic by processor |
This is why an application audit and a database audit are the same audit. Oracle's LMS team runs the application user reconciliation and the DBA_FEATURE_USAGE_STATISTICS options check in one pass — the options activated inside an EBS database are read exactly as they would be in any other Enterprise Edition instance. The mechanics of that options exposure are covered in depth in our Oracle Database options guide; the WebLogic side is in the middleware sub-guide.
The restricted-use boundary map, the metric reconciliation checklist, and the migration levers used across 340+ engagements.
No — and that gap between the sales narrative and the support roadmap is real leverage. Oracle's Applications Unlimited programme commits to continued Premier Support for PeopleSoft, JD Edwards EnterpriseOne, E-Business Suite, and Siebel, with published roadmaps extending into the 2030s. A migration to Fusion Cloud is therefore a commercial decision, not a support-cliff necessity. Many customers concede a forced-march timeline they were never obligated to accept, surrendering the strongest card they hold at renewal: the credible option to stay.
| Product | Support posture | Buyer leverage |
|---|---|---|
| E-Business Suite | Premier Support committed under Applications Unlimited | "Stay" is credible; negotiate Fusion BYOL terms |
| PeopleSoft | Premier Support roadmap into the 2030s | No support cliff; resist forced timelines |
| JD Edwards EnterpriseOne | Continuous delivery; long roadmap | Third-party support is a genuine alternative |
| Siebel | Maintained; smaller install base | Migration optional, not mandated |
We separate the support facts from the sales narrative and rebuild the renewal position around the option to stay.
Exposure is lopsided. The application user count is the visible metric, but the technology stack underneath is where six- and seven-figure findings originate. The table reflects the pattern across our Oracle applications engagements.
| Finding source | Frequency | Typical trigger | Severity |
|---|---|---|---|
| Restricted-use DB used beyond the app | Very high | Custom reporting / BI reading app database | Very high |
| EE options inside app database | High | Partitioning, Diagnostic/Tuning Pack activated | High |
| Application User under-count | High | Stale access lists, undeprovisioned leavers | Medium |
| WebLogic running standalone | Medium | Middleware reused for non-Oracle workloads | High |
| Custom-metric misdeclaration | Medium | Revenue / employee bands crossed without true-up | Medium-high |
The lesson buyers take from this is structural: separate the application database from any non-application workload, keep the technology layer's feature usage clean, and treat the user reconciliation as a quarterly control rather than an audit-week scramble. The deep mechanics live in the three cluster sub-guides; the cross-cutting audit playbook is in our Oracle audit defence guide.
A move from EBS or PeopleSoft to Oracle Fusion Cloud Applications is the single largest commercial event in the Oracle applications lifecycle — and the one moment your leverage is highest, because Oracle wants the cloud win. Three levers decide the outcome. First, support runway: because Applications Unlimited removes the support cliff, you set the timeline, not Oracle. Second, BYOL and credits: existing on-prem entitlements and unused support should be converted into cloud credits, not written off. Third, the technology cleanup: a migration is the natural moment to retire the restricted-use exposure that has accumulated, rather than carry it into a new contract. We cover the destination economics in the Oracle Fusion applications analysis.
| Migration lever | What it does | When to pull it |
|---|---|---|
| Hold the support runway | Removes Oracle's timeline pressure | Before any cloud commitment |
| Convert entitlements to cloud credits | Recovers value of owned licences | During Fusion negotiation |
| Clean the restricted-use stack | Stops carrying old liability forward | Pre-migration readiness |
| Benchmark the SaaS subscription | Anchors per-user pricing to market | At proposal stage |
A clean Oracle applications position has four parts: a reconciled Application User and custom-metric count rebuilt from the application's own tables; a documented boundary around every restricted-use database and middleware instance, proving it runs only the licensed application; a quarterly options-and-features review of those databases identical to the one you run elsewhere; and a renewal strategy that treats the support runway as the asset it is. Customers who hold those four read their own exposure months before Oracle's LMS team does — and walk into a Fusion conversation with leverage instead of a deadline. Where an unlimited agreement sits over the estate, the same discipline feeds directly into Oracle ULA negotiation, turning a certification deadline into a restructuring opportunity.
Our Oracle practice reconciles application metrics and audits the restricted-use stack underneath, so you know what an audit will find — before Oracle does. $1.8B+ documented client savings · 68% average audit-claim reduction · buyer-side only since 2016.
The price-book changes, audit triggers, and negotiation levers we see across 340+ engagements, in one short email — before they reach you as a vendor proposal.
