0% found this document useful (0 votes)
24 views2 pages

Background Job

The document discusses background jobs in SAP, including how to create and schedule them using transaction codes SE38, SM36, and SM37. Background jobs run non-interactively and in parallel for automated processing. They are classified into high, medium, and low priority and can have statuses like scheduled, released, ready, active, finished, and cancelled.

Uploaded by

Pawan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views2 pages

Background Job

The document discusses background jobs in SAP, including how to create and schedule them using transaction codes SE38, SM36, and SM37. Background jobs run non-interactively and in parallel for automated processing. They are classified into high, medium, and low priority and can have statuses like scheduled, released, ready, active, finished, and cancelled.

Uploaded by

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

BACKGROUNG JOB

Background job:

There is a non-interactive process that runs behind interactive tasks. Processes and operations run
parallel without interfering with each other.

Tcode for background processing:

1. SE38 – Create Variant for Background job


2. SM36- Schedule the job
3. SM37- Monitor the job

Advantages of background jobs:

1. By automating the process, the manual effort is reduced.


2. It can be scheduled according to the preferences of the user.
3. The program can be run in the background seamlessly without requiring user interaction.
4. Once the variant for background job has been defined, the user does not need to worry about
value input.
5. When system load is low, it is ideal for time-consuming, intensive programs.

Background jobs are classified into three priorities:

1. Class A (High priority)- Some tasks are urgent and must be scheduled with class A priority.
2. Class B (medium priority)- Once class A job 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.

Status of background jobs:

1. Scheduled -
You have defined the program name and variant, but not the start parameters such as start and
end dates, frequency or duration. That means you haven't defined when a job should be
scheduled in the system.
2. Released -
All conditions for a job definition's start are met and the job is ready for release
3. Ready -
A background workprocess meets all requirements, but the scheduler has put the job in the
queue because it is waiting for background workprocess to be available
4. Active -
The job has started running in the background. When the job is in active status, we cannot
change its status
5. Finished -
When a job is executed successfully, it means that the task has been completed without any
error.

1 By- Miss. Payal Patel


6. Cancelled -
The job has been forcefully canceled by the administrator or there may be an issue with the job

Steps to create and schedule new background job:

1. Tcode SM36
2. Enter job name, Priority of job class, Define specific server (Optional)
3. Enter username  Copy
4. Click on Step button
5. Give program name and Variant Name (if Variant is created)  Save
6. Click start condition ( IF start condition not specified job will always remain in scheduled status)
7. Define job type  a. Immediate Job (Immediate running)
b. Periodic Job (Date/Time)
(Job will be released only it meets scheduled start date/time you can define or scheduled
minutes/hourly/daily/weekly/monthly)
8. Check  Save  Save  Save  once job step and start condition are defined job information
window will be appear  Save

2 By- Miss. Payal Patel

You might also like