The Oracle Applications Licensing Guide

Oracle Applications licensing spans four acquired product families, E-Business Suite, JD Edwards, PeopleSoft, and Siebel, each with different user definitions and module structures. Most overpayment comes from counting application users against the wrong definition, paying for modules nobody uses, and the entangled database licences underneath every application. This guide reconciles the four models.

Executive summary

Oracle's applications portfolio was assembled by acquisition, and it shows. E-Business Suite, JD Edwards EnterpriseOne and World, PeopleSoft, and Siebel were each independent products with their own commercial models before Oracle bought them, and Oracle has largely preserved those models rather than harmonising them. The result is four different ways of counting users, four different module structures, and four different sets of audit traps, frequently sitting inside a single enterprise that grew by acquisition itself.

The defining risk in applications licensing is the user definition. Oracle application user metrics, Application User, Employee, and various module specific definitions, count people by role and access rather than by named login. A single human may consume multiple licensed user types across modules. Organisations routinely license against the wrong definition, either over provisioning by counting every employee or under provisioning by counting only active sessions, and an audit reconciles the gap at list price.

Beneath every application sits the database, and applications audits almost always become database audits. The E-Business Suite technology stack, the PeopleSoft database, and the Siebel repository are all Oracle Database deployments whose licensing is entangled with the application above. This white paper sets out the four application models, the user definitions that decide cost, the module and component traps, and the database entanglement, then presents the buyer side framework for measuring and defending an applications estate. Read it alongside our Applications licensing service and the Database licensing guide.

What is inside

1. The four application families compared: E-Business Suite, JD Edwards, PeopleSoft, and Siebel user models.
2. Application user definitions explained, and why one person can consume several licensed user types.
3. Module and component traps, including read only access, self service users, and indirect access.
4. The database entanglement beneath every application, and how applications audits become database audits.
5. A buyer side measurement and negotiation framework with prioritised recommendations.

Read by application owners, IT procurement, and vendor management teams across thirty countries. Part of a fourteen paper buyer side library.

About the practice

Oracle Software Licensing is an independent buyer side advisory practice with offices in New York, London, and Stockholm. Across more than 750 Oracle engagements the practice has delivered an average audit reduction of seventy percent and over $300M in client savings, drawing on 20+ years of combined licensing experience. We do not resell or implement Oracle software. We measure estates, defend audits, and negotiate settlements on behalf of the buyer. Explore our audit defence service or request a consultation.