Scribd
Upload
20 views3 pages

Background Job

Uploaded by

srsatapathy087
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views3 pages

Background Job

Uploaded by

srsatapathy087
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Background Job

Background job is a non-interactive process that runs behind the normal


interactive operations. They run in parallel and do not disturb interactive
(foreground jobs) processes and operations.

It is scheduled from SM36. You can analyse it from SM37 by viewing its job log.

Advantages of Background Jobs

 It reduces manual effort & automates the task.


 It can be scheduled as per user's choice.
 It reduces user interaction and can run seamlessly in the background
without user input
 Once you define the variant for background job, the user doesn't have to
worry about value input in the field. Thus, user confusion is also reduced.
 Ideal for time- consuming/resource intensive programs which can be
scheduled to run in the night (when system load is low).

Background jobs are classified into three categories

1. Class A (High/critical Priority): - Some tasks are urgent or critical and


must be scheduled with class A priority job. Class A priority reserves one
or more background work processes. Users have to decide how many
background work processes should be assigned to Class A priority job.
Suppose a user chooses 2 background work processes for this category
then available background work processes for class B and C = (Total
number of work processes set in operation modes RZ03)- (Background
work processes allowed to class A category).
2. Class B (Medium Priority): - Once Class A jobs are completed; Class B job
will start executing in the background before class C jobs.
3. Class C (Low Priority): -It runs after both class A and class B jobs are
completed.
Possible status of background jobs

1. Scheduled: - You have defined the program name and variant but not
defined start condition like Start Date, End Date, Frequency etc. That
means you have not defined when a job should be scheduled in system.
2. Released: - All required criteria are fulfilled for job definition. Start
condition is must for the job to be in release status.
3. Ready: - All the required conditions are met to run the job in a
background work process. But job scheduler has put the job in the queue
because it is waiting for background work process to be free.
4. Active: - Job has started running in the background. We cannot change
the status of the job once it is in Active status.
5. Finished: - Job is executed successfully. It means the desired task is
competed without any error.
6. Cancelled: - There are two possibilities for this. The Administrator has
forcefully cancelled the job or there might be some issue with job. You
can investigate this from Job logs.

Why Delete Background Job?


Old jobs occupy space on the system. To avoid any inconsistencies within the
system normally we delete the logs. Because if the file system gets full, your SAP
system will crash!

You can delete jobs in two ways: -

1. Multiple jobs at once.


2. Single job deletion.

Delete Multiple Jobs at once

The best way to do this is use report RSBTCDEL2(New version of


RSBTCDEL). Old job logs will be deleted and will not show in the job overview.
spool list recipient

"spool list recipient". You will get output in your mailbox. You can check email
from SBWP.

You might also like