/SCMB/TOENTITY
masterGUID keySupply 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
Two things make this table load-bearing for analytics: TZONE is what localizes EWM's UTC timestamps per site, and SCUGUID22 carries the same GUID in the CHAR22 compressed form the /SAPAPO tables key on — the one public row where both encodings sit side by side.
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
14 fields · 2 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | SCUGUID | Supply chain unit GUID — the RAW16 key warehouse, door, and party references resolve against | RAW(16) | Key |
| 3 | ENTITY | Readable supply chain unit identifier | CHAR(20) | |
| 4 | SCUGUID22 | The same GUID in its 22-character compressed form — the bridge to the CHAR22-keyed master-data tables | CHAR(22) | |
| 5 | SCUTYPE | Supply chain unit type | CHAR(4) | |
| 6 | TZONE | Time zone of the unit — what turns EWM's UTC stamps into local warehouse time | CHAR(6) | |
| 7 | PARTNER_GUID | Business partner GUID behind the unit | RAW(16) | |
| 8 | DELFLG | Deletion indicator | CHAR(1) | |
| 9 | LONGITUDE | Longitude of the unit | DEC(15,12) | |
| 10 | LATITUDE | Latitude of the unit | DEC(15,12) | |
| 11 | CREATEUSER | Created by | CHAR(12) | |
| 12 | CREATEUTC | Creation time | DEC(15) | UTCFilter date |
| 13 | CHANGEUSER | Last changed by | CHAR(12) | |
| 14 | CHANGEUTC | Time of the last change | DEC(15) |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCMB/TOENTITYon 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.
6 parameters not filled: <catalog>, <schema>, <client>, <SCUGUID>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCMB/TOENTITY — Supply 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
-- Purpose: Column-selected read of /SCMB/TOENTITY — auto-generated from field metadata
-- Grain : One row per client + SCUGUID
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCMB/TOENTITY; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scmb_toentity — 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.SCUGUID AS "Supply chain unit GUID — the RAW16 key warehouse, door, and party references resolve against",
lower(hex(t.SCUGUID)) AS "Supply chain unit GUID — the RAW16 key warehouse, door, and party references resolve against (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ENTITY AS "Readable supply chain unit identifier",
t.SCUGUID22 AS "The same GUID in its 22-character compressed form — the bridge to the CHAR22-keyed master-data tables",
t.SCUTYPE AS "Supply chain unit type",
t.TZONE AS "Time zone of the unit — what turns EWM's UTC stamps into local warehouse time",
t.PARTNER_GUID AS "Business partner GUID behind the unit",
lower(hex(t.PARTNER_GUID)) AS "Business partner GUID behind the unit (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.DELFLG AS "Deletion indicator",
t.LONGITUDE AS "Longitude of the unit",
t.LATITUDE AS "Latitude of the unit",
t.CREATEUSER AS "Created by",
t.CREATEUTC AS "Creation time", -- UTC
t.CHANGEUSER AS "Last changed by",
t.CHANGEUTC AS "Time of the last change" -- UTC
FROM <catalog>.<schema>.scmb_toentity t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.SCUGUID = unhex('<SCUGUID>') -- pass the 32-character hex form
-- AND t.CREATEUTC >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.CREATEUTC <= <TS_TO>
ORDER BY t.SCUGUID;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_t300_md.MANDT = scmb_toentity.MANDT AND scwm_t300_md.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scwm_tdoor.MANDT = scmb_toentity.MANDT AND scwm_tdoor.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON sapapo_matlwh.MANDT = scmb_toentity.MANDT AND sapapo_matlwh.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON sapapo_matlwhst.MANDT = scmb_toentity.MANDT AND sapapo_matlwhst.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance only
More Master Data & Parties tables
- /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
- /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