Reportingintermediate

BI Publisher Data Models and Sub-Templates

Understand advanced BI Publisher data model techniques including multiple data sets, bursting, and reusable sub-templates

A single BI Publisher data model can combine multiple data sets — separate named queries (SQL, PL/SQL, or even a mix of a SQL query and a web service call) — linked together through defined data links (parent-child relationships based on matching key columns), enabling a single report to pull from genuinely different sources and structure them hierarchically in the output XML without requiring a single monolithic SQL join.

Bursting is like a printing press that produces one big run of personalized letters and then automatically stuffs and addresses individual envelopes to each recipient, rather than a person collating and manually mailing each all letter one at a time. Sub-templates are like a company's standard letterhead stationery reused across every document type instead of redesigning the letterhead for each new form.

Key Concepts

1
Bursting is a powerful BI Publisher capability that splits a single data model execution into multiple separate output documents, each delivered differently — for example, running one invoice data model but automatically generating and emailing an individual PDF invoice to each customer's specific email address, all from one report execution rather than one-report-per-customer manual submissions. Bursting definitions specify the split key, the delivery channel (email, fax, print, FTP), and per-recipient parameters.
Bursting
2
Sub-templates allow common formatting elements (a standard company letterhead, a reusable footer with legal text, a standard formatting macro) to be defined once and referenced from multiple parent templates, avoiding duplicated template maintenance across dozens of reports that all need the same branding elements — directly analogous to how developers use shared code libraries to avoid duplication.
Sub-templates
3
Interviewers frequently test whether a candidate can describe how they'd design a report that automatically emails each customer their own invoice PDF (the classic bursting scenario), and how they'd structure a data model with multiple linked data sets rather than one giant query.