EWM Reference

/SCWM/PNPAKH

masterMixed key

Packaging 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

Identity

Module: Master Data & PartiesBronze: scwm_pnpakh

Notes

Packaging specifications persist as iPPE (integrated Product and Process Engineering) objects: the header is a node keyed by a node GUID plus a change counter, so one specification can have several rows and only the active one describes current behavior — filter STATUS before joining. The header-to-variant link runs through the generic iPPE relationship tables (PNODID for node identification, PRELID for the relationships), which are outside this catalog's namespaces and are not cataloged here; the practitioner hook from an on-screen packaging specification ID to a node GUID is PNODID's node-name column, and the exact mapping is not publicly documented, so treat it as a lead to verify in your own system rather than a rule. Because that link cannot be executed from cataloged columns alone, no join edges are drawn on this table.

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 — LGNUM plus 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 the CHAR(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.

Fields

14 fields · 3 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#	Field	Description	Type	Flags
1	MANDT	Client	CLNT(3)	Key
2	PNGUID	GUID of the iPPE node that carries the packaging specification header	RAW(16)	Key
3	PNCNT	Change counter — one specification has a row per change state, so the key is the node plus the version	NUMC(8)	Key
4	PNTXCNT	Counter into the iPPE node text tables, where the description lives	NUMC(5)
5	STATUS	Status of the packaging specification — filter it, because only the active state describes current packing behavior	CHAR(1)
6	ACTIVATE_TIME	Time the specification was activated	DEC(15)	UTCFilter date
7	ACTIVATED_BY	User who activated the specification	CHAR(12)
8	PS_GROUP	Group the packaging specification belongs to	CHAR(4)
9	LEVEL_SET	Level set — which set of packing levels the specification is built from	CHAR(10)
10	BAND_UP_REL	Upper rounding limit as a percentage of the demand quantity	DEC(16,3)
11	BAND_DN_REL	Lower rounding limit as a percentage of the demand quantity	DEC(16,3)
12	MINIMUM_QUAN	Minimum quantity a supplier will ship against this specification	INT4(10)
13	ROUNDING_GOAL	Rounding method applied when demand is rounded to whole packs	CHAR(4)
14	DOC_EXIST	Flag: documents are attached to the specification	CHAR(1)

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/PNPAKHon 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.

Query parameters

CatalogSchemaClient (MANDT)From timestamp (yyyymmddhhmmss, UTC)To timestamp (yyyymmddhhmmss, UTC)

Include optional filters (2)

5 parameters not filled: <catalog>, <schema>, <client>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCWM/PNPAKH — Packaging 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
-- Purpose: Column-selected read of /SCWM/PNPAKH — auto-generated from field metadata
-- Grain  : One row per client + PNGUID + PNCNT
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/PNPAKH; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_pnpakh — 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.PNGUID AS "GUID of the iPPE node that carries the packaging specification header",
  lower(hex(t.PNGUID)) AS "GUID of the iPPE node that carries the packaging specification header (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.PNCNT AS "Change counter — one specification has a row per change state, so the key is the node plus the version",
  t.PNTXCNT AS "Counter into the iPPE node text tables, where the description lives",
  t.STATUS AS "Status of the packaging specification — filter it, because only the active state describes current packing behavior",
  t.ACTIVATE_TIME AS "Time the specification was activated",  -- UTC
  t.ACTIVATED_BY AS "User who activated the specification",
  t.PS_GROUP AS "Group the packaging specification belongs to",
  t.LEVEL_SET AS "Level set — which set of packing levels the specification is built from",
  t.BAND_UP_REL AS "Upper rounding limit as a percentage of the demand quantity",
  t.BAND_DN_REL AS "Lower rounding limit as a percentage of the demand quantity",
  t.MINIMUM_QUAN AS "Minimum quantity a supplier will ship against this specification",
  t.ROUNDING_GOAL AS "Rounding method applied when demand is rounded to whole packs",
  t.DOC_EXIST AS "Flag: documents are attached to the specification"
FROM <catalog>.<schema>.scwm_pnpakh t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.ACTIVATE_TIME >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.ACTIVATE_TIME <= <TS_TO>
ORDER BY t.PNGUID;

Verified August 2026

Landing conventions differ — see namespaced names in a lakehouse.

Relationships

No join paths are cataloged for this table — see the notes above for how it connects.

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

/SCWM/PACKGeneral packing — build, repack, and unpack handling units at a work center
Read accessChangestock-hu

Browse more Master Data & Parties tables

/SCWM/PNPAKH

Fields

Boilerplate SQL

Relationships

Transaction codes that touch this table

More Master Data & Parties tables