Skip to main content

[SAP MM] Error VLA317 or VLA318 given while posting Goods Receipt via MIGO transaction

Below is the solution approach for the following error messages :

  • Batch Error VLA317 during Goods Receipt using Inbound Delivery 
  • Error VLA317 'Inbound delivery batch cannot be changed to &1 here' is reported 
  • Error VLA318 'Inbound delivery valuation type cannot be changed to &1 here' is reported 
  • Error VLA319 Return delivery qty greater than previously GR-posted qty: &1/&2 when reversing a delivery GR is not happening with reference to Inbound Delivery
Solution Approach

Options for Resolution: 

Approach 1 : Update the Inbound Delivery with the Batch Number (LIPS-CHARG)/Valuation Type (LIPS-BWTAR) prior to posting the Goods Receipt via MIGO transaction. 

Approach 2 : Implement Note 2991640 and then the error VLA317/VLA318 can be customized as a warning.

Please be aware that this may cause inconsistencies so review all the information provided in this note. Run transaction SPRO (or OVM1) and follow the path: Logistics Execution -> Shipping -> System Modifications -> Specify Characteristics for System Messages

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