All posts · BI Reports

OTBI Basics: Oracle Transactional Business Intelligence

OTBI gives Fusion Cloud users self-service reporting directly on live transactional data — no SQL needed. Here's how to navigate subject areas, build analyses, and create dashboards.

Anurag Jangra · January 10, 2026 · 5 min read · ... views

What OTBI is

Oracle Transactional Business Intelligence (OTBI) is the self-service analytics layer built into Oracle Fusion Cloud. It provides real-time reporting on Fusion data — no data warehouse, no extracts, no waiting for nightly loads. Users build analyses using drag-and-drop interfaces against pre-built subject areas.

Subject areas: the data catalogue

OTBI organises available data into subject areas — themed groups of dimensions and facts. Examples:

  • Procurement - Purchase Orders Real Time: PO headers, lines, distributions, suppliers
  • Payables Invoices - Real Time: invoice headers, lines, payments, suppliers
  • Human Capital Management - Workforce: employees, assignments, salaries, absence

Each Fusion module has its own subject areas. Finding the right subject area for your report is the first challenge.

Building an analysis

  1. Navigate to Reports and Analytics → Create → Analysis
  2. Select the subject area (e.g. “Procurement - Purchase Orders Real Time”)
  3. Drag columns into the analysis from the left panel: PO Number, Supplier, Amount, Status, Creation Date
  4. Add filters: Status = OPEN and Creation Date >= @{LAST_N_DAYS}{30}
  5. Add a table, chart, or pivot view
  6. Save to the catalog

Filters and prompts

Filters restrict analysis data. Prompts let users set filter values at runtime (similar to report parameters). For executive dashboards, pre-filter data by business unit or date range using session variables (@{session.BUSINESS_UNIT}).

Aggregation rules

Each metric column has an aggregation rule (Sum, Average, Count, Max, Min). Change via right-click → Edit Formula → Aggregation. For headcount metrics, use Count Distinct on employee_id rather than Count.

When to use OTBI vs BIP

OTBI: ad-hoc analysis, self-service, dashboards, real-time data, no IT involvement needed BIP: formatted documents (PDFs, payslips, POs), complex layouts, scheduled delivery, data from outside Fusion, high-volume report generation

Think Beyond the Implementation

Questions worth sitting with after reading this

01

Why is this architecture appropriate for this specific context — and where would it be the wrong choice?

02

What assumptions did we make that aren't stated explicitly? What happens if those assumptions are wrong?

03

What would break first if the requirements changed — volume doubled, a third system was added, or the deadline halved?

04

What alternatives did we reject, and why? Was the decision made on evidence — or habit?

AJ
Anurag Jangra
Oracle Cloud PaaS Consultant · OIC & VBCS Specialist

4.5+ years delivering enterprise Oracle Cloud integrations and VBCS applications across manufacturing, IT services, and financial sectors. OCI Certified — writes about real-world OIC, VBCS, SQL, and BI Publisher patterns from production experience.

Chat on WhatsApp