Explain OTBI: Oracle Transactional Business Intelligence in Oracle Applications

43 / 60

Reportingintermediate

OTBI: Oracle Transactional Business Intelligence

Explain OTBI's role as Fusion Cloud's native, real-time, ad hoc reporting tool

OTBI is Fusion's built-in ad hoc reporting. Its distinguishing property is that it queries the live transactional database, not a warehouse.

OTBI is like a hotel concierge desk that lets guests request custom information (an analysis) using plain language and predefined categories (subject areas) rather than requiring guests to personally search through the hotel's raw operational records — and the concierge only shares information the guest is actually authorized to know.

Key Concepts

Subject areas hide the data model. A subject area is a curated, business-language view over Fusion's tables:

    "Payables - Invoices Real Time"
      folders:  Invoice, Supplier, Business Unit, Time
      measures: Invoice Amount, Paid Amount, Open Amount

A business analyst drags fields into columns and applies filters. OTBI generates the SQL, including the joins, which they never see.

That is what makes it self-service. The alternative is knowing that supplier data lives in TCA across several tables and how to join them.

Real-time, and the trade that comes with it.

    traditional BI   extracted overnight into a warehouse, reported
                     from there. Fast, and a day behind.
    OTBI             queries the transactional tables now. Current,
                     and it competes with transaction processing.

So an OTBI analysis scanning a year of invoices runs against the same database serving users. A badly filtered analysis is not just slow for its author.

That is the practical reason OTBI is for operational questions — what is open now, what needs approval today — and a warehouse is still right for multi-year trend analysis.

Security is inherited, which is the underrated part. Subject areas respect the same data security policies as the application.

    a user who sees only the India BU in Payables
    -> sees only the India BU in an OTBI analysis

There is no second security model to maintain and no way to reach data through reporting that you cannot reach through the screens. Bolt-on BI tools historically got this wrong, and it is how reporting becomes a data leak.

Choosing the subject area is the skill. There are hundreds, and picking the wrong one produces an analysis that is difficult or impossible to complete.

The "Real Time" suffix marks transactional subject areas. Others are built for specific analytical questions, and combining more than one in a single analysis requires common dimensions — which is the usual reason an analysis will not build.

OTBI against BI Publisher. OTBI for exploration and analysis by a business user. BI Publisher for a pixel-perfect document — an invoice, a statutory form — where the layout is the requirement.

What the interviewer is probing.1. "What is OTBI for?" Probing: the positioning. Stalls: "Reports." Moves up: real-time operational reporting on transactional data through subject areas, without extracting to a warehouse.

2. "How does it differ from BI Publisher?" Probing: the distinction. Stalls: "Nothing." Moves up: OTBI is ad-hoc analysis over a semantic model; BI Publisher produces pixel-perfect formatted documents from a query.

3. "What is the performance caution?" Probing: the practical angle. Stalls: "None." *Moves up:* it queries live transactional tables, so a broad unfiltered analysis competes with users doing actual work.

4. "What limits which data a user sees?" Probing: the security angle. Stalls: "Nothing." Moves up: the same data security that applies in the application, so two users running one analysis legitimately get different results.