Skip to main content

[SAP EWM] Error /SCWM/GM034 comes during GI reversal

 Issue :

Product has been posted goods issue (GI) from HU AAAA on storage bin BBBB. The GI reversal is stuck by error:
/SCWM/GM034: You can only post to bin BBBB using a handling unit

Root Cause :

  • During GI cancellation the system tries to post the stock back into the same HU (which has been deleted in the meantime). If this HU no longer exists, it will try to post as unpacked stock to the same bin. However, this can be prevented by error /SCWM/GM034 in case of HUs are obligatory in that storage type and the GI happened by a product warehouse task (WT).
  • Consider also it is not possible to cancel the goods movement and post the stock to a different HU.
Solution Approach :

In case the GI posting was done by a HU WT, then system re-creates automatically the HU posted for GI.

In case the GI posting was done by a product WT there are two options:

Option A)
Change the storage type settings regarding HU requirement to value ' ' (HU allowed but not a requirement) and re-try the reverse GI posting. It can be done in the customizing via transaction SPRO - SCM Extended Warehouse Management - Master Data - Define Storage Type - field "HU Requirement".

Option B)
Re-create manually the HU AAAA on bin BBBB as an empty HU. When you re-create the GI posted HU as an empty one, pay attention to enter the desired HU number in the HU field, otherwise the number will come from the number range. Then the posting will work as expected.

In case of you have huge number of HUs in GI warehouse tasks. The only option to reverse this ADGI GI posting is to upload the stocks again via /SCWM/ISU. Please create a CSV file for the upload based on the content of GI WT. You have to add one extra line per HU with the packaging material of the HU, so that the HU can be recreated.

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