Stock not transferred from ROD storage location after SMQ2 error solving

[CharlotteH]

We have a SAP S4 set-up with embedded EWM. We have a ROD (received on dock) storage location and an AFS (available for sale) storage location in our EWM. So as long as the putaway warehouse tasks aren't confirmed, the stock remains in the ROD storage location. When we then confirm the warehouse tasks, the stock is moved with a transfer order and movement type 411 automatically to storage location AFS. 

When something goes wrong on the inbound flow, and we need to reprocess an inbound delivery that got stuck in the SMQ2 error queue (note that we solve the error queue, and not just save the LUW to SMQ3!), we experience that our automatic 411 transfer from the ROD storage location to the AFS storage location does not happen anymore. Probably because the warehouse tasks that trigger it, had already been confirmed. 

Does anyone have any experience in how to solve this? 

[Daniil]

Hi Charlotte, I guess it depends on how you solve the error. something queue is disappearing after debugging (from my experience, and if I remember right it was one OSS note about such behavior, not for your case, but generally for SMQ2). communication is asynchronous, so warehouse task is always already confirmed when your Queue in smq2. If it happens without debugger I am not sure how could it be and I would suggest to check for some wired developments or oss notes.

[CharlotteH]

Thanks all for the input. 

I gone for the shortcut and I've did a negative stock correction in the ROD storage location and a positive stock correction in the AFS storage location. Not ideal, but it does have the wanted result. 

[Chris1973]

Hi @CharlotteH @Daniil 

Let us focus on what might help you answer your question.

In my experienced scenario, the stock sat in F1 (ROD) and was not visible in ERP. This meant we could not make use of MIGO or manual 411s. In our case what reliably pushed the stock from ROD to AFS the way it should’ve done was the use of the SCWM-POST. If this scenario keeps repeating itself, I would advice you to look into your Transfer BADI as this might help you automate the missed updates.

@Daniil thank you for your contributions.

Best regards

Chris

[Daniil]

sure, let's focus on solution, could you elaborate solution with transfer BAdi please, @Chris1973 

[Chris1973]

Hi @CharlotteH 

Thanks for your detailed explanation of the scenario.

Your observation is correct. The automatic 411 movement from ROD to AFS which normally triggers upon putaway warehouse task confirmation does not happen again after the delivery is reprocessed in SMQ2, particularly if the warehouse tasks had already been confirmed.

The reason is as follows:

The designated trigger for the 411 movement is tightly linked to the initial warehouse task confirmation event.

Once that confirmation has occurred, reprocessing the inbound queue (LUW in SMQ2) doesn’t retrigger the stock movement logic, as the system considers the physical stock movement already completed.

Here is my suggestion on how to resolve it:

• If the stock is still technically in the ROD location but not reflected in AFS, you can manually post the 411 movement (ROD → AFS) via MB1B or MIGO using movement type 411/E (if relevant for your scenario).
• You may also use the Adjust Stock Posting transaction /SCWM/ADGI to realign stock between EWM and MM if you have inconsistencies after queue reprocessing.
• If this happens frequently, consider implementing a BAdI or enhancement to monitor the state of warehouse tasks and trigger the required movement or follow-up delivery update logic post-SMQ2 reprocessing.

Please note, there may be a relevant SAP Note or fix depending on your release version. If this behaviour is not consistent with expected design, I’d suggest raising an incident under component SCM-EWM-IF-ERP to confirm with SAP if it can be handled more gracefully in newer releases or via a standard BADI.

I hope this helps you solve the issue. I am happy to help if you have further questions.

If you find my response helpful, kindly accept the answer and award a Kudos to this post. Your support is appreciated.

Best regards

Chris

[Daniil]

thanks chatGPT

[CharlotteH]

Hey Chris, doing a manual 411 is not the solution, unless you know how to do a stock transfer from stock type F1 (ROD stock) to F2 (AFS stock), not starting from a SCWM transaction as my F1 stock is not available in EWM yet.