3241131 - F2345 I QA16: WMQF* stuck entries after mass processing of inspection lot decisions

For EWM lot (origin 17), after executing

- mass usage decision in fiori app 'Manage Usage Decisions' (F2345) with function 'Make Quick Usage Decision'
OR
- collective usage decision (UD) in transaction QA16,

• the stock type is not changed for some batches (remains Q4 instead of F2 - for example);
• stuck queue entry is displayed with state RETRY and with message
  "Asynchronous execution of Follow Up Action with Retry logic" / "Command to tRFC/qRFC: Execute LUW again."
  in the 'Message Queue' of transaction /SCWM/MON (Warehouse Management Monitor). The queue name starts with WMQF.
• WMQF* stuck queue entries are shown in transaction SMQ2 in status RETRY referring function module /SCWM/QDECIDED_FUP_PROCESS. However, the queue / LUW can be executed manually without any issues.

Single processing (lot-by-lot) for such EWM storage locations do not lead to the same stuck queue entries, only mass processing seems to be affected.

SCM-EWM-QM, SCM-EWM-QM-FUP, QM-IM-UD, QM-FIO-IM-UD, QM-FIO-IM, QM-FIO, BC-MID-RFC, CA-QIE, Usage decision for inspection lot was successfully made, embedded, QFOA_EWM_LOG_FOLLOW_UP_S4, EWM_A, SAPMHTTP, QRFC:, QRFC, TRFCQIN, RETRYNR, TRFCQIN-RETRYNR, RSTRFCIC, inbound, externally triggered , KBA , SCM-EWM-QM-FUP , Follow-Up Processing , BC-MID-RFC , RFC , QM-IM-UD , Inspection Lot Completion , SCM-EWM-QM , Quality Management , CA-QIE , Quality Inspection Engine , QM-FIO , Fiori apps for Quality Management , QM-FIO-IM , Quality Inspection Fiori application , QM-FIO-IM-UD , Quality Inspection Fiori appl. Usage Decision , Problem