03. Define Background Jobs

Define Background Jobs

To define a new job, use transaction SM36. From Release 4.6A, you can use the Job Wizard to define new jobs as follows:

Specify job name, class, and optional target server

Define a job step (a step can be an ABAP program, external command, or external program)

Add further steps (if necessary)

Start condition (time or event based)

Complete the definition

The Job Wizard allows you to go back and make changes at any point during the definition process.

The start conditions of a job can be time based or event based.

Time based:

Immediate

At date/time

On a chosen workday (defined as a certain workday per month)

All time-based start conditions can be periodic. That is, a job can be performed at regular, defined time intervals. Days that are not workdays can be treated as exceptions.

Parameter rdisp/btctime specifies the time interval of the job scheduler.

Event based:

After event (optional parameters can be used to further specify events) These can be periodic. That is, the job can be triggered every time the event occurs.

After job (this can depend on the status of the previous job)

At change of operation mode (for example, between day and night)

Parameter rdisp/btcname specifies which application server handles events triggered from within R/3.