/SCWM/TRSRC_GRP
configSemantic keyResource groups — the grouping of resources that share a queue sequence; three columns, all key
Definition only. The group carries no attributes of its own: what it means is maintained elsewhere, as the ordered list of queues the group works, so a group code here is a key to join on rather than a row to read. Resources point at it through RSRC_GRP.
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
3 fields · 3 key
3 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | RSRC_GRP | Resource group — the whole table is this key; the group's behavior is maintained as the queue sequence assigned to it | CHAR(4) | Key |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TRSRC_GRPon 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.
4 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>
-- ============================================================
-- Table : /SCWM/TRSRC_GRP — Resource groups — the grouping of resources that share a queue sequence; three columns, all key
-- Purpose: Column-selected read of /SCWM/TRSRC_GRP — auto-generated from field metadata
-- Grain : One row per client + LGNUM + RSRC_GRP
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TRSRC_GRP; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_trsrc_grp — adjust to your landing convention (see quirks #namespace-slashes). 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.RSRC_GRP AS "Resource group — the whole table is this key; the group's behavior is maintained as the queue sequence assigned to it"
FROM <catalog>.<schema>.scwm_trsrc_grp 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
ON scwm_rsrc.MANDT = scwm_trsrc_grp.MANDT AND scwm_rsrc.RSRC_GRP = scwm_trsrc_grp.RSRC_GRP AND scwm_rsrc.LGNUM = scwm_trsrc_grp.LGNUM
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/QSEQSet the order in which a resource group works its queues — which pool of work its operators are offered first, second, and so onRead accessConfigurationresources
- /SCWM/RSRCMaintain resources — the operators, vehicles, and devices that execute warehouse orders, with their group, type, and assigned queueRead accessChangeresources
More Resources & RF Execution tables
- /SCWM/TRSRC_TYPResource types — the physical characteristics of a class of resource: travel velocities and their unit, position management, RF task-interleaving behavior, and the layout type used for automated aisles
- /SCWM/RSRCResources — the operators, vehicles, and devices that execute warehouse orders, with the queue each is working, the bin it is currently at, and the handling unit it is carrying
- /SCWM/T346Queue definition — the execution queues warehouse tasks, warehouse orders, and resources are routed through, with the operating environment each queue serves and the material-flow controller behind it where the queue drives automation
- /SCWM/T346TQueue descriptions — one row per queue per language; the readable name behind a queue code