BI Suite EE Plus at $221,250 per processor excludes Essbase, Scorecard, and BI Publisher, yet the OBIEE installer offers all three on the same screen
Oracle's own installer presents Essbase, Real-Time Decisions, and BI Publisher next to the OBIEE components you did license, and selecting any of them writes a timestamped footprint into the WebLogic domain that an LMS script will find. BI Publisher alone prices at $49,680 per processor and Scorecard at $89,550, so a mid-sized 16-core Intel estate carrying both as accidental installs is an eight-processor claim worth over $1.1 million at list. Your next move is deciding whether to remediate quietly before Oracle asks, or to price the shortfall now and hold it as renewal currency.
Prepared by Redress Compliance · August 22, 2026 · Oracle advisory. OBIEE and Analytics Server audit defense engagements, 2024 to 2026.
Executive summary
The gap between BI Suite EE Plus at $221,250 per processor and BI Foundation Suite at $300,000 per processor is Essbase, Scorecard, and BI Mobile, and the OBIEE installer does not enforce that $78,750 boundary.
Selecting Essbase during installation deploys the EPM Suite tools into the same WebLogic domain as OBIEE, where they appear as a distinct product in Fusion Middleware Control with a creation timestamp Oracle can date to the day.
BI Publisher is the single most frequent finding in OBIEE audits because it carries its own metrics at $49,680 per processor and $497 NUP, and Oracle LMS scripts query for it specifically.
The only bundled entitlement most customers hold is the restricted-use Analytics Publisher right that ships with E-Business Suite, which does not extend to general-purpose enterprise reporting against non-EBS sources.
Scorecard and Strategy Management is a $89,550 per processor SKU that Oracle de-supported and removed from Analytics Server, so you can be back-licensed for a component with no forward roadmap.
That asymmetry is your strongest negotiation lever: Oracle is asking for six figures per processor for software it will not fix, which makes a remediation credit toward OAS or OAC far more defensible than a cash settlement.
Legacy BI Suite Enterprise Edition estates that added users after the EE Plus transition are structurally non-compliant, because Oracle's licensing documentation bars incremental EE purchases and forces every new user or processor onto EE Plus.
With OBIEE 12c Extended Support ended in August 2025 and Fusion Middleware 12.2.1.4 Premier Support ending December 2026, Oracle has a compressed window to monetize these estates and knows it.
What EE Plus actually includes, and what the installer offers anyway
Oracle's Licensing Information documentation splits the on-premise BI technology stack into three contractual objects: BI Suite Enterprise Edition Plus, BI Server Enterprise Edition, and BI Suite Enterprise Edition Plus Upgrade Only.
Only one of those, the EE Plus entry, carries a dedicated table of included products and components, and that table is the whole of your entitlement. Nothing installed outside it is licensed by implication, by proximity, or by the fact that Oracle's own binary offered it.
The problem is that the OBIEE product installer presents a single product selection screen on which Essbase, Real-Time Decisions, and BI Publisher sit alongside the BI Server, Answers, and Dashboards components you did buy.
Ticking Essbase does not just deploy Essbase: it drops the associated EPM Suite tooling into the same WebLogic domain as OBIEE, where it registers as a separate product in Fusion Middleware Control with an install timestamp. That is a discoverable artifact.
In 25 years of Oracle negotiations, I have not once seen an LMS reviewer accept "the installer offered it" as a defense, and there is no contract language anywhere that supports the argument.
The pricing gap between what EE Plus covers and what sits one checkbox away is where the audit money is. After Oracle's June 2013 repricing, EE Plus moved from $295,000 to $221,250 per processor and Scorecard and Strategy Management from $149,250 to $89,550.
BI Foundation Suite, the bundle that genuinely does include OBIEE, Scorecard, Essbase, and BI Mobile, fell from $450,000 to $300,000 per processor, though the September 2017 Victorian State Purchase Contract list shows it transacting at $324,000 with EE Plus at $238,950.
A reminder that regional and public sector lists diverge from the Global Technology Price List.
Anyone budgeting a remediation should price from the list vintage Oracle will quote, not the one they remember. Our Oracle BI and analytics on-premise licensing guide tracks how these SKU boundaries shifted through the OAS transition.
| Component | Metric and list price | Inside EE Plus at $221,250/proc? | Inside BI Foundation Suite? |
|---|---|---|---|
| BI Server, Answers, Dashboards, Delivers | Included | Yes | Yes |
| Essbase | Separate SKU, offered on OBIEE installer screen | No | Yes |
| Scorecard and Strategy Management | $89,550 per processor | No | Yes |
| BI Publisher | $49,680 per processor, $497 NUP | No | Yes |
| BI Mobile | Bundled component | No | Yes |
| BI Server Administrator | $6,264 NUP | No | No |
| ODI for Oracle BI | $24,840 per processor, $745.20 NUP | No | No |
| Real-Time Decisions | Separate SKU, offered on installer screen | No | No |
Read the table down the middle column, not across. Essbase, Scorecard, BI Publisher, and BI Mobile are all "No" against EE Plus and all "Yes" against BI Foundation Suite, which means Oracle has built a single upsell path out of four separate audit findings.
If a reviewer lands on you carrying Scorecard at $89,550 and BI Publisher at $49,680 per processor, the combined $139,230 per processor claim sits within striking distance of the $78,750 per processor delta between EE Plus and Foundation Suite. That is not an accident of the price list.
It is the mechanism by which an audit becomes a migration.
Two entries deserve separate attention because they are metric traps rather than bundle traps. BI Server Administrator at $6,264 NUP is not in either suite.
And it is priced per named user against a role that most estates hand to three or four people without recording it. ODI for Oracle BI at $24,840 per processor is a restricted-use ODI license.
And organizations that extend those mappings beyond BI-sourced data have converted it into a full ODI requirement.
Neither shows up in a self-declaration exercise because nobody thinks of them as products.
The BI Publisher problem: bundled right, restricted right, and no right
BI Publisher generates more audit findings than any other component in an OBIEE estate, and the reason is structural rather than behavioral. Three entirely different entitlement states produce an identical footprint on disk.
The first is a full-use license, purchased as its own SKU at $49,680 per processor or $497 NUP.
The second is the restricted-use Analytics Publisher right that ships with E-Business Suite: Oracle's Application Licensing Table dated March 10, 2026 confirms that EBS applications include restricted use of BI Publisher, but restricted use means reporting on the licensed application's own data.
Not a general-purpose enterprise reporting platform.
The third state is no right at all, which is where most OBIEE customers sit, because they assumed a $221,250 per processor suite would obviously cover a report formatting engine.
The OAS-era change made the confusion worse rather than better. Oracle Analytics Server genuinely does bundle BI Publisher, along with BI Server, Answers, Dashboards, and WebLogic Server, under a single license. But that bundling is conditional: the components are licensed for OAS purposes only.
Publishing reports from a non-OAS data source, or using the bundled WebLogic to host an unrelated application, converts a bundled right into a separate license obligation.
Customers who read "BI Publisher is included in OAS" and applied that to a pre-OAS OBIEE 11g or 12c estate have imported a right that their contract does not grant them.
LMS scripts are built for exactly this. The collection routine enumerates BI Publisher instances and reconciles the count against Oracle's order records, which means the reviewer arrives already knowing the delta before you have answered a question.
Your defense is documentary, not technical: establish which entitlement state each instance sits in, evidence the EBS restricted-use scope where it applies, and decommission anything that cannot be mapped.
Do this on your own timetable, because the same accidental-use pattern that drives database option findings applies here with a higher unit price.
The asymmetry worth naming: Oracle can distinguish these three states from its order records in minutes, and you cannot distinguish them from your servers at all. That is the leverage gap.
Close it by building an instance-by-instance entitlement map before the audit letter, because the map is worth roughly one negotiating round once a reviewer is on site.
Oracle Database Options & Management Packs: the accidental-use audit trap
The separately-licensed options and packs that ship enabled by default, get switched on with a single click, and become the single largest line item in most Oracle audit findings.
Get the white paper →Why Oracle prices the option packs it will no longer support
The list price of a BI option pack in 2026 is not a price. It is an arithmetic base.
Oracle repriced this family once, in June 2013, and then stopped: BI Suite Enterprise Edition Plus fell from $295,000 to $221,250 per processor, Scorecard and Strategy Management from $149,250 to $89,550, and BI Foundation Suite from $450,000 to $300,000, with named user pricing left at $3,675.
Those numbers have been carried forward, unchanged in substance, for over a decade.
The Victorian State Purchase Contract list from September 2017 shows the same SKUs at localized figures ($238,950 for EE Plus processor, $324,000 for Foundation), and the current Oracle Technology Global Price List still anchors Oracle Analytics Server at $221,250.
A price that does not move for thirteen years while the underlying product drifts toward end of life is not a price signal to buyers. It is a fixed multiplicand that Oracle applies to whatever core count LMS discovers.
Read alongside the product roadmap, the intent becomes legible. Scorecard and Strategy Management is de-supported. There is no OBIEE 14c and there will not be one. Extended Support for 12c ended in August 2025, and Premier Support for Fusion Middleware 12.2.1.4 runs out in December 2026.
Oracle is not selling these SKUs. Oracle has not meaningfully sold these SKUs to new logos in years.
Yet the list entries remain live, fully priced, and fully quotable by an audit team, because the SKU only needs to exist on paper long enough to be multiplied by eight processors and a 22% support back-charge.
That is the mechanism. The audit team and the cloud sales team are running the same play from opposite ends of the same account. The audit function establishes a number, denominated in a currency (perpetual licenses for dead products) that Oracle has no strategic interest in collecting.
The cloud function then offers relief in a currency Oracle does want: OAC subscription, or an OAS term arrangement that pulls you off 12.2.1.4 before the December 2026 support cliff. The claim is not the objective.
The claim is the pressure that makes the migration conversation happen on Oracle's timetable rather than yours.
Once you see the option-pack audit as migration financing rather than compliance enforcement, your concession set changes entirely. A compliance dispute is argued on entitlement documents, install evidence, and the boundary table in the Licensing Information doc.
A financing negotiation is argued on what Oracle's compensation plans reward. Cloud ARR is recognized, recurring, and career-relevant inside Oracle.
A one-time perpetual true-up on a SKU that will not be supported in eighteen months is a bad trade for the rep who books it, however good it looks on the audit finding letter.
The buyer-side implication is direct: do not settle a back-license claim in cash. Cash settles nothing forward.
You pay list-derived arithmetic for perpetual rights on Scorecard, a product Oracle has already de-supported, then pay 22% annually on that inflated net for the privilege of running something with no patch path.
In twenty-five years of these negotiations, in my experience, the customers who paid cash on BI option-pack findings paid twice: once for the true-up, and again eighteen months later when the migration they had not budgeted arrived anyway.
The correct move is conversion. Take the entire computed exposure, including the support back-charge, and treat it as a single credit line applied against a forward OAS or OAC term commitment.
Oracle can book that as new subscription rather than a compliance recovery, which is precisely why the discount depth on the forward term will exceed anything you could extract on the back-license line.
Insist that the settlement document extinguishes all historical claims for the audited period across the full BI estate, not just the SKUs named in the findings, and that the credit is applied to license fees rather than to support.
If your estate mixes metrics, work the arithmetic through the OBIEE Named User Plus versus Processor decision before you commit to the shape of the forward term, because the metric you land on will govern the next renewal, not this one.
How processor counting turns a small install into a large claim
The reason an accidental checkbox becomes a seven-figure line is the Core Factor Table. Oracle counts processor licenses by multiplying physical cores by a factor between 0.25 and 1.0.
Intel x86 carries 0.5, so a 16-core Intel host requires eight processor licenses per licensable product, regardless of whether one analyst ever opened Scorecard. The arithmetic below shows a single mid-sized server carrying two unlicensed components.
| Line | Calculation | Amount |
|---|---|---|
| Host: 16 Intel x86 cores, factor 0.5 | 16 x 0.5 | 8 processor licenses |
| Scorecard and Strategy Management | 8 x $89,550 | $716,400 |
| BI Publisher | 8 x $49,680 | $397,440 |
| License subtotal at list | $1,113,840 | |
| Support back-charge, 22% per year | Applied to net license price | $245,045 per year |
| NUP alternative, minimum test | 8 processors x 10 NUP | 80 NUP minimum per product |
The Named User Plus escape route usually fails. The 10 NUP per processor minimum forces 80 users per product on that host whether you have eight users or none, and at $497 per NUP for BI Publisher the minimum is cheap, but Scorecard NUP economics collapse well before you reach real headcount.
Work the counting rules through our guidance on NUP minimums and audit traps before conceding a metric.
Two multipliers make this worse. Virtualized estates expand the countable footprint, because Oracle counts every host where the software could run under its soft-partitioning position, not where it did run.
And the pricing source matters: all Oracle Business Intelligence technology products sit on the Oracle Technology Global Price List, not the BI Applications list, so an auditor will price from the higher-tier document.
Establish the correct host boundary and core factor before you discuss entitlement, because every downstream number scales from that single count.
The legacy EE to EE Plus uplift trap
The most expensive non-compliance in an OBIEE estate often has nothing to do with which components are installed.
Oracle's Licensing Information documentation states plainly that existing BI Suite Enterprise Edition customers may not license incremental users or processors of BI Suite EE; any addition must be purchased as EE Plus users or processors.
The Upgrade Only SKU exists to convert each legacy EE license to EE Plus, and once that conversion path is on the table, the older metric is closed for growth.
The practical consequence is structural: if your headcount grew, or you refreshed onto a server with more cores, and no EE Plus order line carries an effective date matching that growth, you are short by construction. No installer checkbox is required.
An auditor does not need to find Essbase in the WebLogic domain to build this claim, and in my experience this is the finding buyers are least prepared for because it lives in ordering documents rather than in the estate.
Pull three evidence sets before Oracle asks for them. First, every original ordering document from the EE era, including the effective date of each line and the exact metric named. Second, the EE Plus and Upgrade Only order lines, if any, with their dates.
Third, a headcount and hardware timeline: named user counts at each measurement point and the core count and processor type of every server at each refresh. Reconcile those three against the NUP versus processor decision you actually made, because a metric switch mid-history creates its own gap.
The uplift trap converts a paperwork question into a quantified claim.
At the 2013 repriced list of $221,250 per processor, a single 16-core Intel server refresh (core factor 0.5, so eight processors) that was never uplifted from EE to EE Plus prices at roughly $1.77 million at list before support.
And Oracle will add 22 percent annual support on the net figure plus backdated support on the shortfall period.
Your leverage is timing. If you identify the gap first, the uplift is a negotiated order line at a discount typical of enterprise Oracle transactions. If LMS identifies it, the same gap arrives priced at list with backdated support attached.
Evidence base: what LMS finds and the patterns that repeat
Deployed enterprise-wide under an EBS restricted-use assumption, this is the single most common OBIEE finding.
Dashboards left live after the sponsoring business owner departed still count as deployed and used.
The findings repeat because the collection method repeats.
LMS works from Fusion Middleware Control product inventory, opmn and domain configuration files, deployment timestamps, and its own collection scripts, which query specifically for BI Publisher deployment and compare instances against Oracle's order records.
Five patterns account for most of the exposure we see in OBIEE engagements.
| Finding | How LMS detects it | Why it becomes a claim |
|---|---|---|
| Essbase and EPM tools in the OBIEE WebLogic domain | Fusion Middleware Control shows Essbase as a separate product with an install timestamp | Essbase sits in BI Foundation Suite, not EE Plus. See Essbase standalone versus bundled |
| BI Publisher used for general enterprise reporting | LMS script queries BI Publisher deployments, cross-checked to order lines | EBS restricted use covers Applications-sourced output only, not general reporting |
| Scorecard dashboards still live | Deployment records and dashboard artifacts in the domain config | Deployed and available equals licensable, regardless of active users |
| Bundled WebLogic hosting non-BI applications | Domain config lists deployed applications outside the BI stack | The bundled right is for OAS or BI purposes only; other workloads need full WebLogic |
| ODI running BI Applications ETL | opmn and agent configuration, plus job scheduling artifacts | ODI for BI is a separate SKU at $24,840 per processor; general ETL exceeds the restricted grant |
Two things drive the recurrence. First, timestamps are unforgiving: an installer checkbox ticked in 2016 produces a footprint that survives every upgrade and every staff change, and nobody uninstalls what nobody knows is there.
Second, the restricted-use grants are genuinely narrow, and the narrowness is documented in the Application Licensing Table rather than in the product documentation your BI team reads.
Read those grants against your actual deployment before Oracle does, and cross-reference the wider OBIEE and BI Suite options landscape so you price every finding at once rather than conceding them one at a time.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Inventory the WebLogic domain before Oracle does, and capture install timestamps for every deployed component, because Fusion Middleware Control will show Essbase and the EPM tools as separate products with dates that an LMS script reads as a usage start point.
- Map every installed component to a specific order line and to the Licensing Information table entry for BI Suite EE Plus, since that table is the contractual boundary an auditor works from, and anything you cannot tie to an order line (BI Publisher at $49,680 per processor, Scorecard at $89,550) is an open claim.
- Decommission Scorecard and any unused Essbase footprint now, with documented evidence of removal, including change tickets, uninstall logs, and a signed statement of the date, so the exposure window is closed and dated rather than left running while you negotiate.
- Price the residual shortfall twice, at list and at your own historical discount, because Oracle opens at list on an audit finding and enterprise customers in our experience settle in the 40 to 70 percent discount band, and knowing both numbers defines the settlement range before the first call.
- Open the OAS or OAC conversation on your timetable, not Oracle's, so migration credit for the BI estate is negotiated as commercial value rather than conceded as audit relief, and read our Oracle BI and analytics on-premise licensing guide alongside the NUP versus processor metric comparison before you commit to a target metric.
The sequence matters more than any single step. Remediating before you have priced the exposure hands Oracle a clean baseline and destroys your negotiating position, while pricing before you have inventoried means you are guessing at a number Oracle can already see.
Inventory, map, remediate, price, then convert. Note that on a 16-core Intel estate the 0.5 core factor produces eight processor licenses, so BI Publisher and Scorecard as accidental installs is roughly a $1.1 million list claim.
That figure is your ceiling, not your settlement. Never let Oracle establish list as the starting point for a compliance discussion when your paper record shows a decade of discounting.
Frequently asked questions
Does Oracle BI Suite EE Plus include Essbase?
No. Essbase is included in Oracle BI Foundation Suite, which lists at $300,000 per processor, not in BI Suite EE Plus at $221,250. The confusion comes from the OBIEE installer, which offers Essbase as a selectable component alongside OBIEE, Real-Time Decisions, and BI Publisher.
Selecting it deploys the EPM Suite tools into the same WebLogic domain, where they show as a separate product in Fusion Middleware Control with a timestamp Oracle can read.
Is BI Publisher included with OBIEE or Oracle Analytics Server?
It depends on which product you licensed. BI Publisher has its own Processor ($49,680) and Named User Plus ($497) metrics and is licensed separately alongside OBIEE.
Oracle Analytics Server does bundle BI Publisher, but only for OAS purposes, so using it as a general enterprise reporting engine against other sources exceeds the bundled right. E-Business Suite includes a restricted-use Analytics Publisher right that covers EBS reporting only.
What is Scorecard and Strategy Management worth in an audit claim?
It lists at $89,550 per processor following the 2013 reduction from $149,250. On a 16-core Intel server, which counts as 8 processors at the 0.5 core factor, an unlicensed Scorecard deployment prices at roughly $716,400 at list before back-support.
Oracle has de-supported Scorecard and removed it from Analytics Server, which is exactly the argument you use to convert the claim into a forward credit rather than a cash settlement.
Can we still add users to a legacy BI Suite Enterprise Edition license?
No. Oracle's Licensing Information documentation states that existing BI Suite Enterprise Edition customers may not license incremental users or processors of BI Suite EE and must purchase EE Plus users or processors instead.
Any headcount or hardware growth after that point without a matching EE Plus order line is a compliance gap by construction. Pull your original ordering documents and check the effective date against every subsequent hardware refresh.
How does Oracle count processors for an OBIEE audit claim?
Oracle applies the Core Factor Table to physical cores. Intel x86 carries a factor of 0.5, so an 8-core server requires 4 Processor licenses and a 16-core server requires 8.
Named User Plus is an alternative metric but carries a minimum of 10 NUP per processor, which means small user populations on large hardware still generate large counts. Virtualized estates typically expand the countable footprint further under Oracle's partitioning policy.
When does support for OBIEE 12c end and what are the options?
Extended Support for OBIEE 12c ended in August 2025 and there is no 14c release. The Oracle-supported forward paths are Oracle Analytics Server on premise or Oracle Analytics Cloud.
Fusion Middleware 12.2.1.4 Premier Support ends in December 2026, which compresses the surrounding stack timeline as well. Third-party support is a viable alternative if you intend to stay on OBIEE while you evaluate non-Oracle analytics platforms.
Should we remediate an accidental Essbase or BI Publisher install before Oracle audits?
Usually yes, but only with documented evidence. Decommission the component, record the removal date, retain configuration exports proving it is gone, and confirm no users accessed it in the interim. Silent removal without evidence invites Oracle to price the historical period anyway.
If the component has been in production for years with active users, remediation alone will not clear the exposure and you should price the shortfall and plan the negotiation instead.
