Dialog work processes are intended for dialog processing. For this reason, the duration of a dialog step is limited. Background processing is intended for operations that require a longer time to run.
Background processing is also suitable for activities that are scheduled to run regularly.
A background job consists of one or more steps.
An ABAP program
An external command
An external program
Each job is processed without interruption by a single background work process.
Types of background jobs: Background jobs can be classified into six types. i.e.
Class A: with/without target server
Class B: with/without target server
Class C: with /without target server
Class A: These are the high priority jobs which can be scheduled according to
User request . Eg;- payroll run, daily,weekly, monthly reports etc.
In order to execute class A jobs we need a dedicate background
Work process of type A ( needs to be defined while configuring
Operation mode)
Class B: Standard jobs/housekeeping jobs like SAP_Collector_for_performance
SAP_REORG_SPOOL etc.
Class C: Low priority jobs
To define a new job, use transaction SM36, 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.
Background processing is also suitable for activities that are scheduled to run regularly.
A background job consists of one or more steps.
An ABAP program
An external command
An external program
Each job is processed without interruption by a single background work process.
Types of background jobs: Background jobs can be classified into six types. i.e.
Class A: with/without target server
Class B: with/without target server
Class C: with /without target server
Class A: These are the high priority jobs which can be scheduled according to
User request . Eg;- payroll run, daily,weekly, monthly reports etc.
In order to execute class A jobs we need a dedicate background
Work process of type A ( needs to be defined while configuring
Operation mode)
Class B: Standard jobs/housekeeping jobs like SAP_Collector_for_performance
SAP_REORG_SPOOL etc.
Class C: Low priority jobs
To define a new job, use transaction SM36, 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.
A job step can be any one of the following.
ABAP program
External command
External program
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.
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)
Status of Jobs
The job status can be any of the following:
Scheduled: job is created but has no start condition
Released: job is completely defined and waiting for selection
Ready: job has been selected for execution
Active: job is being executed by a background work process
Finished: the entire job has been successfully executed
Canceled: job terminated with problems
As long as a job has status scheduled or released, it can still be changed.
If execution of a job has already started, its progress can be monitored in the job log. If the job contains ABAP programs, their output is stored in spool lists.
To create the steps of a new job from an existing job, choose Copy.
Scheduled: job is created but has no start condition
Released: job is completely defined and waiting for selection
Ready: job has been selected for execution
Active: job is being executed by a background work process
Finished: the entire job has been successfully executed
Canceled: job terminated with problems
As long as a job has status scheduled or released, it can still be changed.
If execution of a job has already started, its progress can be monitored in the job log. If the job contains ABAP programs, their output is stored in spool lists.
To create the steps of a new job from an existing job, choose Copy.
To monitor jobs, call transaction SM37.
From the job overview, you can navigate to various detailed job-related views:
The job log enables you to monitor the progress of a job.
The spool list contains the output of ABAP programs, if any.
Job details include the job definition, execution time, and background work process number.
No comments:
Post a Comment