Explain BI Publisher Architecture & Data Model Basics in Oracle BI

BI Publisher and OBIEE Answers solve different problems, and confusing them is the giveaway. The architecture separates data from presentation, and that is the

All topics

29 / 55

Publisherbeginner

BI Publisher Architecture & Data Model Basics

Explain BI Publisher's core architecture — data models, layout templates, and the report engine that merges them — and how it differs from OBIEE Answers.

BI Publisher and OBIEE Answers solve different problems, and confusing them is the giveaway.

The Data Model is like a mail-merge data source (a spreadsheet of names and addresses); the Layout Template is like the letter template with placeholders; BI Publisher is the mail-merge engine that stamps out a perfectly formatted letter for every single row, in whatever format (print, PDF, email) is needed.

Key Concepts

    Answers / Analyses   interactive exploration on a screen.
                         Sort it, filter it, drill into it.
    BI Publisher         a document. An invoice, a payslip, a
                         statutory form, a cheque. Pixel-perfect,
                         printed or filed.

The architecture separates data from presentation, and that is the idea to state first.

    Data Model  -> XML  ->  merged with a Template  ->  output
                                                        PDF, Excel,
                                                        RTF, text

A data model produces XML. Its source can be SQL, an OBIEE subject area, a web service, an Excel file or a PL/SQL procedure returning a ref cursor.

A template formats it. Built in Word (RTF), Excel, or the online layout editor, referencing the XML's element names.

Why the separation is the point. One data model, several templates:

    invoice data model
      -> invoice_customer.rtf    a formatted PDF
      -> invoice_internal.xls    a spreadsheet for finance
      -> invoice_edi.etext       a fixed-width file for a partner

Same query. Change the query once, and all three outputs follow.

And the other direction. A template change — the logo, the wording, a field moved — happens in Word, by whoever owns the document, with no developer and no deployment.

The data model is a tree, not a result set. Because a document is hierarchical — an invoice header with its lines — the XML is nested, and the template loops over it. That is a different mental model from a report that returns rows.

Where BI Publisher runs. Standalone, inside OBIEE and OAC, and embedded in EBS and Fusion. The same engine, which is why templates and data models move between them.

The choice in one line. If a human reads it on a screen and interacts with it, use Answers. If it is printed, filed, emailed as a document, or sent to another system, use BI Publisher.

What the interviewer is probing.1. "What are the parts of a BI Publisher report?" Probing: the foundation. Stalls: "A report." Moves up: a data model producing XML, one or more templates defining layout, and output and delivery settings — separated so each can change independently.

2. "Why is that separation the main selling point?" Probing: the argument. Stalls: "It is tidy." Moves up: one dataset drives PDF, Excel, HTML and text, and a business user can change the template without touching the query.

3. "What data sources can a data model use?" Probing: breadth. Stalls: "SQL." Moves up: SQL, PL/SQL ref cursors, web services, HTTP, Excel and an OBIEE analysis — which is how it reports on non-database sources.

4. "What is the bursting feature for?" Probing: the capability. Stalls: "Splitting." *Moves up:* splitting one run by a key and delivering each part separately, so a thousand customers each get only their own statement.