Oracle EBS Negotiation. A buyer side paper on the support stream that pays Oracle forever.

Oracle E Business Suite (EBS) is a mature on premises ERP. Most enterprise customers paid for the perpetual licenses years or decades ago, and the live commercial conversation now is the annual support stream at twenty two percent of net license value, indexed by Oracle's CPI escalator (typically three to eight percent).

That support stream is the highest margin line item in the Oracle relationship. It is also one of the most negotiable, because Oracle has shifted its growth posture entirely to Fusion Cloud, Oracle Database 23ai, and OCI. EBS is no longer the strategic product.

This paper sets out how to use that to recover support cost, manage Premier Support to Sustaining Support transitions, defend audit exposure on the technology stack (WebLogic, Database, Java SE), evaluate the Fusion migration honestly, and run the eleven move buyer side playbook into the next renewal. Read the related Oracle services practice, the Oracle knowledge hub, and the Oracle Fusion ERP negotiation.

The numbers worth holding onto. A typical mid market EBS estate (around five hundred named users, full Financials and Procurement plus Order Management, on premises Database Enterprise Edition with Partitioning and Diagnostics Pack, WebLogic, and a Java SE deployment for forms) pays annual support of one and a half to four million dollars. Across the engagements we run, twenty to thirty five percent of that support spend is recoverable without compromising functionality, either through support negotiation, third party support migration, license stack rationalization, or a structured Fusion trade in.

What you will learn

• The Oracle EBS module pricing map. Named User Plus list prices across Financials, Procurement, Project Management, Order Management, Manufacturing, HCM, and CRM (Siebel) modules, with the realistic discount range Oracle accepts on net new processor purchases (forty to sixty percent).
• The Named User Plus versus Application User versus Custom Application User decision tree. Where each metric applies, the user counting traps (employee count minimums for some modules, the indirect access rule), and how to avoid Oracle's default sizing.
• The hidden technology stack tax. WebLogic Server requirement, Database Enterprise Edition options (Partitioning, Diagnostics Pack, Tuning Pack), and the Java SE deployment risk. The stack frequently costs more than the EBS modules themselves.
• The Premier to Sustaining Support timeline. EBS 12.2 Premier Support continues through 2034 with the latest Oracle extension. The earlier 12.1 cohort is on Sustaining Support. What changes at each transition, and where the negotiation leverage sits.
• The third party support math. Rimini Street, Spinnaker, and Support Revolution typically cut the support line by fifty to sixty percent. The functional trade off (no new patches, no Oracle escalation path) and when it makes sense.
• The Fusion migration trade honestly. Where Oracle's cloud migration credits and PPM offers actually save money, and where they recreate the original lock in with a worse cost curve.
• The audit posture against EBS estates. Database options sprawl, WebLogic deployments, Java SE on EBS application servers, and the entity scope creep from M and A activity.
• The eleven move buyer side playbook. Sequenced moves from internal census through alternative posture, with dollar values against each.

Table of contents

Who this is for

CIOs and CFOs running EBS at scale, IT procurement leaders preparing the next support renewal, Oracle Center of Excellence and ERP CoE leaders, M and A teams handling EBS scope changes in divestitures or acquisitions, and finance teams modeling the cost of staying on EBS versus migrating to Fusion. The paper is written for buyer side decision makers. There is no Oracle product marketing in it.