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

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] 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

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