Category 3: Preliminary and Subsequent Leg for Each Delivery 

This type of leg determination type can generally be used if a transportation chain is to be illustrated in a shipment document.

For example, multiple trucks leave from different shipping points to take deliveries to a harbor, where they are to be loaded onto the ship. The ship then carries the deliveries to the destination harbor, where they are once again loaded onto multiple trucks to be delivered to different customers. During this process, the system assumes that each delivery is so large that an entire truck is necessary for each one (Full Truckload - FTL).

Only preliminary, main and subsequent legs appear here, as opposed to transportation chains, which use multiple documents (preliminary shipment document(s), main shipment document, subsequent shipment document(s)) to illustrate the process.

If you want depict a transportation chain within a shipment document, you must also accept the limited functions available to you.

The reason: Almost all shipment document functions refer to the document as a whole:

In our example, when the trucks go from their respective shipping points to the harbor, the freight documents should not also contain main leg and subsequent leg information. When you create texts, you would not know if they are supposed to be valid for the preliminary, main or subsequent legs.

In order to avoid such limitations, we would recommend that you denote a transportation chain using multiple shipment documents. You can create these shipment documents almost automatically by using collective processing.

However, if you only want preliminary, main and subsequent legs to show up for documentation purposes, then this is the correct leg determination type.

Procedure for this type of leg determination:

  1. The system assumes that the main leg will be entered manually (here, manually means either entered directly or by way of a route entry)
  2. Hamburg-New York

  3. Now, legs are automatically formed for all existing deliveries from the delivery’s departure point to the main leg’s starting point (which was entered manually).
  4. Shipping point ‘0001’ - Hamburg (for delivery 1),

    Shipping point ‘0001’ - Hamburg (for delivery 2),

    Shipping point ‘0002’ - Hamburg (for delivery 3),.

    Shipping point ‘0002’ - Hamburg (for delivery 4),.

  5. Now the system creates legs from the end point of the main leg (which was entered manually) to the destination point of each delivery.

New York - customer 1 (for delivery 1),

New York - customer 2 (for delivery 2),

New York - customer 2 (for delivery 3),

New York - customer 3 (for delivery 4),

Exception:

If there is no main leg, the system creates direct links between the departure points and the destination points of the delivery.

Shipping point ‘0001’ - customer 1 (for delivery 1),

Shipping point ‘0001’ - customer 2 (for delivery 2),

Shipping point ‘0002’ - customer 2 (for delivery 3),

Shipping point ‘0002’ - customer 3 (for delivery 4),

The legs that were created are filled in with data in accordance with step 6 in Automatic Leg Determination, and border points and load transfer points, as in step 7.

Finally, the system determines which deliveries are assigned to which legs. See also Automatic Assignment of Deliveries.

You have created a shipment document that contains three separate deliveries for a total of 60 tons of a product. Each delivery departs from Chicago and is transported to New York by truck. In New York, all the deliveries are loaded onto a ship and transported to Hamburg. In Hamburg, each delivery is loaded onto a separate truck and transported to the ship-to party in Heidelberg. You specify the New York-Hamburg route in the shipment document header. The system creates a main leg from New York to Hamburg, three preliminary legs from Chicago to New York, and three subsequent legs from Hamburg to Heidelberg.