Multiple freight orders to a single transportation unit

[maxime_malvache]

Hello SAP Gurus,

I have a question regarding the TM-EWM integration.
In a regular process a freight order is created and it generates the creation of a transportation unit in EWM via LDAP message. (relation 1 to 1 between FO and TU).

We have a requirement to create 1 Freight Order per day, per O-D pair, per PRO#. This design is created to meet EDI210 requirement where carrier invoice is sent to shipper based on PRO#.

However, in EWM a single transportation unit representing the actual truck is needed, and we have multiple ship-to/PRO# within this TU.

The challenge with this approach is that we would have a relationhip of multiple freight orders to a single transportation unit.

We still want to have a communication between EWM and TM - we want to update the loading start, loading end, departure and other changes if required – so having no synchronization between TM and EWM does not seem to be an option.

What would you recommend in this scenario where multiple FO needs to be represented by a single transportation unit?

It seems that an enhancement on both the inbound and outbound LDAP would be a good approach - but I am looking for feedbacks/suggestions.

SAP version: SAP S/4 HANA 1909 with embedded EWM

Many thanks!

Maxime

[hanna_siefert]

Hi Maxime,

If I understand correctly, you

- need a TU per truck in EWM

- you want to settle costs on a daily basis

- you want to have TM-EWM integration working

Do you really have the requirement to just have 1FO per day, or would it be suitable to have 1 FSD per day, so you bundle the FOs for the day in a FSD and might trigger the EDI message EDI210 from the FSD. To which webservice you want to map the EDI210 to?

Regards, Hanna

[maxime_malvache]

Hello Hanna,

Many thanks for your message.
We indeed want one TU per truck in EWM and want to have the TM-EWM integration working. Planning must be done within TM.

However, regarding EDI 210, the main requirement is to match the incoming EDI 210 (carrier invoice by PRO#), and not only by day.

Hence, we can potentially have 2 PRO#s that can result in 2 invoices in the same day. We will use InvoiceRequest_In. This will go to TM and not to Finance.

I will explain the 2 options we see to meet the above requirements:

Our first option is to build these LTL trailers in TM and to use star shaped schema freight orders (1 FO = actual truck in this scenario).
One stage contains multiple requirement documents; each stage creates an FSD. In this case EDI 210 needs to be matched against the charges at freight order stage level. This is our first complexity.

With this approach we would still have additional constraints: The star shaped schema can only be generated out of DSO options. This covers all scenario but in case there is a transshipment location to be determined, VSR optimizer needs to run and will not result in a star shaped schema freight order. In addition, if we choose star shaped schema freight order, new order added to the freight order (because the truck still has available capacity) will result in new stages, and not adding to existing ones (in case there was already a stage for the same destination), resulting in double freight calculation.

Considering these challenges, our second option is to not use star shaped schema.
In this 2^nd option we would create one 1 Freight Order per day, per O-D pair, per PRO# in TM.
An enhancement will be required to do the planning within TM (each FO will have a field, might be groupid, that represents the actual truck). With this option multiple FOs will have the same truck indentifiation.
With this kind of design we need to enhance the EWM-TM integration via the LDAP messages. Multiple FOs must be linked to a single TU (based on the field with the truck identifcation).

Hopefully this clarifies the requirements,

Maxime

[gaurav_jain27]

HI Maxime,

[gaurav_jain27]

HI Maxime, How did you finally manage to achieve this. Kindly through some light on the final solution.