Route Determination as Part of Cross-Docking 

Use

When you use route determination as part of cross-docking, the system takes into account cross-docking routes (CD routes).

Prerequisites

●      You have defined request types for CD routes in Customizing for SCM Basis under Routing Guide ® Route Determination ® Define Request Types for Routing Guide.

●      You have defined CD routes. Here you have made sure that all the routes involved are suitable for cross-docking, in other words, they have one of the request types defined previously.

Features

The system first searches for possible route sequences in the route network that meet the following conditions:

●      The start location of the request is contained in the first route of the route sequence.

●      The destination location of the request is contained in the last route of the route sequence.

Then it checks each possible route sequence to ascertain whether the attributes of the individual routes agree with the requirements in the request, for example, shipping conditions, weight restrictions, and request type. If a route in a route sequence does not meet these requirements, the system rejects the entire route sequence. The result is a number of route sequences that the system represents as a trip, in other words, a sequence of legs. The difference in comparison with route determination without cross-docking is that the trip covers multiple routes in this case.

The additional steps in route determination take place in the same way as in the case of route determination without cross-docking (see Route Determination).

You can use the Business Add-In (BAdI) Enhancements for Scheduling in Routing Guide (/SCTM/EX_RG_PROCESS_SCHED) to determine alternative durations for the transshipment activities.