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

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more