Possible Status of Background Jobs

Definition

The status of a background job can signify six different conditions, as explained in the table below.

Job Status	Explanation
Planned	Steps that make up the job have already been defined, but the start condition has not yet been defined.
Released	The job has been fully defined, including a start condition. Without a start condition, a job cannot be released. Only an administrator or a user with appropriate authorizations for background processing can release a job, preventing unauthorized users from running jobs without approval.
Ready	The start condition of a released job has been met. A job scheduler has put the job in line to wait for an available background work process.
Active	The job is currently running. Active jobs can no longer be modified or deleted.
Finished	All steps that make up this job have completed successfully.
Canceled	The job has terminated abnormally. This can happen in two ways: An administrator intentionally terminates a job with Transaction SM37, Job ® Cancel active job A job step contains a program that produces an error, such as: an E or A error message in an ABAP program a failure return code from an external SAPXPG program

Only jobs with status Planned, Released, or Ready can still be modified, unreleased, deleted, or prevented from running.