Scribd
Upload
107 views

SAP Background Job Processing SM36 - Create, Schedule, Reschedule PDF

Uploaded by

anilvishaka7621
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
107 views

SAP Background Job Processing SM36 - Create, Schedule, Reschedule PDF

Uploaded by

anilvishaka7621
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 15
ou” = SAP Background Job Processing SM36: Create, Schedule, Reschedule What is a 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. Itis scheduled from SM36. You can analyze it from SM37 by viewing its job log. Advantages of Background Jobs * Itreduces 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 workprocess. But job scheduler has put the job in the queue because it is waiting for background workprocess 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 canceled the job or there might be some issue with job. You can investigate this from Job logs How to schedule the background job? You can schedule the background job using SM36, Planned or immediate jobs can be scheduled Step 1) Execute T-code SM36. SAP Easy Access - User | (//cdn.guru99.com/images/sap/2013/03/032013_0839_1.pna) BE > BBZiv4

You might also like