Using Default Route transit time in the Freight Unit scheduling

[Coracini]

Hello TM experts,

One of the TM master data that is frequently used in our customers process is the Default Route. It helps us correctly generate the freight stages when additional stages need to be considered during a freight execution. For example, in an export scenario, if we have to consider road transport to the port of origin, sea freight to the port of destination and also the last road leg to the end customer, it is the default route that helps us specify the correct breakdown of these stages.

One of the features of the Default Route is that we can register the transit time of each stage and during the creation of the transport documents, this time is considered to calculate the departure and arrival dates of each stop. When we use a process coming from a FWO, this use is clearer. However, I often see doubts about how to use this when creating the TOR documents. This blog aims to provide a step-by-step guide on what needs to be configured for this to work. So let's go step by step:

1) Create your default route specifying your transit time:

2) Make your Freight Unit Building Rule consider the application of default route:

3) Here's the golden tip: Just having the transit time registered in the default route does not tell the system the correct way to use it. To do this, we need to create a planning profile with a scheduling strategy to be considered. Here I used the strategy without optimization (VSS_EMBED), calculating the times from the arrival date backwards. Don't forget to register the planning horizon in the selection profile:

4) Add this planning profile to your freight unit configuration. Additionally, enable automatic DDD calculation. When creating a FU where DDD calculation is enabled, the TM checks if there is a default route being used and a registered planning profile to then perform the calculation. If there is no planning profile, it proceeds to call the DDD settings. If it is not configured, it does not perform this calculation:

5) Make the other logistics integration settings so that your document integrates correctly with the TM and uses your created FUBR (The settings may vary if your implementation is embedded or side-car, but they are not the focus of this process).

6) Let's test it!

(Screenshot from internal SAP environments)

Feel free to leave your comments and suggestions.