Product Information
Creation of locations during integration with SAP TM
Dear friends of SAP TM,
In this blog post we already talked about the so-called one time locations and how they are created in SAP TM integration if a deviating delivery address is used in an embedded scenario.
But now, let’s talk about the use case when a location for a ‘regular’ source or destination location is used but not created yet when entering SAP TM integration.
Let’s explain this with the following example:
Assume, we have a sales order to deliver goods from shipping point ‘ZMH1’ and we integrate with SAP TM in an embedded scenario to do the transport planning.
The shipping point has of course been created in the system before creating the sales order:
SAP TM now requires locations to do the transport planning based on its address and other information. Means, source and destination (and possible intermediate stops) have to be represented by an entity of master data object ‘Location’.
Now, we could have created the location of shipping point ‘ZMH1’ upfront with report /SAPAPO/CREATE_LOCATION, but somehow we didn’t and there’s also no need to do so.
During the integration of the sales order with SAP TM, we recognize that the location for the shipping point is still missing and trigger its creation ‘on the fly’:
And indeed, the location of the shipping point has been correctly used as source location in the created freight unit:
The same holds also true for destination locations, of course. And this works similarly for other documents from SD, LE and MM.
I hope this gives a bit more insight. Feel free to comment, I appreciate!
Best regards,
Michael
Hello everyone,
In a former version of this blog post, it was not mentioned, that an embedded integration scenario is described. This has been added, just to avoid any confusion.
Best regards,
Michael
We have similar scenario for Creation of FU but facing issue in one of the cases. It would be really great if you can help.
When Destination Location XXX Exists in Location master it works fine and creates FU with the same Destination Location XXX. But we make changes to Address of XXX in Sales Doc, FU gets created with a newly creation location. and this is not the expected behavior. How this can be fixed.
Hello Soundararajan,
I expect a one time location is created. And this happens every time a change is made to the address in the sales document, or in other words, by entering a document-specific address.
Otherwise transport planning can't be done on the actual address and you surely want to to do transport planning on the intended delivery address.
Best regards,
Michael
Hello Michael,
I have observed a change in the General data tab of Location when I was trying to check for a customer who is on S4 cloud and I saw that for On premise, we had External location and BSG reference and in the cloud system, i see that its not there anymore and it had Reference object, object and object type as shipping point. Is this change common for all embedded TM or is it just for cloud? Just wanted to clarify
Kind Regards,
Kalyan
Hello Kalyan,
This has been changed with this development in TM embedded in SAP S/4HANA on premise version. So it's in respective systems in on premise and public cloud version.
The fields are technically still there but hidden in transaction /SCMTMS/LOC3. In transaction /SAPAPO/LOC3 the fields are still shown.
Best regards,
Michael
Hello Michael,
I have one location SP_XXX that have been created.
Someone has trigger the report /SAPAPO/CREATE_LOCATION, and another location have been created under the name : SP_XXX_01 as a copy of SP_XXX.
I have defined my conditions on the source location and TO Type, to display the execution org and execution group automatically in my FU. The source location that I have defined is SP_XXX.
The issue I'm facing is : as there are 2 same locations : SP_XXX and SP_XXX_01, the source location that is automatically integrated in the FU when I create the OBD is the location SP_XXX_01 whereas it's SP_XXX that is defined in my conditions.
Therefore the Execution Org and Execution group are not displayed automatically in the FU.
Do you know how can we maintained the first source location that have been created when the OBD is replicated to TM in FU ?
Thanks
Best regards,
Sivéane