Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 4 · BI Publisher: data models, templates and bursting
Scheduling and delivery
Lesson 41 of 177 · 2 min
A report that must run nightly is three separate things: a schedule, a delivery, and a way of knowing it failed. Most people build the first two. The schedule is an ESS job — Module 15 covers the scheduler properly — and the decisions are frequency, the time, and what happens if the previous run is still going. Run it after the data it reports on is complete, which for anything month-end means after the close process rather than at midnight on the first. Delivery has three common channels and each fails differently. EMAIL fails per recipient: a wrong address bounces, and the job still reports success. FTP or SFTP fails on the destination being unavailable, on a credential that expired, or on a permission — and a file half-written is worse than no file, because the receiving system may read it. THE CONTENT SERVER is the safest because it…
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