Processing RFC Queues errors on EWM SAP Public Cloud

[#1]

Hi,

I am trying to reprocess the Qrfc on SAP EWM Public Cloud, but I couldn't do it. I found this solved topic : Solved: Handling RFC Queue Errors in SAP EWM Public Cloud - SAP Community which say I have to contact SAP Support. I went into the tile Dashboard Messages, I found no queues to reprocess. I adjusted the quantity to 0 on EWM side and the client want to have it on S4 side but it's stuck. When I try to reprocess it directly on the monitor  I have this message : 

Command to tRFC/qRFC: Execute LUW again for queue DLWS0M8E6E4   0080000423.

Message no. /SCWM/MONITOR064

How can I successfully reprocess it ? 

Thank you very much for your help !

[HenrikeGroetecke]

Hello,

Thank you very much for your question. Here's the AI-generated response. Please check whether it helps you resolve the issue.

Kind regards,

Henrike

Joule Response

Reprocessing qRFC in SAP EWM Public Cloud

Issue Summary

You have a stuck qRFC queue (DLWS0M8E6E4 0080000423) in SAP EWM Public Cloud with the error:

Command to tRFC/qRFC: Execute LUW again — Message no. /SCWM/MONITOR064

This message is classified by SAP as "self-explanatory," but in practice it does not reveal the underlying root cause directly. The real error is often hidden behind this generic status, and the queue remains in RETRY state. [1]

---

Resolution Steps

Step 1: Verify Queue Status via Dashboard Messages Tile

Since you found no queues in the Dashboard Messages tile, the queue may not be surfacing there due to how Public Cloud exposes qRFC errors. Instead, navigate directly to the Warehouse Monitor:

• Go to /SCWM/MON → Tools → Message Queue
• Locate the stuck queue (DLWS* prefix)
• Check the error status and attempt reprocessing from there [2]

Step 2: Attempt Debug LUW in the Monitor

Per SAP KBA 3555285, the "Execute LUW again" message can sometimes appear because the application log is too large to display — not necessarily because there is a real blocking error. The recommended action is: [3]

1. Click the Debug LUW button on the stuck queue
2. Press F8 to execute
3. If no error appears during execution, the queue may actually process successfully
4. If an error does appear, set a breakpoint on function module /SCWM/TO_CREATE_WHR and check variable lt_bapiret for the actual error detail [3]

Step 3: Check SLG1 Application Log

Even if the queue monitor shows no detail, check transaction SLG1 for application logs around the timestamp of the queue failure. Filter by the queue name or the user ID associated with the stuck queue. This often reveals the true blocking error (e.g., authorization issue, lock conflict, or customizing gap). [4] [5]

Step 4: Check for Authorization Issues (SU53)

A common hidden cause for this error is a missing authorization. After the queue failure, run transaction SU53 with the user that triggered the queue. If a missing authorization object is displayed, assign it and then reprocess the queue. [6]

Step 5: Engage SAP Support

Since you are on SAP EWM Public Cloud, direct queue debugging (e.g., production debug access) is restricted. If the above steps do not resolve the issue: [7] [5]

• Raise a support case under component SCM-EWM-DLP (Delivery Processing) or SCM-EWM-WOP (Warehouse Order Processing), depending on the queue type
• Reference KBA 3258037 (WMDPDO/WMDPDI queues in RETRY with SR053) and KBA 3555285 (WM* queue with "Execute LUW again") in your case
• SAP Support will debug the queue in the production environment to identify the exact root cause [8] [9]

---

Key Considerations

Quantity Adjustment Impact on S/4HANA Sync

• You adjusted the quantity to 0 on the EWM side, but the S/4HANA side has not yet received this update — this is precisely because the qRFC carrying the confirmation is stuck.
• Until the queue is successfully processed (or cleared by SAP Support), the two systems will remain out of sync.
• Do not manually force-delete the queue without SAP Support guidance, as this can cause permanent data inconsistencies between EWM and S/4HANA. [2]

Known Limitation in EWM Public Cloud for qRFC Reprocessing

• In the Public Cloud environment, standard on-premise tools like direct SMQ1/SMQ2 access and production debugging are not available to customers — this is a confirmed constraint, which is why the SAP Community thread you referenced advises contacting SAP Support. [7]
• The Warehouse Monitor (/SCWM/MON → Tools → Message Queue) is the primary self-service tool available in Public Cloud for queue visibility and reprocessing attempts. [2] [10]
• If the queue cannot be reprocessed via the monitor, SAP Support is the required escalation path for Public Cloud environments.

Sources (10)

Web

• [1] Command to tRFC/qRFC: Execute LUW again for queue &1.Web Search: michaelmanagement.com

SAP Resources

• [2] Queue Contents Editing for Failed Queues from EWM to ERPSAP Community
• [3] 3555285 - WM* queue failed with error: "Command to tRFC/qRFC: Execute LUW again"SAP for Me
• [4] Stuck WMQF* queues | SAP Help PortalSAP Help
• [5] 3440931 - Clarification of different error messages in WMQF* stuck queueSAP for Me
• [6] 3361002 - QSLS* queue stuck in Retry, error /SCWM/QINSP203SAP for Me
• [7] Processing RFC Queues errors on EWM SAP Public CloudSAP Community
• [8] 3258037 - WMDPDO or WMDPDI queues in status RETRY - Error SR053 | SAP Knowledge Base ArticleSAP Support User Applications
• [9] 3555285 - WM* queue failed with error: "Command to tRFC/qRFC: Execute LUW again" | SAP Knowledge...SAP Support User Applications
• [10] 3301813 - WMQF* inbound queue stuck after Usage Decision for Insp. LotSAP Support User Applications

[Tazer7]

Thank you very much for your answer !