Practice iii · Applications
Oracle Applications Licensing
Independent buyer side advisory for E-Business Suite, JD Edwards, PeopleSoft, and Siebel licensing and user definitions.
Independent buyer side advisory for E-Business Suite, JD Edwards, PeopleSoft, and Siebel licensing and user definitions.
Oracle applications licensing spans E-Business Suite, JD Edwards, PeopleSoft, and Siebel, each priced on its own user definitions, modules, and metrics. Most exposure comes from miscounted application users and modules embedded in a suite. A buyer side review reconciles the definitions to actual use and harmonises contracts acquired through mergers.
Oracle's four application families each carry their own pricing logic, and none of it is intuitive. E-Business Suite licenses by Application User and by module, where a single named user often requires entitlements across several modules. JD Edwards splits between EnterpriseOne and World, with user types that map imperfectly to job roles. PeopleSoft prices by application and by metric that ranges from employee count to revenue. Siebel counts named users by component. A position assembled across all four, often through acquisition, is rarely consistent.
The user definition is the battleground. Oracle's Application User metric counts individuals authorised to use a program, not the individuals who actually log in. Self service modules, where every employee technically has access, can be read as licensing the entire workforce even when a fraction ever transacts. The gap between authorised and active is the single largest source of overpayment in the applications estate.
Modules embedded in a suite are the second trap. A customer who buys a financials suite may find that procurement, projects, or advanced modules within it carry separate entitlements. Usage of an embedded module that was assumed to be included generates a finding. The suite boundary is contractual and frequently misunderstood.
Mergers and acquisitions turn all of this into archaeology. Acquired entities arrive with their own Oracle contracts, their own metrics, and their own shelfware. Harmonising them into a single defensible position, and recovering duplicate entitlements, is work the buyer has almost never done before Oracle audits the combined estate.
Mapping authorised versus active users across E-Business Suite, JD Edwards, PeopleSoft, and Siebel, with a defended methodology for self service access.
Identification of which modules are genuinely in use, which are embedded in a suite, and which carry separate entitlements.
Confirmation that employee, revenue, and record based metrics are calculated against the contractual definition rather than the high water mark.
Consolidation of Oracle contracts inherited through mergers, with recovery of duplicate and overlapping entitlements.
Assessment of custom code and integrations that touch licensable modules and can extend the metered population.
Removal of shelfware and rebalancing of the support stream before the next renewal locks it in.
We open the channel with Oracle on your terms, fix the scope of the conversation, lock the calendar, and ensure no measurement data leaves the perimeter without buyer side review.
An independent measurement against the same ruleset Oracle applies, performed earlier and with cleaner data. Every finding is categorised by exposure tier and tied to the contract clause that governs it.
Findings are documented and argued line by line. Concessions are priced. We have sat on Oracle's side of these tables and know which positions hold and which dissolve.
The settlement is converted into forward commercial value rather than backward payment, with renewal protections, audit cure provisions, and portability written into the result.
Applications engagements scope to the number of families and the complexity of the contract history. A single family user reconciliation fits a fixed fee. A multi family harmonisation after a merger suits a retainer. Where a finding is live or a recovery is in play, a gain share arrangement ties the fee to the outcome.
The right structure depends on the engagement. Read our engagement model overview to see when a fixed fee, a retainer, or a gain share arrangement fits, then request a consultation to scope your estate.
E-Business Suite uses the Application User metric, which counts individuals authorised to use the program, not those who log in. Self service modules where every employee has technical access can be read as licensing the whole workforce. Reconciling authorised against active users is the core of any EBS review.
PeopleSoft prices by application and by a metric that varies, from employee count to revenue to records processed. The metric must be calculated against the contractual definition, not the highest figure the business has ever reported, which is where most PeopleSoft overpayment originates.
They are separate product lines with separate licensing. EnterpriseOne and World carry different user types and metrics. A combined estate, often the result of acquisition, needs each line reconciled on its own terms before a single position can be defended.
Not always. A suite has a contractual boundary. Modules such as procurement, projects, or advanced financials may carry separate entitlements even when they appear inside the suite. Using an embedded module that is not included generates a finding.
Acquired entities bring their own contracts, metrics, and shelfware. The combined estate is rarely consistent. Harmonising the contracts and recovering duplicate entitlements is essential before Oracle audits the merged organisation, and it frequently surfaces recoverable overpayment.
Yes, and it is the most common inflation. If every employee can technically reach a self service module, Oracle may read that as licensing the entire workforce. A defended active user methodology, agreed in the contract, prevents the org chart from setting the price.
Before a renewal, immediately after an acquisition, and on any audit contact. Applications exposure compounds through user growth and inherited contracts, so a baseline before renewal prevents the position from drifting against you.
The database that every application family runs on, with its own metric and option pack exposure.
View the practice →Hyperion, OBIEE, and Essbase, which draw on application data and carry their own user metrics.
View the practice →When application growth across an acquired estate justifies an unlimited agreement or a clean certification.
View the practice →A buyer side reconciliation of user definitions and modules across E-Business Suite, JD Edwards, PeopleSoft, and Siebel prices the estate against the contract rather than the org chart.