/SCWM/PVPAKC
masterMixed keyPackaging 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
SUB_PS carries a nested packaging specification, which is how a pallet recipe points at the carton recipe underneath it. It is typed as the packaging specification GUID rather than the iPPE node GUID this catalog's header table keys on, so no edge is drawn to the header — the nesting is real, the public evidence for how the two GUID spaces line up is not.
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
10 fields · 3 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | PVGUID | GUID of the iPPE variant the content belongs to — the same variant the element row hangs on | RAW(16) | Key |
| 3 | PVCNT | Change counter of the variant | NUMC(8) | Key |
| 4 | MATID | Product being packed, as a product GUID (RAW16 form) | RAW(16) | |
| 5 | SUB_PS | Nested packaging specification packed at this level — typed as the packaging specification GUID, not the iPPE node GUID the header keys on | RAW(16) | |
| 6 | UNIT | Unit of the packed quantity | UNIT(3) | |
| 7 | QUAN | How much of the product the level holds | QUAN(31,14) | |
| 8 | MEINS | Base unit of measure of the product | UNIT(3) | |
| 9 | REFMIX | Whether products sharing a reference product may be mixed in the pack | CHAR(1) | |
| 10 | BATCHMIX | Whether different batches may be packed together | CHAR(1) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/PVPAKCon 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/PVPAKC — Packaging 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
-- Purpose: Column-selected read of /SCWM/PVPAKC — 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/PVPAKC; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_pvpakc — 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 content belongs to — the same variant the element row hangs on",
lower(hex(t.PVGUID)) AS "GUID of the iPPE variant the content belongs to — the same variant the element row hangs on (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.MATID AS "Product being packed, as a product GUID (RAW16 form)",
lower(hex(t.MATID)) AS "Product being packed, as a product GUID (RAW16 form) (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.SUB_PS AS "Nested packaging specification packed at this level — typed as the packaging specification GUID, not the iPPE node GUID the header keys on",
lower(hex(t.SUB_PS)) AS "Nested packaging specification packed at this level — typed as the packaging specification GUID, not the iPPE node GUID the header keys on (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.UNIT AS "Unit of the packed quantity",
t.QUAN AS "How much of the product the level holds",
t.MEINS AS "Base unit of measure of the product",
t.REFMIX AS "Whether products sharing a reference product may be mixed in the pack",
t.BATCHMIX AS "Whether different batches may be packed together"
FROM <catalog>.<schema>.scwm_pvpakc 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_pvpakc.MANDT = sapapo_matkey.MANDT AND scwm_pvpakc.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
More Master Data & Parties tables
- /SCWM/PVPAKLPackaging 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
- /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