Background Job Processing What is a background Job in SAP How to schedule the background job in SAP (SM36) What are status of background jobs in SAP What are the Standard jobs in SAP How to schedule standard jobs in SAP Common Background Job Errors & Troubleshooting What is a background Job in SAP Unlike Foreground jobs, Background jobs are non-interactive processes that run behind the normal interactive operations. They run in parallel and do not disturb interactive(foreground) processes and operations. It is scheduled from SM36. You can analyze 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 in 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. How to schedule the background job in SAP (SM36) You can schedule the background job using SM36. Planned or immediate jobs can be scheduled. Step 1) Execute T-code SM36. Step 2) Fill the job name, priority(A/B/C) and the target server. Background jobs once scheduled on a target server run on that server. Main purpose of defining target server is the workload balancing. Step 3) Click on “spool list recipient”. You will get output in your mailbox. You can check email from SBWP. Step 4) Insert your SAP username and click copy button. Step 5) Click Step button to define ABAP program, variant’s details, etc. Step 6) Define program name, variant details. 1. Enter your program name,Variant name in the field. If you have not created variant as per your requirement ,then leave it blank. 2. Press save button. Step 7) Once you schedule the job you will get the following screen. Step 8) Click Start conditions to fill start date, end date, frequency,etc for job. If you do not specify start condition then job will always remain in scheduled status. A job in scheduled status will never run. 1. Click on Date/Time(For periodic jobs). If you click “Immediate” then job will start running right away. But it will not be set as periodic job. It’s like “press and run”. 2. Define job’s start date/time, end date/time. The job will be released only once it meets its Scheduled start date/time. 3. Press periodic values. Step 9) Click on Hourly/Daily/Weekly period to define the frequency of the job as per your requirement.We will select Other Period Step 10) Here you specify the recurring criteria of the job.For example, You can have the Job run after every 5 days from the Start Date. Here we select job to run every 10 minutes Step 11) Click on save button. Step 12) Click on save again. Step 13) Click save again I will explain each start condition you can use then if you require Start Conditions. Immediate: - It will run batch jobs immediately Date/Time:-Specify the date/Time to run the Batch Jobs After Job: - Dependent on other job which should be run After Event:-Dependent on other event which should be run At Operation Mode:- job will run At Operation Mode which we define in RZ04 (Day Or Night) Step 14) Once Job step and start conditions are defined the following window will appear. Step 15) Press save. Step 16) Goto SM37 to know the status of the job. Step 17) Select your criteria for the job which you want to monitor. 1. Put your job name and username who scheduled the job. 2. Select the status of the job. 3. Specify the date range. In our scenario we just specify the end date while keeping From Date Open. Step 18) You will get the following screen. Look at the status, it’s a released means start conditions are met, and the job is in the queue is waiting for background work process to be free. What are status of background jobs in SAP 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 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 desired task is competed without any error. 6. Cancelled:- There are two possibilities for this. Administrator has forcefully cancelled the job or there might be some issue with job. You can investigate this from Job logs. 7. What are the Standard jobs in SAP 8. 9. 10. SAP_CCMS_MONI_BATCH_DP : Internally this job runs 11. RSAL_BATCH_TOOL_DISPATCHING report. This job dispatches monitoring architecture methods 12. 13. SAP_COLLECTOR_FOR_JOBSTATISTIC : Internally this job runs RSBPCOLL report. This job generates run time statistics for background jobs 14. 15. SAP_COLLECTOR_FOR_PERFMONITOR : Internally this job runs RSCOLL00 report. This job collects data for the performance monitor 16. 17. SAP_COLLECTOR_FOR_NONE_R3_STAT : Internally this job runs RSN3_STAT_COLLECTOR report. This job will collect non-abap statistic data (Distributed Statistic Records - DSR) 18. 19. 20. SAP_REORG_ABAP_DUMPS : Internally this job runs RSSNAPDL report. This job cleans up old abap short dumps SAP_REORG_BATCH_INPUT : Internally this job runs RSBDCREO report. This job cleans up old batch input sessions SAP_REORG_JOBS : Internally this job runs RSBTCDEL report. This job cleans up old background jobs SAP_REORG_JOBSTATIC : Internally this job runs RSBPSTDE report. This job cleans up old data from the run time statistics of the jobs SAP_REORG_ORPHANED_JOBLOGS : Internally this job runs RSTS0024 report. This job cleans up orphaned job logs. The logs that cannot be deleted by RSBTCDEL report (i.e SAP_REORG_JOBS), remains as orphans which will be deleted by this job. SAP_REORG_SPOOL : This job internally runs RSPO0041 report. This job deletes old spool data SAP_REORG_XMILOG : This job internally runs RSXMILOGREORG. This job deletes XMI logs SAP_SOAP_RUNTIME_MANAGEMENT : This job internally runs RSWSMANAGEMENT report. This job does the SOAP runtime monitoring SAP_REORG_UPDATERECORDS : This job internally runs RSM13002 report and this deletes old update records How to schedule standard jobs in SAP Goto transaction SM36 and click on standard jobs push button. This displays standard jobs screen. Here select all the jobs and click on default scheduling push button to schedule all of them as per their default schedule. Incase you would like to change the default schedule for each job, it can also be done by selecting each job and defining its start date/time and periodicity in the same screen. Need of scheduling basis standard jobs. Standard jobs are the jobs that should run regularly in the SAP system. These jobs will perform housekeeping like deleting old spool requests (thus avoiding spool overflow), deleting old background jobs/logs/updates/batch input sessions/ABAP short dumps, collecting operating system/database level statistics (used for workload reporting) etc Common Background Job Errors & Troubleshooting 1. User and password Issues (Authentication/ Authorization) user lock, user id expiry, password change, lack of roles etc. 2. File system problems: BTC reads from the file system to update the database. File not opened, or corrupted, file sharing issues, file came with different characters, file not found as well. 3. Variants are not properly defined. 4. Dead locks issue (Lock mechanism congested) 5. Update mechanism failed 6. Table space over flow (ORA-1653; ORA-1654) 7. Table space max extent reached (ORA-1631; ORA-1632) 8. Archive struck (ORA-255; ORA-272) 9. The memory is not sufficient and errors (No Roll Area, PXA (Buffer), Page Errors) 10. Problem in the program and inputs (Indefinite loops like 1/0) 11. Dependent jobs/ events failure 12. Target systems are not available to process the jobs.
Posted on: Fri, 04 Jul 2014 09:38:38 +0000
Trending Topics
Recently Viewed Topics
© 2015