/SCWM/TWORKST
configMixed keyWork centers — the packing, deconsolidation, value-added-service, and counting stations in the warehouse, each modeled as a storage type and bin
The DDIC short text calls this a work center profile. LGPLA ties the station to a real bin, so HU movements to and from a work center look like ordinary bin moves in the task tables.
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
17 fields · 3 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | WORKSTATION | Work center within the warehouse (packing, deconsolidation, value-added services, counting) | CHAR(4) | Key |
| 4 | PROCS | Process interface the work center runs | CHAR(4) | |
| 5 | LGTYP | Storage type the work center is modeled as | CHAR(4) | |
| 6 | LGPLA | Storage bin assigned to the work center | CHAR(18) | |
| 7 | I_SECTION | Inbound section of the work center, where arriving handling units land | CHAR(4) | |
| 8 | O_SECTION | Outbound section of the work center, where finished handling units leave | CHAR(4) | |
| 9 | PROCTY | Warehouse process type used for moves created at the work center | CHAR(4) | |
| 10 | WRKSTTYP | Work center layout type | CHAR(4) | |
| 11 | HUINPUT | Whether the handling-unit field is ready for input in the RF and desktop user interfaces | CHAR(1) | |
| 12 | DLFT_PMAT | Default packaging material, as a product GUID | RAW(16) | |
| 13 | RL_PROCTY | Warehouse process type for return transfers from the pick point | CHAR(4) | |
| 14 | RLTYP | Return storage type for pick-point returns | CHAR(4) | |
| 15 | RLBER | Return storage section for pick-point returns | CHAR(4) | |
| 16 | AAREA_PLAN | Activity area used for planning at this work center | CHAR(4) | |
| 17 | SCALE | Identifier of the scale connected to the work center | CHAR(10) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TWORKSTon 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.
5 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <WORKSTATION>
-- ============================================================
-- Table : /SCWM/TWORKST — Work centers — the packing, deconsolidation, value-added-service, and counting stations in the warehouse, each modeled as a storage type and bin
-- Purpose: Column-selected read of /SCWM/TWORKST — auto-generated from field metadata
-- Grain : One row per client + LGNUM + WORKSTATION
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TWORKST; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tworkst — 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.WORKSTATION AS "Work center within the warehouse (packing, deconsolidation, value-added services, counting)",
t.PROCS AS "Process interface the work center runs",
t.LGTYP AS "Storage type the work center is modeled as",
t.LGPLA AS "Storage bin assigned to the work center",
t.I_SECTION AS "Inbound section of the work center, where arriving handling units land",
t.O_SECTION AS "Outbound section of the work center, where finished handling units leave",
t.PROCTY AS "Warehouse process type used for moves created at the work center",
t.WRKSTTYP AS "Work center layout type",
t.HUINPUT AS "Whether the handling-unit field is ready for input in the RF and desktop user interfaces",
t.DLFT_PMAT AS "Default packaging material, as a product GUID",
lower(hex(t.DLFT_PMAT)) AS "Default packaging material, as a product GUID (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.RL_PROCTY AS "Warehouse process type for return transfers from the pick point",
t.RLTYP AS "Return storage type for pick-point returns",
t.RLBER AS "Return storage section for pick-point returns",
t.AAREA_PLAN AS "Activity area used for planning at this work center",
t.SCALE AS "Identifier of the scale connected to the work center"
FROM <catalog>.<schema>.scwm_tworkst t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.WORKSTATION = '<WORKSTATION>'
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
ON scwm_tworkst.MANDT = scwm_lagp.MANDT AND scwm_tworkst.LGPLA = scwm_lagp.LGPLA AND scwm_tworkst.LGNUM = scwm_lagp.LGNUMON scwm_tworkst.MANDT = sapapo_matkey.MANDT AND scwm_tworkst.DLFT_PMAT = 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 Warehouse Structure tables
- /SCWM/T300The warehouse number definition — one row per EWM warehouse, the four-character key every structure, bin, stock, and task row is striped by
- /SCWM/T300_MDWarehouse-to-party assignment — the supply chain unit the warehouse maps to plus the default entitled-to-dispose and ship-to parties
- /SCWM/T300TWarehouse number descriptions — one row per warehouse per language; the readable name behind LGNUM
- /SCWM/T301Storage type definition — one row per storage type in a warehouse; the first level of structure below the warehouse number
- /SCWM/T301GStorage type groups — the grouping of storage types that share one stock-removal rule, putaway rule, and maximum-quantity check
- /SCWM/T301MStorage type group assignment — which storage types belong to a group and in what sequence they are searched