Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 15 · ESS jobs and scheduling
What breaks: the job that stopped running
Lesson 153 of 177 · 2 min
Four failures, and none of them is an error message anybody receives. ONE: A SCHEDULE THAT ENDED. Schedules can have an end date, and a job scheduled for "a year" during implementation stops quietly on its anniversary. Nothing fails; the job simply is not there any more, and the symptom is a file that stopped arriving. TWO: A SUBMITTING USER DISABLED. The schedule runs under the identity of whoever created it. When that person leaves and their account is disabled, their scheduled jobs stop — which is why Module 10's rule about never using a named person's account applies to schedules as much as to integrations. THREE: A JOB SET BLOCKED BY ONE FAILED STEP. Step one fails, steps two and three never run. Correct behaviour, and the reports nobody received are three separate escalations from three teams who do not know they share a cause. Lesson 3. FOUR: A…
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.