Category 2: Preliminary/Subsequent Leg for Point of Departure/De (SAP Library - Shipping in Series Sales and Distribution)

Category 2: Preliminary/Subsequent Leg for Point of Departure/Destination

This type of leg determination forms a preliminary leg for each point of departure and a subsequent leg for each destination point. It can be used if a transportation chain is to be set up within 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 only one truck is needed between each departure point and destination point (Less Than Truckload - LTL).

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.

Caution

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:

Outputs can only be printed for the entire document, not for individual legs
Handling units can only be created for the entire document, not for individual legs
The same is valid for texts, deadlines in general, etc.

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:

The system assumes that the main leg will be entered manually (here, manually means either entered directly or by way of a route entry)

Example

Hamburg-New York

Now, legs are automatically formed for all existing delivery departure points to the main leg’s starting point (which was entered manually).

Example:

Shipping point ‘0001’ - Hamburg

Shipping point ‘0002’ - Hamburg

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

Example

New York - Customer 1,

New York - Customer 2,

New York - Customer 3,

Exception:

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

Example

Shipping point ‘0001’ - Customer 1,

Shipping point ‘0001’ - Customer 2,

Shipping point ‘0002’ - Customer 3.

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.

Example

You have created a shipment document that contains two deliveries to be dispatched to a ship-to party in Heidelberg. The first delivery is to be loaded in Boston, the second in Chicago. You specify the New York-Rotterdam route in the shipment header. Automatic leg determination creates a main leg from New York to Rotterdam, one preliminary leg from Chicago to New York, a second preliminary leg from Boston to New York, and one subsequent leg from Rotterdam to Heidelberg.

This graphic is explained in the accompanying text