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

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more

[SAP EWM] Adding custom fields for /SCWM/PACK Screen

If business want to add a custom field to the /SCWM/PACK screen and the requirement is that once business enter value here system will check against the weight in the material master  Step 1 : Structure /SCWM/S_PACK_VIEW_HUHDR need to be appended with the new custom field Step 2 : Then use screen enhancement /SCWM/UI_PACKING /SCWM/EX_WRKC_CHECK_BFR_HU_CMP to include logic specific to validation and updation of the table
Post a Comment
Read more