3685139 - Explicit setting of check-out milestone required for freight order execution in SAP S/4HANA Cloud Public Edition

• In the Manage Freight Order app: when attempting to add the "Set to Departed" event at the destination stage, receive the error message no. SCMTMS/TOR_EV_PROC026: "Event checkout must be reported manually or via a service and can't be derived".
• This issue does not occur if set the status to 'Checked Out/Departed' at the source location, then set it to 'Arrived/departed' at the destination location. 

SAP S/4HANA Cloud Public Edition

The latest delivery requires the explicit setting of the Check-Out milestone. Previously, the Check-Out would be implicitly set when marking 'Arrival' at the destination. Given the significance of the Check-Out milestone, it is necessary to set it explicitly. This ensures that uses are fully aware of the subsequent processes triggered by the Check-Out action:

• Transition to freight cost confirmation
• Printing of transportation documents
• Dispatch of the advanced shipping notification for the consignment order

For additional details, refer to the Freight Order Management documentation. 

To automate this step, there is option to utilize Local (C1) APIs or External (C2) APIs. Further information is available here: Freight Order Event.

• Freight Order Management documentation
• Freight Order Event documentation

freight order, check-out milestone, transportation management, load unload app, departure issue, explicit check-out, SAP S/4HANA Cloud Public Edition, freight cost confirmation, transportation documents, advanced shipping notification, TM FO , KBA , TM-FRM-FRO-2CL , Freight Order (Public Cloud) , Problem