/SCWM/PVPAKL
masterMixed keyPackaging specification element — one level of the packing recipe as an iPPE variant: what packaging material is used, how much of it, and whether the level creates a handling unit
MATID here is the packaging material (the box, carton, or pallet), not the product being packed — the product is on the content table. HURELEVANT is the column that decides whether this level produces a real HU when the specification is executed, which is what makes a nested pack recipe turn into a nested HU hierarchy.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, configuration, an organizational object, or a language-striped text companion.
- Semantic key
- Every non-client key column is readable business data —
LGNUMplus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide). - GUID key
- Every non-client key column is a GUID —
RAW(16)on the /SCWM, /SCDL, /LIME, and /SCMB tables, and theCHAR(22)compressed form on the product master. Join the raw column; a hex rendering is for reading only, and the two encodings need converting between (see the quirks guide). - Mixed key
- The key mixes readable and GUID columns in either direction — a product GUID inside an otherwise-readable bin key, or a readable status type inside an otherwise-GUID key. Check which side of a join you are on (see the quirks guide).
- DOCCAT: PDO
- A /SCDL delivery table holds several document categories in one table — inbound and outbound requests, the inbound delivery, the outbound delivery order, and the final outbound delivery — discriminated by
DOCCAT. The chips list the categories this table carries; anchor the one you mean or documents of every kind come back together (see the quirks guide). - Embedded S/4HANA only
- Deployment: shown only when a table does not exist in both embedded S/4HANA EWM and decentralized EWM. No table in this wave is deployment-specific, so the badge stays absent until one is.
Structural facts — how the table is keyed, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
9 fields · 3 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | PVGUID | GUID of the iPPE variant the packing element belongs to | RAW(16) | Key |
| 3 | PVCNT | Change counter of the variant | NUMC(8) | Key |
| 4 | ELEMENT_TYPE | Element type — what part the element plays in the packing level | CHAR(4) | |
| 5 | MATID | Packaging material used at this level, as a product GUID (RAW16 form) — the box or pallet, not the product being packed | RAW(16) | |
| 6 | HURELEVANT | Whether this level creates a handling unit when the specification is executed | CHAR(1) | |
| 7 | UNIT | Unit of the element quantity | UNIT(3) | |
| 8 | QUAN | How much packaging material the level consumes | QUAN(31,14) | |
| 9 | DISPLAY_ORDER | Sequence of the element within its element group | CHAR(8) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/PVPAKLon Databricks — the client anchor is already in place, the namespaced name is rendered as the underscore bronze name replication targets conventionally land it under, and any RAW16 GUID column selects a hex rendering alongside the raw value. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
3 parameters not filled: <catalog>, <schema>, <client>
-- ============================================================
-- Table : /SCWM/PVPAKL — Packaging specification element — one level of the packing recipe as an iPPE variant: what packaging material is used, how much of it, and whether the level creates a handling unit
-- Purpose: Column-selected read of /SCWM/PVPAKL — auto-generated from field metadata
-- Grain : One row per client + PVGUID + PVCNT
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/PVPAKL; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_pvpakl — adjust to your landing convention (see quirks #namespace-slashes). RAW16 GUID columns are joined raw; the hex aliases are for display only (#guid-keys). Timestamps flagged UTC are DEC(15) yyyymmddhhmmss values in UTC, not warehouse local time (#utc-timestamps).
-- ============================================================
SELECT
t.MANDT AS "Client",
t.PVGUID AS "GUID of the iPPE variant the packing element belongs to",
lower(hex(t.PVGUID)) AS "GUID of the iPPE variant the packing element belongs to (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.PVCNT AS "Change counter of the variant",
t.ELEMENT_TYPE AS "Element type — what part the element plays in the packing level",
t.MATID AS "Packaging material used at this level, as a product GUID (RAW16 form) — the box or pallet, not the product being packed",
lower(hex(t.MATID)) AS "Packaging material used at this level, as a product GUID (RAW16 form) — the box or pallet, not the product being packed (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.HURELEVANT AS "Whether this level creates a handling unit when the specification is executed",
t.UNIT AS "Unit of the element quantity",
t.QUAN AS "How much packaging material the level consumes",
t.DISPLAY_ORDER AS "Sequence of the element within its element group"
FROM <catalog>.<schema>.scwm_pvpakl t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
ORDER BY t.PVGUID;Verified August 2026
Landing conventions differ — see namespaced names in a lakehouse.
Relationships
Diagram of 1-hop neighbors — join details below. GUID joins and text-table joins are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON scwm_pvpakc.MANDT = scwm_pvpakl.MANDT AND scwm_pvpakc.PVGUID = scwm_pvpakl.PVGUID AND scwm_pvpakc.PVCNT = scwm_pvpakl.PVCNT -- RAW16 GUID equality — join raw; hex is for display/conformance only · what is packed and what it is packed in are two rows on the same iPPE variant — join the variant GUID and its change counter together, or change states crosswhat is packed and what it is packed in are two rows on the same iPPE variant — join the variant GUID and its change counter together, or change states cross
ON scwm_pvpakl.MANDT = sapapo_matkey.MANDT AND scwm_pvpakl.MATID = sapapo_matkey.MATID -- the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equalitythe /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality
Transaction codes that touch this table
Curated: the EWM transactions an analyst would trace back to these rows, and how each one touches them.
R read · W write · R/W read + write
More Master Data & Parties tables
- /SAPAPO/MATKEYThe product master key table — the bridge between the internal product GUID every EWM table carries and the readable material number, with the base unit, weights, volumes, and shelf-life control
- /SAPAPO/MATLWHWarehouse product — the warehouse-level settings for a product: putaway and stock-removal control, storage section and bin type indicators, stock determination, two-step picking relevance, and the slotting demand quantity
- /SAPAPO/MATLWHSTWarehouse product at storage-type level — the same product's parameters narrowed to one storage type: preferred section and bin type, maximum fixed bins, and the min/max/replenishment quantity set
- /SCMB/TOENTITYSupply chain unit header — the location object EWM resolves warehouse, door, and party GUIDs against, carrying the readable identifier, the time zone, and the geo-coordinates
- /SCWM/PNPAKHPackaging specification header — the packing recipe as an iPPE node, with its status, the time it was activated, its group, and the rounding limits that decide how demand quantities are rounded to whole packs
- /SCWM/PVPAKCPackaging specification content — what is packed at a level: the product, the quantity and unit, and the mixing rules that say whether different products or batches may share the pack