Oracle Form September 10, 2026 hannanmentor@gmail.com 6 min read

Oracle Reports to BI Publisher Migration: Complete Step-by-Step Transition Guide

For more than two decades, Oracle Reports (6i, 9i, 10g, 11g, and 12c) served as the standard reporting and document generation engine for Oracle E-Business Suite and custom Forms applications. However, Oracle has deprecated Oracle Reports, officially designating Oracle BI Publisher (now part of Oracle Analytics Server / Cloud) as the enterprise successor.

Migrating complex enterprise reports—containing multi-query data models, layout triggers, matrix repeaters, formula columns, and barcode generation—can appear daunting. In this comprehensive architectural guide, we establish a structured, phased roadmap to migrate legacy RDF reports to BI Publisher smoothly and securely.

1. Architectural Comparison: Oracle Reports vs. BI Publisher

Understanding the architectural paradigm shift is critical to planning your migration. Oracle Reports tightly coupled data retrieval, business calculations, and visual layout into a single binary file (.rdf). In contrast, BI Publisher strictly adheres to the Model-View-Controller (MVC) separation of concerns:

Capability	Legacy Oracle Reports (.rdf)	Oracle BI Publisher (BIP)
Architecture	Tightly coupled binary (Data + Layout + Triggers)	Decoupled: Data Model (XML) + Layout Template (RTF/Excel/PDF)
Design Tool	Oracle Reports Builder (client GUI)	MS Word (BIP Desktop Add-in) or Web Template Builder
Output Formats	PDF, HTML, PostScript	PDF, Excel (.xlsx), Word (.docx), Interactive HTML, XML, CSV, eText
Delivery Engine	Custom shell scripts, `rwservlet`, email via PL/SQL	Native Delivery Engine (SFTP, Email, Fax, WebDAV, Cloud Storage)

2. Phase 1: Data Model Extraction and Optimization

The first step in migrating an .rdf file is decoupling the SQL queries and business logic from the visual layout. In Oracle Reports, developers frequently utilized Formula Columns, Summary Columns, and Placeholder Columns inside the data model.

In BI Publisher, best practice dictates pushing all mathematical formulas and aggregations into optimized SQL statements or package specifications. This dramatically accelerates execution speed and keeps templates lightweight:

-- Converting Legacy Reports Formula Logic into Pure SQL
SELECT
    i.invoice_id,
    i.customer_id,
    c.customer_name,
    i.invoice_date,
    i.subtotal,
    i.tax_amount,
    (i.subtotal + i.tax_amount) AS total_invoice_amount,
    -- Replacing a legacy PL/SQL formula column with standard DECODE or CASE
    CASE 
        WHEN i.payment_terms = 30 THEN i.invoice_date + 30
        WHEN i.payment_terms = 60 THEN i.invoice_date + 60
        ELSE i.invoice_date
    END AS calculated_due_date
FROM invoices i
JOIN customers c ON i.customer_id = c.customer_id
WHERE i.invoice_date BETWEEN :p_start_date AND :p_end_date;

3. Phase 2: Template Design with Microsoft Word & BIP Desktop

Once the BI Publisher Data Model generates clean sample XML data, designers build the visual presentation using Microsoft Word with the Oracle BI Publisher Desktop Template Builder extension installed:

Load Sample XML: In Microsoft Word, open the BI Publisher tab and click Sample XML. Select the XML output extracted from your newly created Data Model.
Insert Table Wizards: Use the Table/Form wizard to map repetitive groups (e.g., <G_INVOICE_LINES>) to Word tables.
Format Fields: Apply native Microsoft Word styling, corporate fonts, headers, footers, page numbering (e.g., Page X of Y), and logos with native WYSIWYG precision.
Preview & Validate: Generate instant PDF, Excel, and Word previews directly from MS Word before uploading the template to the server.

4. Phase 3: Integrating BI Publisher with Oracle Forms 12c

In legacy systems, Oracle Forms launched reports via RUN_REPORT_OBJECT or WEB.SHOW_DOCUMENT pointing to rwservlet. To invoke BI Publisher from Forms, you can utilize the BI Publisher Web Services API or a standardized PL/SQL package:

-- Trigger BI Publisher Report Execution from Oracle Forms
DECLARE
    v_url VARCHAR2(2000);
BEGIN
    -- Construct direct BI Publisher viewer URL with runtime parameters
    v_url := 'https://bipublisher.company.com/xmlpserver/Sales/InvoiceReport.xdo'
          || '?_xpf=&_xpt=1&_xdo=%2FSales%2FInvoiceReport.xdo'
          || '&_xmode=4&_xt=Invoice_PDF&_xf=pdf'
          || '&p_invoice_id=' || :INVOICE_BLOCK.INVOICE_ID;

    -- Open rendered high-resolution document in user's browser
    WEB.SHOW_DOCUMENT(v_url, '_blank');
END;

5. Migration Checklist & Validation

Pixel-Perfect Alignment: Validate complex legal terms, barcodes (Code 128, QR Code), and signature blocks against legacy outputs.
Character Encoding & Fonts: Ensure corporate font TTF files are installed on the BI Publisher server to prevent font substitution issues in generated PDFs.
Batch Scheduling: Transition legacy cron scripts to the native BI Publisher Enterprise Scheduler for automated nightly bursting and multi-channel distribution.

Previous Next