Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VTR (Package) SD R/3 transport processing
Basic Data
| Data Element | LAUFK_TXT |
| Short Description | Leg indicator description |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR15 | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | LegIndDes. |
| Medium | 15 | Leg ind.descr. |
| Long | 20 | Leg indicator descr. |
| Heading | 20 | Leg indicator descr. |
Documentation
Definition
Specifies what kind of shipment leg you are dealing with.
Use
You can use this characteristic to classify the shipment leg for analysis purposes.
The leg indicator is determined internally for legs which are created by automatic leg determination.
Examples
The following leg indicators are can be assigned to shipment legs:
- Preliminary leg:
- A subsequent main leg shipment exists or is required for this shipment.
- Subsequent leg:
- A preceding main leg shipment exists or is required for this shipment.
- Main leg:
- One or more preliminary and subsequent shipment legs are required for this shipment.
- Direct leg:
- No other shipments are linked to this shipment.
- Return leg:
- Means of transport is returning to its base.
Dependencies
The leg indicator at leg level is influenced by the leg indicator in
the header and automatice leg determination:
Explanation of Leg Determination Procedure
During leg determination, the system determines the point of departure and the destination of a delivery on the basis of the leg indicator in the shipment header.
Leg determinaton is initiated when you choose the pushbutton "Leg determination" on the shipment stage overview screen or when the status "Planned" has been set in the shipment header. It is only executed if the respective shipment type has a leg determination type defined in the Implementation Guide.
You will find more information on the exact procedure for leg determination in the online documentation by choosing Shipment --> Shipment Stages --> Basic Information on Automatic Leg Determination.
Example:
In the case of a collective shipment (leg indicator 4, direct leg), the point of departure is the shipping point, and the destination is the ship-to-party. In the case of a preliminary leg shipment (leg indicator 1, preliminary leg), on the other hand, deliveries are not sent to the customer, but to a load transport point (for example, the harbor where the goods are loaded onto the main leg transport -- the ship). In the preliminary leg shipment, the destination point is the starting point of the main leg, for example, the harbor. The same applies for the subsequent leg shipment.
Leg determination type 0: Only determination of the assignment of deliveries to the stages.
With this leg determination type, no legs are determined by the system. You can assign the deliveries of the shipment to the existing (that is, manually entered) stages. See:
Leg determination type 1: Leg determination according to pick-up sequence and itinerary sequence.
The itinerary sequence results from the sorting of the delivery notes on the overview screen Delivery Notes for Shipment. If there is more than one point of departure, you must first define the sequence of the points of departure.
Example:
4 delivery notes:
L1 from V1 to W1
L2 from V2 to W2
L3 from V3 to W3
L4 from V2 to W1
(V1,V2,V3 shipping points W1,W2,W3 ship-to-parties)
Result of leg determination:
Preliminary legs:
V1 ---- V2 with L1
V2 ---- V3 with L1, L2, L4
Main legs:
V3 ---- W1 with all delivery notes
Subsequent legs:
W1 ---- W2 with L2, L3
W2 ---- W3 with L3
If you specified a main leg manually beforehand (by creating stages in the shipment document or by specifiying a route), the final point of the last preliminary leg is linked with the starting point of the main leg, and the final point of the main leg with the starting point of the first subsequent leg.
The assignment of the delivery notes to the generated stages takes place automatically.
Leg determination type 2: Preliminary leg for each point of departure. Subsequent leg for each point of destination.
Example:
4 delivery notes:
L1 from V1 to W1
L2 from V1 to W2
L3 from V2 to W2
L4 from V2 to W2
(V1,V2 shipping points W1,W2 ship-to-parties)
A main leg stage from 01 to 02 was specified.
Result of leg determination:
Preliminary leg stages:
V1 ---- O1 with L1, L2
V2 ---- O1 with L3, L4
Main leg stage:
O1 ---- O2 with all delivery notes
Subsequent leg stages:
O2 ---- W1 with L1
O2 ---- W2 with L2, L3, L4
If no main leg was specified, the shipping points are linked directly with the ship-to-parties.
This assignment of the delivery notes to the generated legs is executed automatically by the system.
CAREFUL:
Leg determination type 2 descripes a shipment that involves serveral
modes of transpoort (for example, trucks bring the deliveries to the shipping harbor, the goods are loaded onto a ship, at the destination harbor the goods are again loaded onto a truck).
You should only use this leg determination method if no separate documents are required for partial legs since the output (just like shipping units, texts, deadlines, and so on) is defined for the entire shipment (and is not leg-defined). Separate printing of, for example, truck and shipping documents at different times and for different legs is therefore not possible.
If your requirement extends beyond the actual documentation of the legs in the shipment document and you have to print separate papers for each mode of transport, we recommend that you create a transportation chain with several shipment documents.
Leg determination type 3: Preliminary leg for each delivery note, subsequent leg for each delivery note.
Example:
4 delivery notes:
L1 from V1 to W1
L2 from V1 to W2
L3 from V2 to W2
L4 from V2 to W2
(V1,V2 shipping points W1,W2 ship-to-parties)
A main leg from 01 to 02 was entered manually.
Result of the leg determination:
Preliminary leg stages:
V1 ---- O1 with L1
V1 ---- O1 with L2
V2 ---- O1 with L3
V2 ---- O1 with L4
Main leg stage:
O1 ---- O2 with all delivery notes
Subsequent leg stages:
O2 ---- W1 with L1
O2 ---- W2 with L2
O2 ---- W2 with L3
O2 ---- W2 with L4
If you did not specify a main leg, the system creates a stage from your shipping point to your ship-to-party for each delivery.
The assignment of the delivery notes to the generated legs is executed automatically by the system.
CAREFUL:
Leg determination type 3 describes a shipment involving several modes
of transport (for example, trucks bring the goods to the shipping harbor, the goods are loaded onto the ship, at the destination harbor the goods are again loaded onto trucks). See: Leg determination type 2.
Leg determination type 4: Like leg determination type 1, but the shipping type for preliminary leg and subsequent leg is taken into consideration.
This leg determination type works the same way as leg determination type 1; only the shipping type in the generated stages is filled differently.
While with leg determination type 1 all stages receive the shipping type that is in the shipment header, this only applies in the case of leg determination type 4 for the main legs and direct legs (that is those legs that have the leg indicator for main or direct leg). In the case of preliminary or subsequent legs, the shipping type preliminary leg or subsequent leg is determined from the shipment header.
With leg determination type 4 you can suppress certain legs, since legs are not created if the shipping type of the leg to be generated is empty.
In this case, no preliminary legs would be created during leg determination if the shipping type preliminary leg in the shipment header is blank. Definition
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in |
