Shipment Document containing all the goods that are consolidated by a ship-from party and are then transported together from an issuing location (a plant, for example) to a destination location (a customer, for example). The shipment forms the basis for planning, executing, and monitoring the transportation of goods.
You can create shipments both manually and automatically.
A shipment can have different characteristics that are determined by the shipment type as well as its relationship to other shipments. You define the shipment type in Customizing for
Transportation Management (TM)
. It contains all the important control parameters for the shipment document. The following table shows the possible instances of shipments, the required settings, and the usages:
Instance |
Settings |
Use |
|---|---|---|
Transportation request |
|
You can assign transportation requests to bills of lading or to freight documents. |
Bill of lading |
|
|
The following classification is relevant to the processes in the
Extended
Warehouse Management (EWM)
component:
Planned shipment
: Can still change with regard to type and size, for example, due to a subsequent delivery split in the
Extended
Warehouse Management (EWM)
component.
Final shipment : Is fixed with regard to type and size, in other words, it is confirmed. Most of these shipments are already packed or loaded.
The header contains data such as:
Incoterms
Partners
Dates/times
Transportation details such as transportation mode, route, stops, and transit direction
The shipment items contain data such as locations, dates/times, packages, products, weight and volume, units of measure, and references to the original document, for example, the delivery.
The automatic creation of shipments occurs via an integration interface with goods accepted and shipping. You can also communicate shipments using IDocs. The IDoc structure of the shipment can be mapped to the EDIFACTstandard IFTMIN (International Forwarding and/or Transport Message Instruction).