VTTP table — Shipment Item Table

VTTP stores the assignment of a delivery to a shipment. A shipment document created in VT01N or VT02N has one header row in VTTK and one or more item rows in VTTP, each item row representing exactly one delivery that has been loaded onto that shipment. VTTP does not break the delivery down into its own line items; the granularity is delivery-to-shipment, not product-to-shipment. If a shipment carries five deliveries, there are five rows in VTTP for that TKNUM, one per delivery, each pointing back to the delivery header in LIKP through VBELN. Removing a delivery from a shipment, or deleting the shipment, removes or clears the corresponding VTTP row, which is usually the first place to check when a delivery is reported as stuck between 'goods issue done' and 'shipment complete'.

VTTP is client-dependent and small relative to LIKP or VBAK, so it is rarely a performance problem on its own, but it should never be read without restricting on TKNUM or VBELN first. Selecting by VBELN alone answers 'which shipment is this delivery on', which is the most common lookup. Selecting by TKNUM answers 'which deliveries are on this shipment'. Do not scan VTTP by date ranges; it carries no meaningful date fields of its own, those live on VTTK. When a shipment has been deleted, its VTTP rows disappear along with it, so an empty result set for a known TKNUM usually means the shipment was reversed, not that the query is wrong.

Symptom: a delivery shows as goods-issue-completed but the warehouse insists it was never loaded onto a truck. Select VTTP where VBELN equals the delivery number. If no row returns, the delivery was never assigned to any shipment and the physical loading step in transportation was skipped entirely; the goods issue happened independently of the shipment process. If a row returns, note the TKNUM and check VTTK for that shipment's status before assuming the shipment itself is complete.

VTTP is part of classic LE-TRA shipment processing and continues to exist unchanged in shape in S/4HANA for customers still running VT01N/VT02N-based transportation. It is not touched by the SAP Transportation Management (TM) integration model; systems that have moved freight planning to embedded TM or a decentralized TM system populate a different data model there, and VTTP becomes largely irrelevant for those shipments. Where classic shipment cost documents and VT01N are still in use, VTTP remains the authoritative delivery-to-shipment link with no compatibility view replacing it.

Shipment assignment logic and any custom rules for how deliveries get grouped onto shipments belong to the logistics execution or transportation configuration owner, usually the SD or LE consultant responsible for shipment types and route determination. Freight cost disputes that reference a TKNUM route through the same owner before escalating to controlling, since the shipment cost document depends on the VTTP assignment being correct first.

VTTK is the shipment header table and the natural first stop when investigating a TKNUM found in VTTP. LIKP is the delivery header that VTTP-VBELN points to; LIPS holds the delivery's own material lines and is not directly reachable from VTTP. VBFA carries the document flow that links delivery, shipment, and downstream billing documents together. VT01N, VT02N, and VT03N are the transactions that create, change, and display shipments and therefore write and read VTTP directly.