Two Oracle reporting tools that overlap just enough to be confusing — and a straightforward rule for choosing.
OTBI (Oracle Transactional Business Intelligence) is for self-service analysis: users build and pivot analyses over subject areas without writing SQL. BI Publisher is for pixel-perfect formatted output: statutory documents, invoices, statements, anything where the layout is prescribed. The rule is simple — if a person is exploring, OTBI; if a document must look exactly so, BI Publisher.
Most Fusion estates end up using the wrong one somewhere, usually BI Publisher for analysis because a developer was available, or OTBI for a statutory layout because a user started it. Both work badly outside their purpose: BI Publisher analyses are rigid and need development for every change, and OTBI cannot reliably produce a layout to a regulator's specification.
OTBI exposes curated subject areas. If the data is not in one, OTBI cannot reach it — which is often the deciding constraint.
Users build analyses, combine them into dashboards, and drill to the underlying transactions.
BI Publisher starts from a data model — SQL, a view object or a web service — which is a development task.
RTF, Excel or XSL templates control the output layout. The same data model can feed several templates.
BI Publisher can split one run into many documents and deliver each by email or to a destination — statements being the classic case.
A finance team asks for two things in the same meeting. First, a way to explore receivables ageing by business unit, customer and bucket, following anything that looks odd down to the transaction. Second, a statement of account for each customer, formatted to the company's template, emailed monthly.
These sound like one request and are not. The first is analytical: interactive, exploratory, no fixed layout, value entirely in the drill-down. That is OTBI, reporting against a subject area, and building it as a formatted report would mean producing a hundred variants nobody wants. The second is a pixel-perfect document: fixed layout, one per customer, delivered by email. That is BI Publisher with bursting, and building it in OTBI means fighting a tool that was not designed to control layout.
The common failure is choosing one tool for everything because a team knows it. Formatted documents built in OTBI look wrong; analysis built in BI Publisher cannot be explored. The useful test is a single question — does the person receiving this need to look around in it, or does it need to look exactly right?
| Term | What it means |
|---|---|
| Subject area | The pre-built analytical model OTBI reports against, rather than raw tables. |
| Data model | BI Publisher's query definition, which can read tables, views or web services directly. |
| Layout template | The RTF, Excel or XSL template controlling exactly how a BI Publisher output is formatted. |
| Bursting | Splitting one BI Publisher run into many outputs delivered to different recipients. |
| Drill-down | Navigating from a summary to the underlying detail, which is OTBI's natural strength. |
Every question becomes a development request. Users stop asking, and the reporting function quietly stops being useful.
It is not a layout tool. Forcing it produces something close but not compliant.
If the field is not in a subject area, OTBI is not an option regardless of preference. Check before designing.
Hundreds of near-identical user-built analyses become their own problem. Curate a shared set.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Reports by tool against their type | Whether tool choice follows requirement or habit. | |
| Long-running report executions | Usually analytical queries written against the wrong source, or templates doing work the query should. | |
| Scheduled reports with no recipients | Dead scheduling consuming capacity, common in long-lived instances. | |
| Duplicate reports | Near-identical outputs built separately, a sign of no central catalogue. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.