Skip to content
EWM Reference

/SCWM/T300_MD

configMixed key

Warehouse-to-party assignment — the supply chain unit the warehouse maps to plus the default entitled-to-dispose and ship-to parties

Notes

The bridge between the readable LGNUM and the GUID world: SCUGUID resolves to /SCMB/TOENTITY, which is how the /SCDL delivery documents' WAREHOUSE_ID and the /SAPAPO warehouse-product tables get back to a warehouse number. CUSTODIAN is carried for legacy data.

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.

Structural facts — how the table is keyed, not a trap by itself

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).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field, and UTC marks a timestamp stored in UTC rather than warehouse-local time.

Fields

7 fields · 2 key

7 fields.

Table fields: position, field name, description, data type, and flags. 7 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3CUSTODIANCustodian business partner — carried for legacy dataCHAR(10)
4ENTITLEDDefault party entitled to dispose for this warehouseCHAR(10)
5SC_UNITSupply chain unit the warehouse maps to, in its readable formCHAR(20)
6SCUGUIDSupply chain unit GUID — the join bridge to /SCMB/TOENTITYRAW(16)
7SHIPTODefault ship-to party for the warehouseCHAR(10)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

4 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>

-- ============================================================
-- Table  : /SCWM/T300_MD — Warehouse-to-party assignment — the supply chain unit the warehouse maps to plus the default entitled-to-dispose and ship-to parties
-- Purpose: Column-selected read of /SCWM/T300_MD — auto-generated from field metadata
-- Grain  : One row per client + LGNUM
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T300_MD; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t300_md — 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.LGNUM AS "EWM warehouse number",
  t.CUSTODIAN AS "Custodian business partner — carried for legacy data",
  t.ENTITLED AS "Default party entitled to dispose for this warehouse",
  t.SC_UNIT AS "Supply chain unit the warehouse maps to, in its readable form",
  t.SCUGUID AS "Supply chain unit GUID — the join bridge to /SCMB/TOENTITY",
  lower(hex(t.SCUGUID)) AS "Supply chain unit GUID — the join bridge to /SCMB/TOENTITY (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.SHIPTO AS "Default ship-to party for the warehouse"
FROM <catalog>.<schema>.scwm_t300_md t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.LGNUM = '<LGNUM>'
ORDER BY t.LGNUM;

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

  • /SCWM/T300_MD/SCWM/T300foreign key · 1:1
    ON scwm_t300_md.MANDT = scwm_t300.MANDT AND scwm_t300_md.LGNUM = scwm_t300.LGNUM
  • /SCWM/T300_MD/SCMB/TOENTITYGUID join · N:1
    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 only

Browse more Warehouse Structure tables

More Warehouse Structure tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by SAP. SAP, SAP S/4HANA, and SAP Extended Warehouse Management are trademarks or registered trademarks of SAP SE.