SAP Knowledge Base Article - Preview

3829687 - Duplicate one-time locations for parallel Delivery messages from ERP

Symptom

  • Two different one-time locations are created in SAP Transportation Management (TM) for the same ship-to address when Delivery messages are received at almost the same time.
  • The two inbound messages IntracompanyTransportationRequestRequest_In contain the identical one-time address.
  • Both messages create a Delivery-based Transportation Request and a Freight Unit, and each Freight Unit ends up with its own one-time location instead of sharing one.
  • The issue happens mostly when Deliveries are created in mass in ERP, so that the messages reach TM within the same second or very close to each other.
  • Redundant one-time locations are created in the system.


Read more...

Environment

SAP Transportation Management embedded in SAP S/4HANA 1709 and above releases.

Product

SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023 ; SAP S/4HANA 2025 ; SAP Transportation Management all versions

Keywords

one-time location, duplicate one-time location, two one-time locations, redundant one-time location, one time address, IntracompanyTransportationRequestRequest_In, Delivery-based Transportation Request, DTR, Freight Unit, FU, Freight Order, multiple stages, consolidation, mass Delivery creation, parallel processing, queue name, serialized queue, outbound queue, ERP TM integration, BAdI, same address, location not reused, race condition, ship-to , KBA , TM-INT-LI-CS-DTR , Delivery-Based Transportation Requirement , LO-INT-TM-DL , Delivery Processing , Problem

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.