SAP Reference

VT01N

Create S/4HANA status: Active

Create Shipment

Module: LE · Logistics Execution
Notes

Classic LE-TRA shipment processing. LE-TRA is not SAP's S/4HANA target architecture; its compatibility-package usage rights run only through 2030, with SAP S/4HANA Transportation Management as the target. This is a usage-right boundary, not a claim that the transaction is physically removed on that date.

What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Boilerplate SQL

Databricks SQL

Starting point for querying the tables behind this transaction. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <TKNUM>

-- ============================================================
-- T-Code : VT01N Create Shipment
-- Purpose: Create Shipment — auto-generated boilerplate from tcode-table-map
-- Grain  : One row per VTTK joined to VTTP, VTTS, VTSP, VTPA
-- Tables : VTTK, VTTP, VTTS, VTSP, VTPA
-- Notes  : Auto-generated skeleton. Add MAKT/T001W/LFA1/KNA1 enrichment joins as needed for the business question. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  h.MANDT   AS "Client",
  h.TKNUM   AS "Shipment Number",
  l.TPNUM   AS "Item Number in the Shipment",
  v.TSNUM   AS "Stage Number in Transport",
  vt.TSNUM  AS "Stage Number in Transport",
  vt.TPNUM  AS "Item Number in the Shipment",
  vtp.VBELN AS "Sales and Distribution Document Number",
  vtp.POSNR AS "Item number of the SD document",
  vtp.PARVW AS "Partner Function"
FROM <catalog>.<schema>.vttk h
LEFT JOIN <catalog>.<schema>.vttp l
  ON l.MANDT = h.MANDT
 AND l.TKNUM = h.TKNUM
LEFT JOIN <catalog>.<schema>.vtts v
  ON v.MANDT = h.MANDT
 AND v.TKNUM = h.TKNUM
LEFT JOIN <catalog>.<schema>.vtsp vt
  ON vt.MANDT = h.MANDT
 AND vt.TKNUM = h.TKNUM
LEFT JOIN <catalog>.<schema>.vtpa vtp
  ON vtp.MANDT = h.MANDT
WHERE
  h.MANDT = '<MANDT>'
  AND h.TKNUM = '<TKNUM>'
ORDER BY h.TKNUM;

Tables Used by This Transaction

A curated list of the main business tables behind this transaction, drawn from this reference’s catalog. Tables a query joins only for names and descriptions may be left out.

How these tables connect — join details in the list below.

Loading relationship diagram…

Join details

  • VTTKVTTPheader item · 1:N
    ON vttk.TKNUM = vttp.TKNUM
  • VTTKVTTSheader item · 1:N
    ON vttk.TKNUM = vtts.TKNUM
  • VTTSVTSPheader item · 1:N
    ON vtts.TKNUM = vtsp.TKNUM

R read · W write · R/W read + write