Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 4 · BI Publisher: data models, templates and bursting
Sub-templates and reuse
Lesson 36 of 177 · 2 min
A sub-template holds the parts that are the same everywhere: the header, the footer, the logo, the address block, the standard terms. One definition, referenced by every report that needs it. THE MAINTENANCE ARGUMENT IS OVERWHELMING AND IT IS ALSO THE WHOLE RISK. Change the logo once and forty documents change — which is the point, and which is also what makes a careless edit forty defects instead of one. Both halves are the same sentence. THE VERSION TRAP: somebody updates a sub-template for one report, tests that report, and publishes. The other thirty-nine were never opened. A change that renders perfectly in a portrait invoice can overflow a landscape statement or push a bank file's first data line down by one. Nothing fails at publish time; the next scheduled run produces the broken output. So keep a list of every report consuming each sub-template, beside the sub-template. It is…
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