Purpose
Automatic leg determination is an easy-to-use function that simplifies manual leg creation, or even eliminates the need for it. It does not involve optimization algorithms and also has no "geographical intelligence".
Automatic leg determination creates legs using simple rules that determine point of departure and destination as well as some leg data (service agent, shipping type, leg indicator, and shipment cost relevance for the leg).
The result of automatic leg determination is determined by different parameters you have set; this allows you to simulate various business scenarios.
The most important parameter is the type of leg determination, which can have five characteristics. For more information, see
Leg Determination Categories.The following data is taken from the shipment document:
Process Flow
Leg determination is generally executed as follows:
In this case, the system responds with a message.
A delivery can go from shipping point 0001/ loading point 01 to customer 123 unloading point ramp 15. A return goes the opposite way, however. An inbound shipment goes from vendor 456 to plant 0005 to storage location 0004.
Warehouse number and door are also taken into account where necessary.
Places (departure points and destinations of deliveries or of a leg, etc.) are given a unique identification number during leg determination; this number is then used in further processing. See also
You can display the history of a leg on the stage detail screen. For this purpose, select Management in this screen. You can tell which route a leg originated from and whether it was created manually or automatically.
Leg indicator |
Effect |
4 (direct leg) or 5 (return leg) |
The entire shipment process appears in one shipment document. The shipment document is not related to any other shipments. |
1 (preliminary leg) 2 (main leg) or 3 (subsequent leg) |
This shipment is part of a transportation chain that is reflected in multiple shipment documents. |
This information is important because, as in the case of a preliminary leg shipment, for example, the deliveries are not to be delivered directly to the customer, but to another destination where they are then transferred to the main shipment.
A delivery is brought by truck from shipping point 0001 to Hamburg harbor as a preliminary leg shipment. The delivery is loaded onto a ship in Hamburg harbor. The ship then transports the delivery from Hamburg harbor to New York harbor (main leg). The delivery is then transferred once again and is shipped by train to customers in Chicago (subsequent leg).
For the preliminary shipment, the destination is not the customer in Chicago, but Hamburg harbor. A dialog box appears during leg determination that asks you to enter the destination. If the main leg shipment was created beforehand in the system, Hamburg is automatically taken as a default.
If a destination was entered, the original destination is replaced by the new one in all deliveries. If this does not occur, leg determination is terminated.
The same is valid for a subsequent leg shipment (leg indicator value 3 in the shipment header), except that the point of departure for the deliveries is replaced by the destination harbor from the main leg, as an example.
If new legs are involved, the following data is re-determined:
(copied from the shipment header)
(default triggered by the shipment type)
If a preliminary shipment is concerned, the leg also gets this indicator (the same applies to subsequent shipment). If only one leg exists or if the leg links the delivery departure point directly to the destination, the leg is a direct leg. For all other shipments, the following applies:
If leg departure point = delivery departure point, then preliminary leg
If leg destination = delivery destination, then subsequent leg
If both apply = main leg
(copied from the shipment header)
Exception: In leg determination types 2 to 4, the shipping type preliminary leg is copied to preliminary legs and shipping type subsequent leg is copied to subsequent legs. In this case, these two shipping types can be maintained in the shipment header (on the Control tab page) and are suggested from the shipment type.
If no shipment type can be determined for a leg, the shipment type is not created. This characteristic can be used to better illustrate certain scenarios (for example, it could make sense to give the subsequent legs lower priority in the shipment since they are not important).
There are two existing legs from A to G and from G to B. The border crossing point G is placed between the two legs.
Step 8 is the only step carried out during leg determination of type 0. This means that no legs at all are determined. This may be useful if you want to enter all legs manually (if a scenario is very complicated, for example), but an automatic assignment of deliveries to stages should occur at the very least.
If the standard leg determination does not meet your needs, you can activate a customer enhancement (enhancement V56SLDET), in which you can create your own leg determination.
See also:
Automatic Assignment of Deliveries
Identification of Places Leg Determination Categories Executing Automatic Leg Determination