Skip to Content
Product Information
Author's profile photo Michael Haase

Improved location determination in SAP TM for STO enablement in ASR scenario

Dear friends of SAP TM,

In this blog post we will talk about the integration of stock transport orders (STO) with SAP TM with the special focus on the determination of the source and destination locations.

When integrating any document from SD, LE or MM, we always need respective locations for the source and destination of the transport to enable the transport planning of the created freight unit(s). And this information will obviously be derived from the predecessor document in SD, LE or MM.

For the stock transport orders, the logic for the location determination in TM integration until now was as follows:

  • Source destination: Take the location of the shipping point from the shipping data of the STO (in table EKPV)
  • Destination location: Take the location of the customer as maintained in the STO item. If no customer is provided in the item, take it from the shipping data

Now as our famous Advanced Shipping & Receiving (ASR) came into play, we of course also needed to offer an STO enablement for ASR scenarios. But for that, the location determination for the destination needed to be adapted to enable the ASR functionality in the inbound processing.

Process overview

Let’s explain this be looking at an example of the STO process in ASR:

In detail, the following happens:

  • During creation of the STO, a freight unit is created and the freight unit is planned to a freight document
  • The outbound delivery is created out of the freight document and thereby the freight unit is reassigned to the outbound delivery. Besides, warehouse processing in the outbound happens
  • At next, goods issue is posted at the shipping point, which triggers the creation of the inbound delivery and the freight unit is reassigned to the inbound delivery. Finally, warehouse processing in the inbound happens

But this process can only be enabled for an ASR scenario if the location of the shipping/receiving point is considered as destination of the transport.

See here the comparison of source and destination locations between the default behavior for non-ASR scenarios (why it’s only the default is explained later) and ASR scenarios:

Examples non-ASR & ASR

To show this with examples, we create at first an STO for a non-ASR scenario with its regular location determination:

You see, we transport from a plant in St. Ingbert (and respectively a shipping point which is not ASR relevant) to a customer in Stuttgart.

The created freight unit then looks like this:

So, the destination location is the location of the business partner in Stuttgart.

At next, let’s assume an ASR scenario with an STO for transporting goods from a plant in Berlin to again a plant in Stuttgart:

The plants have respective shipping points assigned, which both are relevant for ASR.

During TM integration, the following freight unit has been created:

You see, that now the respective shipping points have been determined, also for the destination location.

And for the sake of completeness, the final document flow of this STO looks like this:

Further enhancements

Thereby it’s worth to mention that we made another improvement regarding the location determination. If the receiving storage location of a purchase order or purchasing scheduling agreement has an own address, until now we created a one time location. In the context of the ASR inbound process, we now consider also the assigned shipping point as destination location.

The above improvements are now the standard behavior in the context of ASR. As this improvement might also be interesting in non-ASR scenarios, we have added the following customizing setting to the logistics integration profile to enable this also for non-ASR:

The default here is that for non-ASR scenarios, the above functionality is switched off, staying compatible with the behavior until now, but can be switched on easily. It’s just important that existing freight units are not adapted after setting or unsetting this flag so this affects only newly created freight units.

The described functionality is available with SAP S/4HANA 2022 FPS1 and note 3261189.

Thanks for your interest in this topic! I’m happy to discuss your remarks!

Best regards,


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Hernan Suarez
      Hernan Suarez

      Hi Michael. Thank you very much for this new functionality. Excellent explanation and documentation!.

      Could you please explain in more detail what is the logic to the location destination determination in a non-ASR scenario because when create an purchase order they system always create a one-location even though the storage location of the destination plan has not configured any own address. Even though the location for the destinatio plant was created by create-location standard report of TM, the systems continue to create a one-time location. Also, there is no change of address or something similar in the address tab of purchase order item. How can I avoid the creaton of one-time location in inbound transport deriving from purchase order, STO or inbound deliveries?

      Thank you very much and kind regards!

      Author's profile photo Michael Haase
      Michael Haase
      Blog Post Author

      Hi Hernan,

      Thanks for your nice feedback, I appreciate!

      Regarding your question, please check the following blog post explaining details about one time locations and when they are created:

      So I would assume this systems setting explained there is active in your system, causing the creation of those one time locations.

      Best regards,



      Author's profile photo Christoph Greil
      Christoph Greil

      Hi Michael Haase ,


      first of all, thanks a lot for this great blog!

      Will this new location determination and freight unit reassignment to inbound delivery be part of the basic shipping scope?


      Thank you!


      Best Regards,






      Author's profile photo Michael Haase
      Michael Haase
      Blog Post Author

      Hi Christoph,

      Thanks for your feedback!

      Basically, this improvement is not treated as new functionality but still a part of the STO integration.

      Referring to note 3065464, STO integration seems to be part of the advanced scope and not in basic shipping.

      Best regards,


      Author's profile photo Cédric NIKAES
      Cédric NIKAES

      Dear Michael,


      Thanks for this explanation.

      I understand that this logic of determining a shipping point for the destination location in STO scenario (based on MM plant/storage location) is by default active in ASR context and that here, you "only" offer the possibility by customizing, to also enable this behavior for TM-EWM integration based on TU, and that seems clear to me.

      My concern is regarding the E2E process for STO management, with both source and destination location managed in ASR and linked to two different EWM warehouses in an S/4HANA 2022 (Initial Shipment Stack) system (fully embedded)


      Step 1 : STO Creation

      At the moment, when creating the STO, the FU is well created in TM but I have a small difference with your screenshots.

      Indeed, only the source location has managed to determine a warehouse sub stop (loading point) and not the destination location (it seems that in your screenshot, you have a hierarchy here and thus, I assume that the unloading warehouse stop has been defined as a sub stop)


      Step 2 : Outbound Delivery creation

      Then I create the outbound delivery (from TM freight order) on supplying plant side, my FU is well updated and now, the unloading point / warehouse sub stop is created. System finds the WM warehouse connected to plant/storage location, but here, system does not manage to map the WM warehouse to the EWM warehouse.


      Step 3 : GI posting and inbound delivery creation

      When the GI is posted, SPED output is raised and the inbound delivery is created on receiving plant side. This works well.

      Nevertheless, the document flow of the freight unit is not updated with the inbound delivery document as shown in your screenshot.


      Please also note that I would like to avoid using TM integration based on order, but only on delivery and thus, the first moment when the FU will be created is at outbound delivery creation on supplier side ? In such scenario, will the document flow be updated also with the inbound delivery ?


      I'm looking here for information about the target process that you are working on with ASR in STO scenario and clear vision about what is included in S/4 HANA versions, starting with S/4 HANA 2022 initial shipment stack.


      Thanks a lot for your help !



      Author's profile photo Jacob Zimmerman
      Jacob Zimmerman

      "Nevertheless, the document flow of the freight unit is not updated with the inbound delivery document as shown in your screenshot."


      I'm having the same issue as well. Any tips?