3832459 - Freight Booking container number not updated by TransportationOrderGenericRequest_In

• The inbound service TransportationOrderGenericRequest_In with actionCode 02 (Update) and BusinessScope EXTERNAL_PLANNING fails when a container registration number is added to an existing TUR item of a Freight Booking.
• The Update Handler returns the warning "No matching container unit found for registration number &1" (message 067, class /SCMTMS/TOR_ERR_HNDL).
• The processing ends with the error "Processing canceled; data received is not valid" (message 002, class /SCMTMS/INB_AGENT).
• The existing TUR item of the Freight Booking is not changed.
• When the registration number is already maintained manually on the item, the message "changeOrdinalNumberValue not specified in message = : serialization cannot be checked" (message 545, class /SCMTMS/TRQ) can appear as well.

SAP Transportation Management embedded in SAP S/4HANA 2023.

container number, container registration number, TUR item, Container Unit, Freight Booking, ocean booking, TransportationOrderGenericRequest_In, TGI, generic inbound service, Maintain Generic Transportation Order, SPROXY, EXTERNAL_PLANNING, actionCode 02, Update Handler, MS_OMUH_SRV, PLATENUMBER, base_btd_id, container not updated, no matching container unit found, Processing canceled data received is not valid, changeOrdinalNumberValue, local TUR item created, departure status update, assertion failure , KBA , TM-FRM-INT-GEN , Transportation Order Generic Web Services , TM-FRM-UH , Update Handler , Problem