Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 6 · Reports at scale: scheduling, delivery, performance
Scheduling patterns that survive
Lesson 56 of 177 · 2 min
Pick a schedule that does not collapse when the month ends on a weekend, because it will, twice a year, and nobody will remember why. MONTH-END is the hard one. "Last day of the month" and "first working day" are different dates, and the report that must run after the close cannot be scheduled by date at all — the close finishes when it finishes. Prefer a schedule tied to the working calendar over one tied to a day number, and where the dependency is on a process rather than a date, run it after that process rather than at a time somebody hopes is late enough. DAILY DELTAS are the easy case with one trap: the boundary. A job that sends "yesterday's transactions" needs to agree with the receiving system about what yesterday means, in which time zone, and what happens on the day nobody ran it. Lesson 6…
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 6 · Reports at scale: scheduling, delivery, performance
- 1The scheduler, and what a job really is
- 2Scheduling patterns that survive
- 3Delivery: email, FTP and content server
- 4Knowing a scheduled report failed
- 5Volume: when the extract stops fitting
- 6Incremental extracts and high-water marks
- 7What breaks: the 2am report
- 8Lab briefing · Schedule, deliver, and prove it ran