Full narration of the briefing. Click a section heading to jump the player to that moment.
There is no such thing as an E-Business Suite licence. Welcome to the Oracle EBS Licensing Series from Redress Compliance. Six short briefings, and one goal: that you can read your own EBS entitlement the way an Oracle auditor reads it. I am Tom, Claire is with me on the numbers.
Start with the thing most finance teams get wrong on day one. You did not buy a suite. You bought a list of modules, each one a separate line, each line carrying its own quantity and its own metric. A module that is not named on a line is a module you do not have, however obviously it belongs to a family you did buy.
That single sentence explains most of the findings we see.
Oracle groups over a hundred licensable modules into eight families: Financials, Procurement, Projects, HCM, Supply Chain, Manufacturing, CRM, and the analytics and governance lines. The family is a planning grouping. The module is the entitlement, and audits price at module level. Across the EBS reviews behind this series, mid market and large estates ran between twelve and thirty modules with genuine daily activity, against entitlement lists carrying twenty to forty five lines.
That gap is not waste in the accounting sense. It is a support annuity, and you can often stop paying it, provided you can prove the module was never used. Notice the direction of the error, though: the same estates also averaged three to five modules enabled or touched by interfaces with no licence line behind them at all.
Here is the asymmetry that decides your decade. Oracle will add quantity on your existing metric within days, cheerfully, at whatever discount you can negotiate. Changing the metric itself is a different animal: it needs a new ordering document, and it reprices against the current list, which means your legacy discount is back on the table. So metrics move up easily and almost never move back down.
The discount applies once. The metric applies every year, to every renewal, through every acquisition, for as long as you run the module. When you are in the room and you have one thing left to push on, push on the metric.
Run the arithmetic once and it changes how you negotiate. Seventy two percent of the ten year cost of a module sits in support, not in licence. Take a typical two hundred user Financials module at a sixty percent discount: roughly three hundred and sixty eight thousand dollars of net licence carries about nine hundred and twenty seven thousand dollars of support across ten years, compounding at the three percent annual uplift most contracts permit. That is why a deeper discount matters more than it looks, because it lowers the base that support is calculated on.
And it is why a dormant line hurts more than it looks. A single unused Sourcing line for forty users at fifty five percent off is close to a hundred and fifty six thousand dollars over ten years for software nobody opened.
Now the part that dwarfs the module stack. EBS runs on an Oracle database, and that database is licensed separately, in processors, at technology list prices. A two node production estate on thirty two Intel cores is sixteen processor licences: seven hundred and sixty thousand dollars of Enterprise Edition list before options, and past one point three million with the option stack a production EBS estate typically runs. That is before a single application user is counted.
And be careful with the vocabulary, because it is a trap in itself. Application User is not Named User Plus. They come from different price lists and count different things. You can be perfectly compliant on Application Users and badly exposed on the database beneath them, and that is the single most common shape of EBS audit finding we see.
So here is the ground we cover. Next session, Application Users, the metric you can actually control, and the dormant thirty to forty percent hiding in most estates. Then the enterprise metrics, Employee and revenue, where growth reprices you with no change in usage at all. Then modules and the prerequisites nobody checks, because owning Purchasing does not license iProcurement.
Then the compliance traps, which drift into place with no purchase order and no decision. And finally the negotiation, and the baseline that ends an audit before it starts. Your first move before any of that: pull one list of every module you pay support on, and one list of every module anyone actually used last quarter. Most estates have never seen those two lists side by side.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator