Oracle Fusion · Guide
otbi vs BI Publisher vs bicc — when to use which
The single most common Oracle Fusion reporting question. Short answer: OTBI for real-time ad-hoc, BI Publisher for formatted output, BICC to extract data to a warehouse — and a customer-owned warehouse when you need to join across subject areas, keep history, and reconcile to GL.
| Tool | What it is | Best for | Limitation |
|---|---|---|---|
| OTBI | Real-time, self-service ad-hoc analysis and dashboards off subject areas | Operational reporting, quick analysis | Combines subject areas only through shared dimensions; runs on production; limited formatting |
| BI Publisher | Pixel-perfect, high-volume formatted output (statements, checks, invoices) | Statutory/printed documents, bursting | Heavier to build; not ad-hoc |
| BICC | Bulk extract of view objects to files for a warehouse | Loading a customer-owned warehouse / data lake | Not a reporting tool — it's the pipe |
| Customer-owned warehouse | Conformed model across all subject areas, governed AI Analyst | Cross-module analytics, reconciliation, history | You build it once — that's where Irvine comes in |
The wall teams hit: OTBI combines subject areas only through the dimensions they share, inside one application, and runs on production; BI Publisher isn't ad-hoc; BICC only extracts. The moment you need cross-module analysis (AP + GL + Projects in one view) reconciled and historical, you need a warehouse — built on BICC extracts, modeled with conformed dimensions. Oracle now recommends its Data Extraction tool, which reads a read-only replica of Fusion, for all new extracts, and says it will eventually replace BICC and BI Publisher extracts (Oracle 26C readiness, status October 2026). BICC stays the working path until each of your extracts maps to a business view.
Want the warehouse without the 12-month project?
10-day proof of concept on your cloud — conformed model, reconciled to source, you own it.