VT01N — Create Shipment - Classic LE-TRA
VT01N is used to create a classic LE Transportation shipment document and assign deliveries for transportation processing. It is most useful when an ECC or legacy S/4HANA-compatible process still uses LE-TRA shipment functionality. Start with the exact document, material, organizational scope and business date, then follow status and document flow before changing configuration or master data.
Verified practitioner reference for VT01N — Create Shipment - Classic LE-TRA. It covers purpose, practical use, key data, proof-in-data checks, S/4HANA context, common errors and related objects so the transaction can be used as part of an end-to-end SAP investigation.
Published 19 Sept 2026· 566 words
Esta página aún no está disponible en español.
Purpose
create a classic LE Transportation shipment document and assign deliveries for transportation processing. VT01N should be understood in the surrounding business flow: source document or requirement, master data, determined status and follow-on document. Capturing that chain is more reliable than treating the transaction as an isolated screen.
When it is used
VT01N is typically used when an ECC or legacy S/4HANA-compatible process still uses LE-TRA shipment functionality. It is also valuable in project testing because it provides a repeatable point in the process. In production, narrow the document/material scope first and capture the before-state before mass actions or configuration changes.
How to use it in practice
- Confirm the landscape still uses classic LE-TRA rather than SAP TM.
- Select the shipment type and planning point.
- Assign the intended deliveries and review route/carrier data.
- Maintain shipment stages/dates required by the process.
- Save and verify delivery/shipment document flow.
Key data objects
These are the fields and objects that most often explain the result in VT01N. Record them in test evidence and support handovers.
- shipment type — verify the exact value, status, validity and relationship to the source or follow-on document.
- transportation planning point — verify the exact value, status, validity and relationship to the source or follow-on document.
- deliveries — verify the exact value, status, validity and relationship to the source or follow-on document.
- route/carrier — verify the exact value, status, validity and relationship to the source or follow-on document.
- shipment dates/status — verify the exact value, status, validity and relationship to the source or follow-on document.
How to prove it in the data
Prove the scenario through chronology and document flow. Start with the source order, delivery, requirement or master record; capture the transaction status; then follow the resulting delivery, billing, production or procurement object. Reconcile quantities, dates and statuses using the same organizational scope. A correct diagnosis explains why SAP selected or rejected the object, not just what message appeared.
ECC vs S/4HANA
VT01N belongs to classic LE-TRA shipment processing. In S/4HANA programs, SAP Transportation Management is the strategic transportation solution; confirm product/release scope before designing new processes around VT01N. For new S/4HANA designs, use current strategic applications and clean-core guidance even when a classic SAP GUI transaction remains available for support.
Common pitfalls and how to diagnose them
- Using VT01N in a process already governed by Transportation Management. Check the source and follow-on document statuses before applying a workaround.
- Assigning incompatible deliveries to one shipment. Check the source and follow-on document statuses before applying a workaround.
- Changing shipment dates without checking delivery planning impact. Check the source and follow-on document statuses before applying a workaround.
Whose problem this is
Primary ownership is the SD/O2C team, with MM, warehouse, Finance or Basis involved when the document flow crosses those components. A strong escalation includes document/material, plant or sales area, date, status, expected result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/vt01nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.