LIKP
transaction S/4HANA status: ActiveSD Document: Delivery Header Data
MANDT · VBELN
All 38 fieldsWhat 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).
- Linked type codes
CLNT — the client key; filter it explicitly and carry it through every join.
NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.
DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.
CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.
LANG — a language key in a text table — one row per language.
What LIKP is for
One row per delivery document, created the moment VL01N (or its background equivalents) creates the delivery — before picking, before goods issue. A delivery number in LIKP is a plan to ship, not evidence anything shipped; WADAT_IST staying 00000000 is how you tell the difference.
Joins that work — and the traps
LIPS on (MANDT, VBELN)
1:N, items.
KNA1 twice
KUNNR is the ship-to, KUNAG the sold-to. Reports that join KNA1 once on "the customer field" silently pick one and are wrong for the other.
Statuses
ECC reads VBUK on (MANDT, VBELN); S/4HANA has the status fields (WBSTK, GBSTK, FKSTK, KOSTK…) directly on LIKP. Same VBELN, no join.
VBUK
The sales order is NOT on the header
Order references live on LIPS (VGBEL/VGPOS) because one delivery can combine multiple orders.
What LIKP does not contain
No materials, no quantities (LIPS); no goods-movement evidence (MSEG/MATDOC via VBELN_IM, or VBFA); no route-execution/shipment data (VTTK/VTTP); in ECC, no statuses (VBUK).
What breaks in practice
- Zero-dates: every DATS field is
00000000until filled — cast blindly and open deliveries appear shipped on a garbage date. - One-delivery-one-order assumptions: order combination puts lines from several orders under one header.
- OTD against the wrong date: WADAT vs LFDAT vs the order's requested date measure three different promises.
Shape & growth
Grows with shipment volume — one row per delivery ever created; header:item ratio follows your lines-per-delivery.
ECC vs S/4HANA
Table survives unchanged in role; gains the LIKP_STATUS include (statuses formerly in VBUK). Remains transparent; no compatibility-view indirection.
Fields
38 fields · 2 key
38 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | T000 |
| Primary key | VBELN | Delivery | CHAR | 10 | |
| ERNAM | Name of Person Who Created the Object | CHAR | 12 | ||
| ERZET | Entry Time | TIMS | 6 | ||
| ERDAT | Date on Which Record Was Created | DATS | 8 | ||
| BZIRK | Sales District | CHAR | 6 | ||
| VSTEL | Shipping Point/Receiving Point | CHAR | 4 | ||
| VKORG | Sales Organization | CHAR | 4 | TVKO | |
| LFART | Delivery Type | CHAR | 4 | ||
| LFDAT | Delivery Date | DATS | 8 | ||
| BLDAT | Document Date in Document | DATS | 8 | ||
| WADAT | Planned Goods Movement Date | DATS | 8 | ||
| WADAT_IST | Actual Goods Movement Date | DATS | 8 | ||
| LDDAT | Loading Date | DATS | 8 | ||
| TDDAT | Transportation Planning Date | DATS | 8 | ||
| LFUHR | Delivery Time | TIMS | 6 | ||
| KUNAG | Sold-To Party | CHAR | 10 | KNA1 | |
| KUNNR | Ship-To Party | CHAR | 10 | KNA1 | |
| BTGEW | Total Weight | QUAN | 15,3 | ||
| NTGEW | Net Weight | QUAN | 15,3 | ||
| GEWEI | Weight Unit | UNIT | 3 | T006 | |
| VOLUM | Volume | QUAN | 15,3 | ||
| VOLEH | Volume Unit | UNIT | 3 | T006 | |
| ANZPK | Total Number of Packages in Delivery | NUMC | 5 | ||
| FKSTKS/4HANA only — this field is not on this table in ECC; the equivalent status lives on VBUK/VBUP there | Billing Status | CHAR | 1 | ||
| ROUTE | Route | CHAR | 6 | ||
| TRAGR | Transportation Group | CHAR | 4 | ||
| LIFEX | External Identification of Delivery Note | CHAR | 35 | ||
| VBTYP | SD Document Category | CHAR | 1 | ||
| WERKS | Plant | CHAR | 4 | T001W | |
| LGNUM | Warehouse Number/Complex | CHAR | 3 | T300 | |
| VERUR | Distribution Delivery | CHAR | 35 | ||
| LVSTKS/4HANA only — this field is not on this table in ECC; the equivalent status lives on VBUK/VBUP there | Warehouse Status | CHAR | 1 | ||
| XBLNR | Reference Document Number | CHAR | 25 | ||
| BOLNR | Bill of Lading | CHAR | 35 | ||
| LIFNR | Vendor Number at Header Level | CHAR | 10 | LFA1 | |
| INCO1 | Incoterms (Part 1) | CHAR | 3 | ||
| INCO2 | Incoterms (Part 2) | CHAR | 28 |
Fields marked S/4 arrived on this table with S/4HANA’s VBUK/VBUP status-field move. In ECC the equivalent status lives on VBUK/VBUP, not here.
Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading LIKP on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
3 parameters not filled: <catalog>, <schema>, <MANDT>
-- ============================================================
-- Table : LIKP SD Document: Delivery Header Data
-- Purpose: Column-selected read of LIKP — auto-generated from field metadata
-- Grain : One row per VBELN
-- Notes : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
h.MANDT AS "Client",
h.VBELN AS "Delivery",
h.ERNAM AS "Name of Person Who Created the Object",
h.ERZET AS "Entry Time",
h.ERDAT AS "Date on Which Record Was Created",
h.BZIRK AS "Sales District",
h.VSTEL AS "Shipping Point/Receiving Point",
h.VKORG AS "Sales Organization",
h.LFART AS "Delivery Type",
h.LFDAT AS "Delivery Date",
h.BLDAT AS "Document Date in Document",
h.WADAT AS "Planned Goods Movement Date",
h.WADAT_IST AS "Actual Goods Movement Date",
h.LDDAT AS "Loading Date",
h.TDDAT AS "Transportation Planning Date",
h.LFUHR AS "Delivery Time",
h.KUNAG AS "Sold-To Party",
h.KUNNR AS "Ship-To Party",
h.BTGEW AS "Total Weight",
h.NTGEW AS "Net Weight",
h.GEWEI AS "Weight Unit",
h.VOLUM AS "Volume",
h.VOLEH AS "Volume Unit",
h.ANZPK AS "Total Number of Packages in Delivery",
h.FKSTK AS "Billing Status",
h.ROUTE AS "Route",
h.TRAGR AS "Transportation Group",
h.LIFEX AS "External Identification of Delivery Note",
h.VBTYP AS "SD Document Category",
h.WERKS AS "Plant",
h.LGNUM AS "Warehouse Number/Complex",
h.VERUR AS "Distribution Delivery",
h.LVSTK AS "Warehouse Status",
h.XBLNR AS "Reference Document Number",
h.BOLNR AS "Bill of Lading",
h.LIFNR AS "Vendor Number at Header Level",
h.INCO1 AS "Incoterms (Part 1)",
h.INCO2 AS "Incoterms (Part 2)"
FROM <catalog>.<schema>.likp h
WHERE
h.MANDT = '<MANDT>'
ORDER BY h.VBELN;Verified August 2026
Released CDS views over this table
Released SAP standard VDM views that read over LIKP. Prefer these over classic-table reads on S/4HANA where available.
Relationships
Diagram of 1-hop neighbors — join details below.
Join details
ON likp.VBELN = lips.VBELN