Skip to main content

Avoiding background job overruns - SAP

Commonly, We schedule background job for every 5 min or so on periodically depends on the functionality of the program and data updates required. In this situation,there might be a situation where previous background job still continue to run even after next schedule due to data or some other reason.

This will make two jobs of same program run parallel and might create locking or performance issues. To avoid such situation, We can add a step to the existing background job prior to the step of the actual program.

The below mentioned program should run prior to the actual program execution.  This program will check and cancel the subsequent job of the next run if the program still runs before next execution.

Program Name - RSBTONEJOB

Note that the variant of this program should be maintained with same name as that batch Job name.




Comments

  1. CLARANCE MULLIANS7 October 2020 at 17:32

    whoah this blog is great i really like studying your posts. Keep up the good work! You understand, many persons are searching round for this information, you could help them greatly.
    wwt shipping containers

    ReplyDelete
  2. Newforceltd8 October 2020 at 01:16

    Permanent and Contract IT jobs in Europe | Overseas Job Consultants is a Newforce Global Services is a Uk Based European Staffing and Consulting Firm.

    ReplyDelete

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.
Post a Comment
Read more

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button
Post a Comment
Read more

Stock Inconsistency Reports

Report: RM07KO01 - Stock consistency check between ML and IM Description : With the Stock Consistency Check report (RM07KO01), you can check the consistency of your stock data at company code level, valuation level, or material level. Possible errors in your stocks can thus be determined at an early stage before they cause major problems Transaction Code : CKMC - Consistency check between Material Master and Material Ledger
1 comment
Read more