MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 15 · ESS jobs and scheduling

Job sets and dependencies

Lesson 149 of 177 · 2 min

A JOB SET IS NOT THE SAME AS TWO SCHEDULED JOBS, and the difference is the whole lesson. Two scheduled jobs run at their own times and know nothing about each other. Job A at midnight, job B at one o'clock, and B runs whether or not A succeeded — or whether or not A has finished. The gap is a guess about how long A takes, and it is wrong the first month volumes grow. A JOB SET CHAINS THEM. B runs after A, and only if A succeeded. That is a dependency the system enforces rather than a schedule somebody hoped was far enough apart. Use one wherever the second step is meaningless without the first. Load the file then run the import. Run the accounting then run the report. Anywhere you find yourself choosing a gap between two schedules, you want a job set. The trade, stated

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 15 · ESS jobs and scheduling

  1. 1What Enterprise Scheduler does
  2. 2Submitting, monitoring and cancelling
  3. 3Job sets and dependencies
  4. 4Custom ESS jobs for your own reports
  5. 5Parameters, defaults and the date trap
  6. 6Reading a failed request
  7. 7What breaks: the job that stopped running
  8. 8Lab briefing · Register and schedule a job