The Oracle Hyperion BI Licensing Guide
Oracle Hyperion and BI products are licensed by a patchwork of metrics: Application User and Named User Plus on the financial close and planning tools, processor and user metrics on Essbase and OBIEE, and suite versus component pricing on BI Foundation. The mix is where audit exposure hides. This guide explains how each product is counted and how to bring the whole estate into a defensible position.
Executive summary
The Oracle Hyperion and Business Intelligence stack is one of the most metric heavy corners of the Oracle catalogue. Hyperion Planning, Hyperion Financial Management, and the close and consolidation tools are typically licensed by Application User or Named User Plus. Essbase carries its own processor and user metrics. Oracle BI Enterprise Edition, often still called OBIEE, and the BI Foundation Suite layer in further metrics and a suite versus component decision. Most estates accumulated these products over years of separate projects, and the result is a tangle of overlapping entitlements that few organisations can reconcile from memory.
That tangle is exactly what an audit exploits. The financial close tools touch large user populations during reporting cycles, Essbase cubes are often more widely accessed than the named entitlement assumes, and BI dashboards reach casual viewers who were never counted. Oracle's measurement scripts surface every one of these populations, and a customer that cannot show how each product is counted faces a compliance claim built on the gap between the entitlement on paper and the access in practice.
This white paper maps the metric for each product in the Hyperion and BI stack, explains where the user counting traps lie, and sets out a buyer side framework for baselining the estate and closing the gaps before Oracle measures them. Read it alongside our BI and analytics licensing service and the Applications licensing guide.
What is inside
- The metric for each product: Planning, HFM, Essbase, OBIEE, and BI Foundation.
- Application User versus Named User Plus on the financial close tools.
- Where casual viewers and integration accounts inflate the count.
- Suite versus component licensing on BI Foundation and when each fits.
- A buyer side framework for baselining and closing the gaps before audit.
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 baseline analytics estates, reconcile metrics, and defend audits on behalf of the buyer. Explore our audit defence guide or request a consultation.