If you work in Oracle Fusion Cloud — whether HCM, Financials, SCM, or Procurement — you've almost certainly run into both OTBI and FDI when someone asks for a report or a dashboard. They sound similar, they both sit on top of Fusion data, and both get thrown around loosely as "the reporting tool." They are not the same thing, and picking the wrong one for a given ask is one of the most common mistakes we see on Fusion implementations.
What Is Oracle OTBI?
Oracle Transactional Business Intelligence (OTBI) is the real-time, ad hoc reporting layer built directly into Oracle Fusion Applications. It runs against a set of pre-built subject areas exposed on top of the transactional schema, so when a payroll flow instance completes or a PO is approved, that data is queryable in OTBI almost immediately.
- Data source: Live transactional data, straight from the Fusion application tables (via the OTBI subject areas / RPD-equivalent semantic layer).
- Latency: Near real-time — no batch extract or load window.
- Tooling: Answers/Analysis, Dashboards, and BI Publisher (BIP) reports built off OTBI subject areas.
- Best for: Operational, transactional reporting — "show me pending approval goals right now," "list today's EFT payments," "what's the current headcount by department."
- Scope: Single Fusion pillar at a time in most subject areas (HCM subject areas don't blend natively with SCM or Financials data without extra work).
What Is Oracle FDI?
Fusion Data Intelligence (FDI) — the evolution of the old Fusion Analytics Warehouse (FAW) — is Oracle's pre-built, cross-pillar data warehouse and analytics platform, sitting on Oracle Analytics Cloud (OAC) infrastructure. Instead of querying Fusion's live transactional tables, FDI extracts, transforms, and loads data into its own warehouse on a scheduled basis, then serves it through curated semantic models and pre-built KPI dashboards.
- Data source: A dedicated Autonomous Data Warehouse populated via scheduled ETL from Fusion (and optionally external/custom sources).
- Latency: Batch — typically refreshed daily (or on a schedule you configure), not real-time.
- Tooling: OAC dashboards, pre-built KPIs, augmented analytics (ML-driven insights), and the ability to extend the semantic model with custom subject areas and PVOs.
- Best for: Cross-pillar, historical, trend, and executive-level analysis — blending HCM, Financials, and SCM data in one model, year-over-year comparisons, workforce and financial KPIs out of the box.
- Scope: Built to span multiple Fusion pillars natively, which is exactly what OTBI struggles with.
Side-by-Side: The Core Differences
| Aspect | OTBI | FDI |
|---|---|---|
| Underlying data | Live Fusion transactional tables | Extracted into a dedicated warehouse (ADW) |
| Refresh cycle | Real-time / near real-time | Scheduled batch (usually daily) |
| Cross-pillar analysis | Limited — mostly single-pillar subject areas | Native — HCM, ERP, SCM can blend in one model |
| Pre-built content | Subject areas only, dashboards are DIY | Pre-built KPIs, dashboards, and ML insights out of the box |
| Customization / extension | Custom subject areas via OTBI data model extensions | Semantic model extensions, custom PVOs, augmented sources |
| Licensing | Included with Fusion Applications | Separate FDI/OAC license |
| Typical consumer | Operational users, transactional BIP reports | Executives, analysts, workforce & finance planning teams |
Where OTBI Wins
Anything that needs to reflect what just happened in the system — pending approval tracking, EFT payment reconciliation for the current payroll run, today's requisition status — belongs in OTBI. It's also the natural home for BIP-driven transactional reports and email bursting, since the data is already current the moment it's queried, with no warehouse refresh lag to explain to the business.
Where FDI Wins
The moment a request sounds like "compare this year's attrition against last year's," "show me total workforce cost alongside headcount trends," or "give leadership one dashboard across HR and Finance," FDI is the right tool. It's also far less SQL-heavy to stand up initially — the pre-built KPIs and semantic model give you a working dashboard fast, and the augmented analytics layer surfaces patterns (like attrition drivers) that would otherwise take custom statistical work in OTBI/BIP.
Do You Need Both?
In most mature Fusion environments, yes — they're complementary, not competing. OTBI handles the "right now, single-pillar, operational" layer; FDI handles the "trend, cross-pillar, executive" layer. Trying to force FDI into real-time operational reporting, or trying to force OTBI into cross-pillar executive dashboards, is usually where implementations get stuck fighting the tool instead of the data.
Our Take
At Nexlify, when we scope a Fusion HCM or ERP reporting requirement, the first question isn't "OTBI or FDI" — it's "does this need to be current-second accurate, and does it need to cross pillars?" That answer almost always points to the right platform, and it shapes everything downstream: which semantic layer to extend, whether BIP bursting is even the right delivery mechanism, and how much ETL/refresh design is worth investing in.
Need help deciding between OTBI and FDI for your Fusion rollout — or extending either one with custom subject areas and KPIs? Nexlify Technology builds both, end to end.