EWM SMQ2-Command to tRFC/qRFC: Execute LUW again. for outbound delivery

[ratana_pouy]

Dear Expert,

At the moment, having two warehouses "A" and "B"

After posting MIGO with movement 201 for Warehouse "A", ERP generates an outbound delivery. Outbound delivery is not found in EWM, but getting stuck in SMQ2 with message:

"Command to tRFC/qRFC: Execute LUW again."
I tried to refresh and execute my times, unluckily, it still be there with the same message.

I am wondering that if i did the same process for Warehouse "B", outbound delivery created in EWM as usual. Make me suprise that it works for Warehouse "B"; not warehouse "A".

Any help to solve this would be highly appreciated.

Regards,

RTN

[jw33]

Hi,

sometimes this happened when there is a hidden error message in the queue, you can only see this by debuggin the Queue (SMQ2) and look into the message-log.

• If all protocols are activated check protocols for you User / RFC-User Transaction SLG1
• Check if your SAP-User / RFC-User have enough sap-authorization (Transaction: SU53)
• Check if there is a Dump (ST22)

Hope this helps.

Greetings

Jan

[ratana_pouy]

hi,

there is no specific error message in SLG1, only below message which is not useful:

"System will execute queue for delivery 0080000200 again (RETRY)."

Also, no error log in ST22.

if i did posting goods issue with cost center from EWM, ERP gets well without an error. Except i post movement type 201 from ERP then getting stuck in EWM.

Please kindly advice.

Regards,

RTN

[ewmbee786]

Hi , just refresh this queue after some time , it will be processed.

[naresh_babu08]

Hi RTN,

Check in SM12 for the lock entries pertaining to the document in Queue. Address the lock entries e.g wait for user to exit the transaction and once it is clear from SM12 reprocess the failed queues.

[former_member230160]

Hello,

the message indicates that an other process is locking some required object (e.g. the delivery). The SMQ entry should have status "RETRY".

This is usually resolved automatically next time the RETRY is done.

If it still persists after several minutes please check if you or an other process are locking the product/stock/delivery.

Best regards

Markus