One query against a custom table converts your free embedded BI Publisher grant into a full-use license priced against the $221,250 per processor Analytics tier
Oracle's own Licensing Information User Manual says a full-use BI Publisher license is required the moment the tool reads data outside the host application or the host schema is modified, including adding a column. That single sentence is the pivot on which six- and seven-figure audit findings turn, because every EBS, PeopleSoft, and JD Edwards estate has custom tables. Decide now whether you buy full use at a negotiated 40 to 70 percent off list or you fence the embedded deployment.
Prepared by Redress Compliance · August 22, 2026 · Oracle advisory. BI and Analytics audit defense engagements, 2024 to 2026.
Executive summary
Oracle's published test is binary, not proportional: a single report joining one XXCUST table triggers the same full-use requirement as a thousand of them.
The Licensing Information User Manual language, that full use is required if BI Publisher "accesses any data outside the Oracle Application for which the restricted BI Publisher license is supplied, or if any modification is made to the Oracle Applications (for example.
By adding columns to an existing table)," gives auditors a one-report trigger and gives you no volume defense.
There is no single embedded grant, so a defense built on the EBS wording will not survive a PeopleSoft or JD Edwards finding.
Oracle explicitly instructs readers to consult the price list supplement for each application, meaning you need three or four separate entitlement citations pulled from your own ordering documents, not one generic policy quote.
The exposure is priced off the Analytics tier, where Oracle Analytics Server lists at $221,250 per processor and $2,000 per Named User Plus with a 10 NUP per processor minimum.
An eight-core Intel server at 0.5 core factor is four processor licenses, roughly $885,000 at list before the 22 percent support stream, which is why a modest reporting server produces an outsized audit claim.
The Forms and Reports grant inverts the usual risk: production is covered and development and test are not.
Oracle's Forms and Reports restricted-use grant is limited to production deployment, so the sandbox where your team builds layouts is the unlicensed environment, and it is the environment nobody thinks to fence.
List price on this line has been frozen since 2013, which is your strongest negotiation fact.
Oracle cut BI Suite EE Plus from $295,000 to $221,250 per processor in July 2013 and has not moved it in 13 years, so any claim that "list has increased" is false and any settlement should land in the 40 to 70 percent discount band buyers routinely achieve.
How the embedded grant actually works, application by application
Every embedded BI Publisher right is a restricted use grant attached to a host product, and no two hosts grant the same thing.
Oracle's Licensing Information User Manual sets the universal ceiling in one sentence: a full use BI Publisher license is required if BI Publisher accesses any data outside the Oracle Application for which the restricted license is supplied, or if any modification is made to the Oracle Application.
For example by adding columns to an existing table.
Then the manual immediately narrows it further, noting that many Applications carry tighter restrictions and directing you to the Price List or Price List Supplement for that specific Application.
Read that as written: the E-Business Suite grant, the PeopleSoft grant, and the JD Edwards grant are three separate documents with three separate boundaries, and an entitlement letter for one proves nothing about another.
In EBS, the grant covers publishing and viewing shipped BI Publisher reports with layout changes permitted, plus shipped or newly created reports that read from uncustomized shipped EBS schemas.
A single report against a CUSTOM or XXAP table, or against a shipped table that a developer added one column to in 2011, is outside the grant.
Forms and Reports inverts the usual assumption: its restricted BI Publisher right is limited to production use, so a development or test instance running BI Publisher under a Forms and Reports entitlement is the exposure, not the production box.
JD Edwards splits the right across Core Tools and Technology Foundation, which is why an EnterpriseOne estate needs the actual Price List Supplement pulled before anyone answers an audit question.
Oracle Analytics Server and the older OBIEE and BI Foundation stacks include Publisher outright, which is the escape hatch discussed in our Oracle BI and Analytics on-premise licensing guide.
| Host product | What the embedded grant covers | What breaks it | Where the entitlement is documented |
|---|---|---|---|
| E-Business Suite | Shipped BIP reports, layout changes, new reports against uncustomized shipped schemas | Custom tables, added columns, any non-EBS data source | EBS Price List Supplement plus the LIUM general restriction |
| PeopleSoft Enterprise | BIP as delivered inside PeopleTools reporting, PeopleSoft data only | Reporting across a non-PeopleSoft schema or a modified record | PeopleSoft Price List Supplement |
| JD Edwards EnterpriseOne | Publisher rights differ between Core Tools and Technology Foundation entitlements | Assuming Core Tools carries the same right as Technology Foundation | JD Edwards Price List Supplement, per component |
| Oracle Forms and Reports | Restricted BIP right limited to production use | Any dev, test, QA, or DR instance running BIP | Forms and Reports Price List Supplement |
| OAS, OBIEE, BI Foundation Suite | Publisher included in the licensed BI product, full use within that license | Deploying Publisher on servers not licensed for the BI product | Oracle Technology Global Price List, August 3, 2026 |
The naming reconciliation problem is doing quiet damage. Oracle renamed the product Oracle Analytics Publisher, but contracts signed before 2020 say "BI Publisher" and the underlying XML Publisher lineage goes back to EBS 11.5.10 in 2003.
Your ordering documents, your CSI support lines, and the 2026 audit script all use different words for the same binary. In practice, that mismatch lets an auditor treat a legacy embedded line as unproven and demand you evidence the grant, rather than Oracle evidencing the breach.
Before any conversation with Oracle, map every Publisher install to a named host entitlement and the specific Price List Supplement clause that authorizes it. Instances with no clean mapping are your negotiation surface, not your defense.
Why the standalone SKU is harder to buy than to breach
Here is the structural asymmetry that makes this issue expensive. Breaching the embedded grant takes one developer, one afternoon, and one query against a custom table.
Buying your way clean is genuinely difficult, because all Oracle Business Intelligence technology products are listed only on the Oracle Technology Global Price List, currently the August 3, 2026 edition.
If your account rep produces a quote sourced from an Applications price list, you are not buying full use Analytics Publisher.
You are buying another application-specific or restricted SKU, which reproduces the same boundary you are trying to escape and hands Oracle a second audit finding two years later.
Insist that any quote cite the TGPL by date and part number, and get the words "full use" into the ordering document rather than relying on a rep's email.
On price, be careful with the number everyone repeats. A widely cited figure of roughly $46,000 per processor for standalone BI Publisher, plus 22 percent support, comes from secondary technical commentary last updated in 2021. It is a useful order of magnitude and nothing more.
I could not confirm a current standalone Analytics Publisher line on the August 2026 TGPL, and in my experience Oracle has quietly let that path atrophy.
What the rep will offer instead is Oracle Analytics Server at $221,250 per processor or $2,000 per Named User Plus with a 10 NUP per processor minimum, which is a five to one jump in unit price against the legacy standalone figure and drags in a full analytics stack you may not want.
That is the steer: the cheap remedy is inconvenient to buy, the expensive remedy is always in stock.
Model both metrics before you respond, because the OAS crossover sits near 111 users per processor, a very different threshold from the Database rule of thumb, and our Named User Plus versus Processor decision analysis shows how quickly that arithmetic moves at mid scale.
Oracle Analytics Licensing: OAC, OAS & the One-Way Door
Oracle Analytics is sold as a perpetual per-processor server (OAS) and a per-OCPU cloud subscription (OAC). The prices, the metric math, and why the migration to OAC does not rever
Get the white paper →The binary trigger is a negotiation asset, not just a risk
Oracle could have written the embedded-use limit as a volume threshold. It could have said that the restricted grant survives up to some number of reports, some number of custom queries, or some percentage of non-shipped content. It did not.
The Licensing Information User Manual says a full-use license is required if BI Publisher accesses any data outside the host application, or if any modification is made to that application, and it offers adding a column to an existing table as the illustrative example. One report. One column.
That is a one-way switch, and most buyers read it purely as a hazard. It is also the most useful structural feature of the entire dispute, because a switch with no gradations cannot be argued about on the axis Oracle usually wins on.
Consider what a volume threshold would have produced. Oracle would ask for report inventories, run counts, scheduler logs, and query histories going back to the start of the contract.
You would spend three months reconstructing which of 4,000 report definitions touched which schema in which quarter, and the finding would grow with every log file you handed over.
That is the shape of a Database options dispute or a Java device count, where the vendor's claim is a function of measured activity and your defense is a slow argument about the accuracy of the measurement. Under the binary rule, none of that matters.
Once Oracle demonstrates a single custom-table query, the usage conversation is over, and it took Oracle roughly one script and one afternoon to get there.
What is left is the only question that carries money: how much of your estate does the full-use license have to cover. A processor license is priced against installed and running capacity, not against work performed.
So the claim size is determined entirely by where BI Publisher binaries sit, how many cores those hosts present, whether non-production environments are in scope, and whether the deployment is defined as one BIP install or as every EBS or PeopleSoft mid-tier that has the component staged.
That is an architecture and scoping argument. It is fought with topology diagrams, core factor tables, virtualization boundaries, and environment definitions, not with usage evidence you cannot control.
The practical consequence is that a finding which reads as catastrophic on Oracle's first spreadsheet is usually a scoping exercise in disguise.
An estate that runs BIP across ten application mid-tiers on 32-core hosts generates a theoretical processor count in the mid-hundreds, and against the Analytics tier list that is an eight-figure opening number.
The same custom reporting workload, consolidated onto a dedicated two-socket host with cores capped, isolated from production application servers, and licensed as a discrete instance, is a two-processor to four-processor purchase. Nothing about the breach changed. The perimeter did.
Buyers who treat this as a compliance problem argue about whether the trigger fired; buyers who treat it as a design problem argue about what the trigger fired on, and the second group settles for a fraction of the first.
Three levers do most of the work. Fence custom reporting onto a small, separately licensed host and route all non-shipped content there.
Establish clean environment definitions so development and test instances are documented as such, since some restricted grants (notably the Forms and Reports embedded grant) draw explicit production-only boundaries that cut both ways.
And decommission or document dormant BIP installs on application servers, because installed-and-running capacity that nobody uses still prices at full rate. Each of these is a decision you can execute before or during a negotiation, which is what makes them leverage rather than mitigation.
The same logic governs the wider Analytics estate, and our Oracle BI and Analytics on-premise licensing guide maps how the option packs behave once you are on the full-use side of the line.
The final variable is the one Oracle cannot move. BI Suite Enterprise Edition Plus has listed at $221,250 per processor since Oracle cut it from $295,000 in July 2013.
Thirteen years without a list adjustment means there is no credible "prices go up in Q4" pressure on this line, and no basis for Oracle to claim the anchor is drifting.
What is negotiable is discount depth, where enterprise buyers routinely land 40 to 70 percent below list, and scope language: how the ordering document defines the licensed program, the environments covered, and whether custom schema access is permitted enterprise-wide or only on named hosts.
Settle the perimeter in writing first. The percentage follows the perimeter, not the other way around.
What the pricing math does to the claim size
Run the arithmetic before you respond to anything Oracle sends. Oracle Analytics Server lists at $221,250 per processor and $2,000 per Named User Plus, with a mandatory minimum of 10 NUP per processor and 22 percent annual support on the net license price.
The Intel and AMD core factor is 0.5, so an 8-core server is 4 processor licenses, not 8. That single conversion is where most self-assessments go wrong in Oracle's favor, and it is also where buyers overcorrect by assuming a factor that does not apply to their chip generation.
The NUP versus processor crossover sits near 111 users per processor at these figures, and that number is specific to this price pair.
| Configuration | Processor math | List license | 22% support (year 1) |
|---|---|---|---|
| 8-core Intel host, 1 instance | 8 cores x 0.5 = 4 proc | $885,000 | $194,700 |
| Two 16-core hosts (prod + DR active) | 32 cores x 0.5 = 16 proc | $3,540,000 | $778,800 |
| 4 proc via NUP at minimum (40 users) | 10 NUP per proc floor | $80,000 | $17,600 |
| 4 proc via NUP at crossover (444 users) | 111 users per proc | $888,000 | $195,360 |
| Same estate, fenced to 1 x 4-core host | 4 cores x 0.5 = 2 proc | $442,500 | $97,350 |
The bottom two rows are the whole negotiation. Below roughly 111 users per processor, Named User Plus is cheaper, and at the 10 NUP per processor floor a four-processor footprint costs $80,000 at list instead of $885,000.
Do not import the Database rule of thumb here: every Database line prices NUP at exactly one fiftieth of the processor price, so 50 users is the crossover there. Using 50 on an Analytics line hands Oracle roughly $800,000 of unnecessary processor licensing on a single host.
Our NUP versus processor decision analysis walks the counting rules that make NUP defensible at audit.
Then the support stream. Twenty-two percent compounds against the net license price, so a $442,500 fenced purchase at a 55 percent discount carries roughly $43,800 of first-year support, while the unfenced $3.54 million position carries roughly $350,000 per year forever.
On renewals, the 2026 price list replaced the flat uplift language most buyers remember with an Inflationary Adjustment Rate, and where an active Contractual Cap Rate exists, support increases by the lower of the CCR or the IAR.
Market observations through 2026 show roughly 8 percent annual support increases where no cap applies. Get your cap rate written into the ordering document at the same time you settle scope.
Evidence base: what the audit findings keep showing
Across BI Publisher engagements the same four findings repeat, and none of them depend on Oracle proving bad faith.
The first is custom schema reporting inside E-Business Suite: an XXAP or CUSTOM schema, a bolt-on staging table for a third-party payroll feed, or a single added column on a shipped table.
Oracle's Licensing Information User Manual is unambiguous that a full-use license is required if BI Publisher accesses any data outside the Oracle Application for which the restricted license is supplied, or if any modification is made to the application.
Adding columns to an existing table being Oracle's own worked example.
The second is development and test instances running BI Publisher under a Forms and Reports restricted grant that is scoped to production, which converts a non-production convenience into a licensable deployment on hardware nobody counted.
The third is contract-vintage mismatch, most often in JD Edwards, where the ordering document and price list supplement in force at signature grant narrower rights than the community wisdom your team is operating on.
The manual itself warns that many applications carry tighter restrictions and directs you to the price list supplement for the associated application, which is a written admission that no universal embedded grant exists.
The fourth is a naming problem: entitlement lines say "BI Publisher," Oracle's current documentation and audit script output say "Analytics Publisher," and the reconciliation gap is where an auditor asserts you hold nothing.
Our broader Oracle BI and Analytics on-premise licensing analysis shows the same pattern across the BI stack.
The Analytics tier processor price the claim is measured against, unchanged since the July 2013 reset from $295,000.
Enterprise buyers negotiate into this range off the August 3, 2026 Technology Global Price List, and a frozen 13-year list price undercuts any urgency argument.
The pattern beneath all four is that the trigger is binary and documentary, not volumetric. Nobody argues about report counts or user headcount at the trigger stage.
In our experience the finding is almost always established from a data model export in under a day, which means your rebuttal window is the scoping call, not the findings meeting.
- 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
- Pull the actual ordering document and price list supplement for every host application, not the generic Licensing Information User Manual text, because the EBS, PeopleSoft, and JD Edwards restricted grants are separate instruments with different scopes and Oracle's own manual tells you to read the supplement for the associated application.
- Run a schema inventory of every BI Publisher data model before Oracle does, extracting the SQL from each report and flagging any table or view outside the shipped application schema plus any column added to a shipped table, then classify each hit as remediable (rewrite against shipped objects), retirable, or genuinely required.
- Separate development and test from production under the Forms and Reports grant, since that restricted license is scoped to production use and a BI Publisher instance sitting on a dev server is a standalone deployment on hardware nobody counted, which is the cheapest finding to eliminate and the most expensive to concede.
- Reconcile "BI Publisher" against "Analytics Publisher" across contracts, quotes, support renewals, and audit script output, and get Oracle to confirm in writing that your pre-2020 entitlement line maps to the current product name, because an unreconciled naming gap lets an auditor treat a licensed deployment as unlicensed.
- If full use is genuinely required, fence it to one named host and negotiate into the 40 to 70 percent band, citing the July 2013 reset to $221,250 per processor that has held for 13 years, applying the 0.5 Intel core factor, and testing Named User Plus at $2,000 where your population sits below roughly 111 users per processor, as set out in our Named User Plus versus Processor metric comparison.
The move that saves the most money is the second one, and it is not a licensing move at all. In most estates the majority of custom-schema hits are legacy reports that nobody has run in two years, or reports that could be rewritten against shipped objects with a week of developer time.
Deleting or rewriting those before the audit scope is agreed shrinks the claim to the handful of reports that genuinely need external data, and that residual set is what you buy against, at one fenced host rather than an estate-wide processor count.
Sequence matters. Steps one through four are internal and cost you consulting days, not license fees.
Only enter step five once you know exactly how many hosts genuinely require full use, because Oracle will price against whatever footprint you disclose first, and a disclosed number is very hard to walk back.
Frequently asked questions
Is BI Publisher free if I already license Oracle E-Business Suite?
It is included as a restricted-use license, not a free full-use license. EBS grants the right to publish and view shipped BI Publisher reports, to change layouts, and to run reports against existing uncustomized EBS schemas.
The moment a report reads a custom table or a column you added, the restricted grant no longer covers it and full use is required.
What exactly is the embedded-use limit in Oracle's own words?
Oracle's Licensing Information User Manual states that a full-use BI Publisher license is required if BI Publisher accesses any data outside the Oracle Application for which the restricted license is supplied, or if any modification is made to the Oracle Applications.
For example by adding columns to an existing table.
That is a binary test with no volume threshold. One qualifying report is enough.
Does the same embedded grant apply to PeopleSoft and JD Edwards?
No. Oracle explicitly says many applications have tighter restrictions and directs you to the price list or price list supplement for the associated application. The EBS, PeopleSoft, and JD Edwards grants are separate documents with different wording and different contract vintages.
Build your defense from your own ordering documents, not from a generic policy page.
Why is development and test the problem under Forms and Reports?
The Forms and Reports restricted-use grant for BI Publisher is limited to production deployment purposes only. Using BI Publisher for application development and testing requires a full-use BI Publisher, Oracle BI EE, or Internet Developer Suite license.
This inverts the normal pattern, where non-production is the safer environment, and it is the finding buyers most often miss.
What does a full-use BI Publisher license cost today?
Oracle no longer promotes a clean standalone line item, so exposure is typically priced against the Analytics tier: Oracle Analytics Server at $221,250 per processor or $2,000 per Named User Plus with a 10 NUP per processor minimum, plus 22 percent annual support.
A legacy standalone figure near $46,000 per processor circulates but should be verified directly against the current Technology Global Price List before you rely on it.
Has Oracle raised the BI list price recently?
No. Oracle cut BI Suite Enterprise Edition Plus from $295,000 to $221,250 per processor in July 2013, and that figure has held for 13 years. If a rep suggests list has moved upward, that is not supported by the price list history.
Use the frozen list as leverage when negotiating discount depth on any settlement purchase.
Is BI Publisher included with Oracle Analytics Server or OBIEE?
Yes, within the context of that product's licensed use. If you hold a valid OAS or OBIEE license covering the relevant processors or users, BI Publisher functionality sits inside that entitlement.
The trap is scope: reporting served to users or environments outside the licensed OAS footprint is not covered simply because OAS exists somewhere in the estate.
