SAP Technical Architecture guide
Background Job Administration
Study SM36 and SM37, background-job steps, start conditions, periodic scheduling, job statuses, logs, spool, and troubleshooting.
Job definition model
A background job combines job attributes, one or more steps, and a start condition. Define jobs with SM36 (or the wizard demonstrated in the PDF), monitor them with SM37, and use RZ01 for the graphical background-processing overview. Background execution shifts suitable work away from dialog processing, but still consumes configured background work processes.
| Concept | Options / states | Recall point |
|---|---|---|
| Step type | ABAP program + variant; external command; external program | A job can have ordered multiple steps |
| Start condition | Immediate; date/time; after job; after event; operation mode | Periodic is recurrence, not proof of execution |
| Scheduled | Definition saved without an executable release | Not yet eligible to run |
| Released | Start condition accepted | Waiting for the condition/scheduler |
| Ready | Condition met and waiting for a background work process | Not yet executing |
| Active | Currently running | Not complete |
| Finished | Execution ended successfully | Still inspect job log/spool for business result |
| Canceled | Execution terminated with an error/cancellation | Inspect job log, step and system evidence |
Definition and troubleshooting workflow
1. In SM36, name the job and set priority/target only when required. 2. Add the correct step: ABAP program plus saved variant, approved external command, or external program. 3. Set the start condition and, for recurrence, explicitly enable Periodic Job and define period values. 4. Release the job. 5. In SM37, filter narrowly and refresh status; inspect the job log, spool, step details and target server. 6. For a canceled or long-running job, correlate timestamps with ST22, SM21, locks, resources and application logs before rescheduling.
Active recall
Test yourself
1. What is the difference between Released, Ready and Active?
Reveal answer
Released has a valid start condition; Ready can run but awaits a work process; Active is executing.
2. Where do input values for an ABAP background report normally come from?
Reveal answer
A saved variant assigned to the ABAP-program step.
3. Why can a periodic job fail repeatedly even though its schedule is correct?
Reveal answer
Recurrence only creates future runs; it does not correct step, authorization, data or resource errors.
Practice this module
This guide maps to 4 questions in the SAP Technical Architecture Top 40 bank.
Open practice