Symptom
The inbound delivery 18000xxxx is stuck at warehouse with the following message: "An exception has occurred that was not caught."
Environment
S/4HANA Cloud Public Edition
Reproducing the Issue
- Navigate to transaction /SCWM/MON.
- Enter warehouse number xxxx.
- Go to Tools > Message Queue.
- Select inbound delivery 18000xxxx.
- Re-execute or reset the message for inbound delivery 18000xxxx.
Cause
Checking in app 'ABAP run time error', ABAP runtime error for the same IBD can be seen:
Category: ABAP programming error
Runtime Errors: UNCAUGHT_EXCEPTION
Exception: CX_FATAL_EXCEPTION
The exception is related to the previous exception "CX_MBV_UNDETERMINED_KALNR" that occurred in program "CL_MBV_MATDOC_UTIL============CP", in line 55 of include "CL_MBV_MATDOC_UTIL============CM004".
Search Key words: MSGID in the ABAP runtime error details can see below message:
SY-MSGTY E
SY-MSGID M3
SY-MSGNO 354
The error M3/354 indicates that the valuation type is not maintained for inbound delivery 18000XXXX item with material ( mentioned in the ABAP run time error SY-MSGV3 ).
Resolution
- Verify the valuation type for material (SY-MSGV3) item of inbound delivery 18000xxxx
- Maintain the valuation type for the reported IBD item.
- Reprocess the stuck queue in the warehouse monitor.
Keywords
inbound delivery, warehouse management, inventory management, stuck queue, abap runtime error, uncaught exception, cx_fatal_exception, cx_mbv_undetermined_kalnr, valuation type, material document, sap s/4hana cloud public edition, warehouse WH70, message queue, error M3/354 , KBA , MM-IM-GF-2CL , Basic Functions (Public Cloud) , Problem
SAP Knowledge Base Article - Public