TM-EWM Integration with FO and TU in SAP S/4 Hana
SAP S/4 Hana implementations that include EWM and TM need a certain set up to allow posting an end-to-end process with a sales order, delivery, freight unit, freight order, transportation unit, picking, packing and goods issue. The below step by step guide explains the most critical steps to allow freight order to transportation unit Integration. The below 12 steps summarize what needs to be done:
PICTURE 1 – STEP SUMMARY
PICTURE 2 – Location and packing material assignment
STEP 1 – Go to transaction /SCMTMS/LOC3
STEP 2 – Assign a warehouse and a Logical System to the related shipping point Location (TM tab)
STEP 3- Assign a packign material to the related means of Transport (same as the one in the resource used on the FO).
PICTURE 3 – Activate PPF messages
The TM to EWM Integration is done via an XML message (even in embedded TM and EWM). This means, the XML Framework needs to be set up and the following message type need activation.
STEP 1 – Go to SPPFC , choose /SCWM/SHP_REV and /SCMWM/TU
STEP 2 – activate the below marked messages
PICTURE 4 – Remove scheduling conditions
Scheduling condition check certain pre-requisites before they are executed. This will lead to non-generation of the Messages that you need if you do not remove them. double-click on the item on the Right side and click on “no condition” for each one of the messages.
PICTURE 5 – Configure ewm Integration profile and assign it to the FO type
SPRO -> TM-> Integration -> Define EWM Int Profile
SPRO -> TM – Freight order management – FO type
STEP 1 – Create Integration profile
Make sure to set multiple updates. This avoids that the Fo becoms uneditable after generating the TU.
STEP 2 – Assign Integration profile to the freight order type.
PICTURE 6 – Create carrier/supplier roles
STEP 1 – go to BP and Change to edit mode
STEP 2 – create carrier and supplier role
STEP 3 – this is required to add the carrier to the FO (TM) and receive it in ewm (supplier)
PICTURE 7 – Create Fo and set load plan Status to finalized
STEP 1 – Create the road freight order in TM
Type “edit road freight order” in sap business client or type/n/ui2/flp. Make sure, it has at least a carrier, a vehicle ressource and a freight unit assigned. The freight unit has to have a delivery generated that was distributed to EWM. Else the TU cannot be assigned to the delivery and will not be generated. The ressource have to have a Means of Transport with a package material assigned.
STEP 2 – Set load plan Status to finalized
If all goes well, a XML message is sent and you get the below message:
PICTURE 8 – Check Tu is created
STEP 1 – call transaction /SCWM/TU
Make sure the warehouse is correctly entered and the period for selection is long enough.
You can type the Fo number into TU external number. They are always the same and usually one to one. If you cannot find the TU, you can check in table /SCWM/TUNIT using TU_NUM_EXT. If it is not There. Check SRT_MONI.
PICTURE 9 – Check XML message
STEP 1 – call SRT_MONI
STEP 2 – Enter *LOAD* into interface Name.
PICTURE 10 – Post movements in EWM and Check Fo execution tab
STEP 1 – Tu Generation
Once the TU was generated successfully, the FO Shows Ready for loading on the execution tab.
STEP 2 – Arrival at Checkpoint
Once you have the TU in EWM, post “Arrival at checkpoint” to acknowledge truck arrival. The FO should show “arrival at Destination” on the execution tab.
STEP 3 – Load and Departure from checkpoint
Do picking, packing, load end and departure form checkpoint in ewm. The Fo execution tab should show the events LOAD_END and Departure with the same times as ewm.
These were the summarized steps to set up the TM-EWM integration.
Very Good explanation...
hi Santhosh, thank you for your feedback.
let me mention something that I learned in addition.
if you do not know why the message "location not warehouse relevant" is issued, you can debug by setting a breakpoint into class /SCMTMS/CL_TOR_A_SEND_REQ_LDAP, method CHECK_LDAP_CAN_BE_SENT. The message number is /SCMTMS/TOR_INT. number 159.
Very Useful information. Thanks Petra.
I have one question. I have the scenario you described but inside the Freight Order I also have a container Unit. When I send the message to EWM the system automatically creates 2 TU: the first TU is the container which also contains the delivery assignment and the second TU is the vehicle. Both TUs obviously are related to the same Freight Order. My expectation was to have one single TU with the delivery assigned and also the vehicle resource assigned. it makes no sense to me to have 2 TUs. do you agree? do you know which might be the issue here?
thanks a lot
You are right, no need to create two TUs, but this is standard and I am also looking for the rationale behind this behaviour.
This is related to your Means of Transport customizing in TM.
You need to set up the active MoTr so that check boxes “No capacity” and “No direct load” are selected.
Roberto Nanga Martínez
wow, thanks Roberto I've been looking everywhere for this exact thing
hi Roberto, yes, thanks for this useful addition.
Thanks Petra for the useful and clear steps and screenshots!
thanks a lot for this how to manual. I have tried to process your steps, but at point 7 I still get no XML message. Are there any other presteps to do to get the XML message?
Thanks in advance.
BR Vlatko Nesterovic
yes, the messages have to be setup in PO. The message types are:
these messages types can be viewed in SPROXY and you can find them in the naming area http//sap.com/xi/TMS/Global . They need to be configured in transaction SOAMANAGER.
thanks for the question. This was missing in the step list.
Thanks for this blog!
Thank you for this insightful blog! looking forward to read more from you.
wow, thank you for your detailed explanation.
I have a question how to update EWM Handling units like Small Box-Large Box-Pallets Hierchies to Delivery and FU items of FO.
sholud we reflect same EWM Handling Unit Information to DO Handling Units and FU items ?
can we control Output message of HU information? like.. make top HU output only for DO Handling Unit and FU items.
not sure if I understand the requirement well. But, I try to answer anyway:
If you do NOT use the package builder in TM, you will still see the FU items updated with the package information that you have built in EWM. So, if you make hierarchies in EWM, you should see them in TM.
If you use the package builder in TM and you are in S/4 Hana 2020, you can decide to build packages in TM based on either pack spec or packing instructions (EWM) or tm package builder rules such as product to package assignments.In TM, you can build packages either on the freight unit (early package building) or make the optimizer generate packages (consolidation) or use buttons in the cockpit or in load planning to build packages in the cockpit or within the freight order. When you transfer the freight order to ewm (as explained above) and use "send loading instructions", this will build planned HUs in EWM.
with report /SCWM/TEST_PB, you can test the package building with the product that you may have set up in the pack spec. I just tested it, it is definitely possible to build packages in the tm freight unit based on the ewm pack spec (unified package builder). In the pack spec, there is the possibility to build several levels. so, I would think that this may fulfill your requirement.
to make it work, you need to set up a package builder profile with the option "packspec ticked", then you assign the profile to the freight unit building rule (advanced settings) and choose the option "build hierarchies".
Of course, you can also build hierarchies using the TM package builder and send those to EWM. In this case, you need to assign a package 1 to product 1 and than another package 2 to package 1. this also builds a hierarchy. you can try with /SCWM/TEST_PB in se38 and /SCWM/PB_PKG_ASS.
Wow.. you've answered long time ago..
so sorry to recognize your comments just now.
firstly, thank you for your dedicated support.
I took some notes as below in detail again.
our team're struggling lots of hu & fu items due to WM output message ( LDAP & qRFC )
we have TM-EWM thru. DO/TO integration case(for loading insturction) & just D/O integration.
both of them makes lots of fu items and it affects subsequent documents performances like cost distribution and freight order/book process.
still we're looking for the way to control output messages from EWM to TM.
if possible and there is no side effects, we don't want to get EWM HU info for subsequent documents till freight cost clearance.
for example) 1 do item > batch split 1~2 items ( LIPS/TOR Iitems : 2 lines, VEPO: 0 lines)
> after ewm gi ( LIPS/TOR Iitems : 190~200 lines, VEPO: 190~200 lines)
Freight order or Freight book has 10~20 FU .. so, they'll have around 4000 records.
Any advice would be of great help.
Nice explanation, thanks Petra.
May I know if anyone have the similar stuff for inbound ( unloading instructions) what all status transmits from EWM to TM.
I would expect, it is mainly the same thing. Except you have to use the load plan status "set unload plan status" to finalized. I have used it for returns and it worked.
hope it helps
One more time the nice blog. Congrats!
It is helping me a lot in this moment.
Hugs and regards
Thank you all for taking the time to provide all this friendly feedback.
Thanks a lot Petra!
Its really useful.
Is it the same procedure also applicable for old version? (i.e TM 9.5 integration with EWM 9.5)? Can you please confirm?
yes, I woudl think every thing is the same in TM 9.5 if Tm and Ewm run on the same client.
But in our case, TM and EWM systems are on different clients. Do you think still the same steps would be applicable?
let me try to list the steps for this case:
STEP 1 - configure DTr type (E direct ewm int)
STEP 2 - Configure integration profile and assign to Fo type (int profile 3/3/I)
STEP 3 - Configure Post processing framework (activate TOR_LDAP_CNC, TOR_LDAP_REQ in/SCMTMS/TOR in appl /SCMTMS/TRANSPORTATION)
STEP 4- go to the condition part of the ppf, click on techn details and assign or delte the conditions)
STEP 5 - creater the partner role "carrier" for your carrier in TM and create it in the ewm client too
STEP 6: in ewm client, assign packing material to your means of transport
STEP 7: activate vehicle and tu creation in spro - control parameters for vehicle creation in ewm
STEP 8: in TM, activate detailed messages for your user (SPRO-basic functions - user interface)
STEP 9: check output management for your sd delivery. There has to be TRD0 on your output profile (you will find the xml number in the output processing log if it has generated)
STEP 10: create a warehouse (SPRO- SCM EWM - create warehouse) this may be necessary both in tm and EWM.
STEP 11: assign warehouse to decentralized system (SPRO - int with other components - ewm - additional attributes - assign warehouse to decentralized)
STEP 12: logical systems: in all systems, you have to create a logical system for erp, ewm and tm. (spro - ewm - define logical system)
STEP 13: assign logical system to client (step below the previous in customizing)
STEP 14: assign logical system to the location in /SCMTMS/LOC3 in tm tab.
STEP 15: assign logical systems in spro - TM - Integration - define SLD-Data of business systems (this has to be done both in ewm and tm)
STEP 16: define message types in SOAMANAGER
LAST Step : Test the process
hope it helps. please add to it if something is unclear or needs corrections.
Of course, it is much easier to use tm-ewm on the same client or embedded. Not a recommended scenario. But, sometimes, you cannot avoid it.
Thanks very much Petra for providing detailed steps!
Will test it.
Thanks a lot for the useful information!
I would like to know if you have faced any similar issue in the 7th step as the following;
The integration used to work properly as you described it for about 3 months. Suddenly something we have not identified changed the behaviour of the system and when I set load plan Status to finalized, the system does not send the XML message. As a workaround we found that first we have to set load plan Status to Not Planned and then to set load plan Status to finalized and save so as to sent the XML message.
Do you have any suggestion to get back to the right behaviour?
no, I have not experienced the same behavior on a regular basis. Maybe occasionaly though, I have seen that the xml does not want to generate. The way you solve it is correct "set to planned" and back to "finalized". I suggest, you open an oss incidert with a reproducable example and let sap solve the issue.
Thanks a lot for your answer Petra!
We have opened an incident with SAP and they are analyzing the situation. When we have the solution we share it with you !!
Very informative post. Thanks , Petra
i did this all set up but in TM , all the events ( arrival at destination ,load begin, load end and departure) comes at the same time when I click on departure from checkpoint in EWM.
Can please suggest the setting , so the TM receives the event only when a specific activity is performed in EWM.
Thanks Ms Hunger.
thank you for the great blog.
I have one question regarding the SOAMANAGER setting for decentralized integration TM/EWM.
We always get the error message during the Setup integration scenario that the Service group /SCWM/SRVG_TM_SR used in IS "does not exist in the system xxx". We already deleted the caches from the SOAMANAGER, but it still doesn't work. Do you have any Idea how we can solve the issue?
Thank you Petra for a great blog.
I have followed the steps for TM-EWM integration (sidecar TM 9.6). However, when I try to generate the LDAP, there is an error message. It looks like EWM is expecting the Package ID and Package Type to be sent. The LDAP message keeps failing with error "package Type missing" "Package ID missing".
Could you suggest how to overcome this error please?
Hi Sreeharsha, I remember, there was a way to enter the package id manually. But, if that does not work, please open an incident with a reproducable example to SAP.
Does anyone have experience to integrate FB - Container scenarios with EWM? What could be best option to achieve this as standard LDAP or ASR do not support it.
SAP does supports it, but it creates several TUs , one for the truck and one for the container. Strange ! There is an exit where you can influence the LDAP and suppress the unwanted items. Then, you get one Tu per Container.
Let me know if it works
Hello Petra, Thanks for looking into this and your expert advice.
I have not explored LDAP further as SAP`s future road-map is ASR oriented. As an alternate, we are going to develop new custom program to create container unit after Shipping readiness in EWM.
Thanks & Regards!
Petra Hunger Thank you very much for this post. It is very useful. I have one question, is it possible to have the same integration between Freight Booking and EWM?
not really. the idea is that a truck always has to travel by road to the port. So, the standard scenario is to create one freight order and one freight booking. The freight order is for the road transport and integrates with EWM, the freight booking is for the sea transport and does not integrate.
In reality, there are customers who do not want to use 2 documents. In this case, the optimizer cannot be used and the port data cannot be entered as you need several stages to distinguish end customer and arrival port. Also, freight costs are often based on the ports ( 300€ for a container from Antwerpen to Singapur) plus road freight of 200 € to Antwerp). its easier to handle that when you use road start and end location in the FO and port start and locations in the freight booking.
If they absolutely want only one document, it is recommended to use only the freight order when there is ewm integration and you have to overcome the obstacle that SAP standard does not allow the mode of transport Sea for a freight order. This is a problem especially for customers who only pay the transport to the port and still see this as sea (in comparison to road transport that goes all the way to the customer).
Having said that, if your choice is to use the freight booking, you can use the LDAP exit to arrange the xml. However, if you do such an unusual choice, it could be that you encounter other obstacles on the way.
Hope that helps
Thank you very much for this post. It is very useful. I have the same question, how to handle the integration between Freight Booking and EWM? In this case we have only leg. No FO.
Can someone suggest the best option?
see my reply above.
Thanks for this useful blog. I have done all the setup and in addition followed the steps mentioned as per the OSS note as well. In my case, I am getting the action executed(I could see it in the Output management in the FO) but I do not see any XML generated. I tried to debug /scmtms/cl_ppf_serv_tor_b2~method_call_by_abap and the system is skipping mc_tor_ldap_req. Could you please give some guidance here?
Thanks and Regards,
get your interface team to set up the XML message in the SOAMANAGER. make sure your action is not inactive in ppf (but, that should not be the case if it generates). Then, it must be an issue for the interface team.
hope it helps
Hello Petra, an excellent post and this was the starting point for my team to configure the TM - EWM interface. The solution works well. However, we are running into an issue with the LDAP message for Load end and Departure status where the Freight order contents are being adjusted and it causes cost distribution issues. We are working with SAP support to resolve this issue.
This need to adjust the Freight order with picked units is not our requirement and causes other issues with freight invoicing.
Is there a way to limit the LDAP messages to just sent the load end and departure time stamps without content information? We are on S/4HANA 2020 using embedded EWM - Advanced and embedded TM.