3301813 - WMQF* inbound queue stuck after Usage Decision for Insp. Lot

There is a inbound queue at APP Warehouse Monitor named WMQF* after Usage Decision for Insp. Lot.

The error message is "Command to tRFC/qRFC: Execute LUW again."

SAP S/4HANA Cloud System

1. Go to APP Warehouse Monitor -> Tools -> Message Queue
2. Display all the message, find the stuck queue WMQF + Warehouse number + Inspection lot number
3. The error message "Command to tRFC/qRFC: Execute LUW again.", message doesn't change after reprocessing the queue.

Improper customizing for storage type.

The error can be caused by multiple reason, below can only be part of them:

Before checking below causes, have a try to reprocess the stuck queues at Warehouse Monitor -> Tools -> Message Queue.

It is possible that the blocker is gone after business user's daily operation.

 

Cause 1.

Check the Customizing "Maintain Storage Types" -> Putaway Control, there can be limitation of the putaway control.

It is mandatory that the flag "No Mixed Stock Types" is not set for a storage type which is used for QQ to FF postings.

Additionally, there can be decision made for nested HUs is like below.

Stock situation before decision is like:

Storage bin 01-01-01

     HU 3000000001(Highest HU)

           -> HU 3000000002(Sub-HU) Stock type Q

           -> HU 3000000003(Sub-HU) Stock Type Q

The HU 3000000001 is assigned to an inbound delivery delivery, Insp. Lot Summary is set as “One Insp. For Product/Batch and Inbound Delivery”. All the HUs share one inspection lot.

After decision made, the stock is expected to be change from QQ to FF. System do stock type change one by one for the sub-hu. If the flag "No Mixed Stock Types" is set, it is intended there is stuck queue.

 

Cause 2.

The stock to be posted from stock type Q is blocked by open Warehouse Task.

 

Cause 3.

The source bin where the stock at is blocked by stock removal or Physical Inventory Document.

 

Cause 4.

it is possible to check set the checkbox "HU WT" flag at Customizing "Maintain Follow-Up Actions".

 

Cause 5.

The follow-up action putaway cannot find the destination bin. Check the putaway stratergy.

 

Cause 6.

Missing entry at customizing "Define Stock Types" for blocked stock or unrestricted stock.

If they cannot resolve the issue, please raise a case to SAP Support.

/SCWM/QDECIDED_FUP_PROCESS, is_t331-mixcat, No Mixed Stock Types, Storage Type, Storage Bin, Inspection Lot, QA11 , KBA , SCM-EWM-QM-2CL , Quality Management (Public Cloud) , SCM-EWM-WOP , Warehouse Order Processing , Problem

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions