Full narration of the briefing. Click a section heading to jump the player to that moment.
Here is the rule that costs the most money when it is assumed rather than checked. Owning a module does not license the modules that surround it. Owning Purchasing does not license iProcurement. Owning Core HR does not license Payroll or Self Service HR.
Owning Inventory does not license Order Management or Advanced Supply Chain Planning. Every line on your ordering document is the entire entitlement, and a module not named on a line is a module you do not have, however logically it sits inside a family you did buy. The family is a planning grouping that Oracle uses to organise a price list. The module is what an auditor prices.
And the dependency runs one way, which is the part that catches people. The extension modules generally need their base module licensed underneath them, so Payroll expects Core HR, iProcurement expects Purchasing, Internet Expenses expects Payables, Order Management expects Inventory. That means a self service or extension rollout is usually two licence lines rather than one: the base, and the thing you actually wanted. But it never runs backwards.
Licensing the base has never licensed the extension, no matter how tightly the two are coupled in the application. Check both directions on your own ordering documents before you plan any rollout, because the dependency map in the implementation guide is a technical document, and it does not tell you what you bought.
Now the error that runs in both directions at once. EBS installs the full stack, so the licensing boundary is a paper boundary, not a technical one, and usage accrues through responsibility assignments, enabled module flags and interface reads long before procurement hears about any of it. Across the reviews behind this series, estates averaged three to five modules enabled or touched by interfaces with no licence line behind them, each one a six figure audit exposure. And the same estates carried two to four fully licensed modules with zero active responsibilities, paying twenty two percent support on a shelf.
One estate, paying for software nobody runs, exposed on software nobody bought.
And the shelf forms in the same places every time, which makes it easy to go looking. Sourcing and Procurement Contracts, added to support a procurement transformation narrative and then never staffed, while category managers keep running events in spreadsheets. Advanced Supply Chain Planning and Demand Planning, the classic planning shelf, where the data was never clean enough to trust a constrained plan so the planners went back to Excel. Learning Management and iRecruitment, displaced by a dedicated talent suite, usually within three years, while the EBS lines stayed on support.
Marketing and Incentive Compensation, where the CRM family shows the most complete abandonment because Salesforce or a commissions tool took the workload. Configurator, Advanced Collections and Internal Controls Manager, licensed for one plant or one controls programme, then quietly dropped when the sponsor left.
Proving a module is genuinely dormant takes three artefacts, and they must be pulled on the same date so they describe one estate at one moment. A responsibility assignment extract showing that no active user holds the module functions. A twelve month transaction count from the base tables showing zero rows, or nothing beyond seeded data. And an interface inventory confirming that no middleware reads the module APIs, because a custom schema or a warehouse feed reading module tables is usage, and it triggered usage claims in a third of the audits we defended.
With those three in hand you can open a support termination conversation. Without them you are asking Oracle to take your word for it.
So the reconciliation that matters is four way: what is licensed, what is used, what is enabled, and what is interfaced. Most estates only ever compare the first two, which is why they are simultaneously overpaying and exposed. Run all four against each other and the picture resolves quickly. Licensed but not used is money you can stop spending, provided you can prove it with the three artefacts.
Enabled or interfaced but not licensed is exposure you want to close on your own timetable, and that matters commercially, because buyers who licensed genuine gaps proactively landed forty to sixty percent below Oracle's opening audit list positions. The same list serves both jobs, and it is also the inventory a Fusion migration starts from, so the work is never wasted.
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