Symptom
After upgrading to SAP S/4HANA 2025, a background ABAP short dump occurs in a two-step stock transport order (STO) scenario when an inbound delivery (IBD) becomes TM-relevant.
This happens in either of two situations:
- SPED output is processed to create the IBD, or
- a non-TM-relevant IBD is changed to become TM-relevant.
Runtime error details:
- Category:
ABAP programming error - Runtime Error:
UNCAUGHT_EXCEPTION - Exception:
/SCMTMS/CX_API_FAULTY_CALL - Program:
/SCMTMS/CL_LE_TM_INTEGRATION==CP - Application Component:
TM-INT-LI-LE
Error analysis section of the dump:
An exception of class "/SCMTMS/CX_API_FAULTY_CALL" occurred. This exception was not caught in procedure "HANDLE_REASSIGN_O2I" "(METHOD)" or propagated by a RAISING clause.
Chain of Exception Objects section:
- Short text:
No FU exists for delivery &1 item &2(where&1is the outbound delivery number) T100_MSGID:/SCMTMS/LOG_INTT100_MSGNO:054
Read more...
Environment
SAP Transportation Management embedded in SAP S/4HANA 2025
Product
Keywords
sped output failed, tm short dump, HANDLE_REASSIGN_O2I, /SCMTMS/LOG_INT 054, /SCMTMS/LOG_INT054, no fu exists for delivery, ibd creation from obd, fu reassignment, embedded ewm, logistics integration, ASR, advanced shipping and receiving, proforma invoice, batch subitems , KBA , TM-INT-LI-LE , Integration with Logistics Execution , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview