BIP Reports - Chapter 2: Architecture and Components of BI Publisher (BIP)

  

🏗️ Chapter 2: Architecture and Components of BI Publisher (BIP)

✅ 1. Overview of BI Publisher Architecture

Oracle BI Publisher (BIP) follows a modular architecture, which separates data extraction, template layout, and report delivery into distinct components. This offers great flexibility and maintainability.

🔄 Key Architectural Flow:

1. Data Source → 2. Data Model → 3. Layout Template → 4. Report Definition → 5. Report Output

✅ 2. Core Components Explained

🔹 1. Data Model

This is the foundation of any BIP report. It defines where and how data is fetched.

• Sources: SQL queries, Web Services, BI Subject Areas, Excel files

• Components:

  • Data Sets: The actual SQL or source

  • Parameters: Runtime inputs for filtering

  • LOVs (List of Values): For dropdown parameter options

  • Event Triggers: Used for advanced control like bursting

Example: A data model with SQL that fetches employee records based on department.

---

🔹 2. Layout Template

The layout defines how the data will be presented to the user.

• Types of Layouts:

  • RTF (Rich Text Format) – created using MS Word + Template Builder

  • Excel – for matrix or financial reports

  • PDF – for read-only printable reports

  • eText – for flat file outputs (used in bank interfaces)

  • HTML – for browser viewing

• Uses XSL/FO under the hood to transform XML into formatted output.

Templates are stored in the catalog and can be reused or replaced without modifying the logic.

---

🔹 3. Report Definition

This is the final product – it links the Data Model to one or more Layouts.

• Settings:

  • Output formats allowed (PDF, Excel, etc.)

  • Default layout

  • Default output locale and translation

• Report can be previewed, scheduled, or embedded in workflows

You can have multiple layouts per report definition — e.g., one for internal use (Excel), one for customers (PDF).

---

🔹 4. BI Catalog

The BI Catalog is the central storage and organization area.

• Structure:

  • Folders: Shared Folders (global) and My Folders (user-specific)

  • Permissions: Role-based access to reports, templates, and data models

  • Search & Filter: Easily locate reports, templates, and datasets

• Folder Types:

  • Custom folder paths (e.g., /Custom/Human Resources/Reports/)

  • Seeded folders by Oracle (read-only)

---

✅ 3. Visualizing the BI Publisher Workflow

 
[Data Source] → [Data Model]
                        ↓
             [Layout Template (RTF/Excel/etc.)]
                        ↓
                 [Report Definition]
                        ↓
                 [Output Delivery (Email/PDF/etc.)]

---

✅ 4. Practical Example

Use Case: Create a Salary Register Report

Step	Component	Description
SQL Query	Data Model	Fetch salary data by employee ID and department
Template Design	RTF Template	Format using Word – include headers, footer, page numbers
Report Setup	Report Definition	Link model + template, enable PDF output
Folder Path	BI Catalog: /Custom/HR/Pay/	Set security for HR role only

---

✅ 5. Advantages of Modular Design

• Separation of Concerns: Data logic and layout design are independent

• Reusability: One data model, multiple layouts

• Security Control: Fine-grained access to reports and folders

• Faster Development: Easier to maintain and update

---

✅ 6. Summary

Understanding the architecture of BI Publisher is key to designing effective reports. With separate components for data extraction, layout design, and delivery, BIP ensures flexibility, scalability, and control over enterprise reporting in Oracle Fusion.

---

---

🔹 Next Steps

• Previous Chapter:   

  Mastering SQL for Oracle Fusion HCM – Chapter 1 : What is SQL? 

• Next Chapter : Mastering SQL for Oracle Fusion HCM – Chapter 3 : Oracle SQL Developer Setup

---