Skip to main content

Perform TO reversal when quant is disturbed

This is the common issue faced by most of the business users as business try to perform reversal than in LT0G item will be locked status as the existing quant was disturbed.

In this scenario, we can we use the below process steps to fix this issue.

Below are the process steps to fix this issue per recommendations by SAP.
  •  Use transaction LT01 to manually create a TO and move the stock back into the warehouse.
  • The delivery is not updated when LT01 is used so the pick quantities need to be reset to 0. To do this, change the delivery quantity to 0 and then copy the delivery quantity as pick quantity (Menu path Edit -> Copy pack quantity as delivery quantity).
  • Once the pick quantity has been reset to 0, the delivery quantity can be changed back to its original value or the item can be deleted if it is no longer required.
  • Report RVDELSTA can be executed to update the delivery WM and picking status.

Change Delivery Quantity to '0' without performing changes at  message control level ( SAP Note - 2332285 - Error VL870 in VL02N )

In order to allow further processing/deletion of the delivery, there is a workaround available. You could temporarily change the item category customizing:

In transaction 0VLP, select the delivery's item category (this can be found on the delivery line item in VL02N).
Change the "Check quantity 0" setting to allow 0 quantities. Setting 'B' raises error VL870, therefore change the setting to 'A' or blank instead. Save.
Then, in transaction VL02N, choose the option Edit> Copy Pack Quantities as Dlv. Quantities. Error VL870 should not be raised now.

This will set the delivery quantity to zero, and allow further processing/deletion of the delivery. Remember to revert the temporary customizing change.

Thank you.

Comments

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