Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 4 · BI Publisher: data models, templates and bursting
Layout, pagination and the printed page
Lesson 37 of 177 · 2 min
This is the unglamorous half of BI Publisher, and it is the half clients notice. Nobody thanks you for a correct query; everybody sees a total split across two pages. Page breaks belong to the data, not to the paper: a break after each supplier, so one statement never starts halfway down another's last page. That is a property of the group, set in the template, and it is the first thing to configure on any document that repeats. Repeating headers are what make page two readable. A table whose column headings appear once, at the top of page one, is a table nobody can read on page four — and the fix is a table property rather than a manual copy of the header row, which is what people reach for and what falls apart when the data grows. Totals that must appear on the LAST PAGE ONLY are…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 4 · BI Publisher: data models, templates and bursting
- 1What a data model actually isFree preview
- 2SQL data sets: writing the query
- 3Parameters and lists of values
- 4Bursting: one run, many recipients
- 5RTF templates: the practical subset
- 6Excel and eText templates
- 7Sub-templates and reuse
- 8Layout, pagination and the printed page
- 9Localisation: Arabic, dates and numbers
- 10Performance: making a slow report fast
- 11Security in BI Publisher
- 12Scheduling and delivery
- 13What breaks: five BI Publisher failures
- 14Lab briefing · A supplier statement, end to end
