/SCWM/RSRC
masterMixed keyResources — 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
Current state, not history — the queue, bin, and carried HU columns are overwritten as work proceeds; execution history lives on the task and order tables
QUEUE against ACT_QUEUE shows where a resource was assigned versus where it actually worked. The resource's group and type resolve against the two configuration tables in this module; MFS_QUEUE names a queue for material-flow scenarios, and because no public source states that those values are maintained in the same queue master, no edge is drawn from it.
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
16 fields · 3 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | RSRC | Resource — an RF user, vehicle, or material-flow device that executes work | CHAR(18) | Key |
| 4 | RSRC_TYPE | Resource type | CHAR(4) | |
| 5 | RSRC_GRP | Resource group used for queue assignment | CHAR(4) | |
| 6 | UNAME | SAP user currently logged on to the resource | CHAR(12) | |
| 7 | RFIND | RF execution environment indicator | CHAR(1) | |
| 8 | GUID_HU | GUID of the handling unit the resource is currently carrying | RAW(16) | |
| 9 | QUEUE | Queue the resource is assigned to | CHAR(10) | |
| 10 | ACT_QUEUE | Queue the resource is actually working | CHAR(10) | |
| 11 | LGTYP | Storage type of the resource's last removal | CHAR(4) | |
| 12 | ACTUAL_BIN | Bin where the resource currently is | CHAR(18) | |
| 13 | DEFAULT_BIN | The resource's default (home) bin | CHAR(18) | |
| 14 | LTRANSCHG_AT | Time of the last logical-transaction change | DEC(15) | UTCFilter date |
| 15 | MFS_QUEUE | Queue assigned to the resource in material flow system scenarios | CHAR(10) | |
| 16 | EXCCODE_OVERALL | Overall exception code currently set on the resource | CHAR(4) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/RSRCon 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.
7 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <RSRC>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/RSRC — Resources — 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
-- Purpose: Column-selected read of /SCWM/RSRC — auto-generated from field metadata
-- Grain : One row per client + LGNUM + RSRC
-- Caution: Current state, not history — the queue, bin, and carried HU columns are overwritten as work proceeds; execution history lives on the task and order tables
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/RSRC; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_rsrc — 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.RSRC AS "Resource — an RF user, vehicle, or material-flow device that executes work",
t.RSRC_TYPE AS "Resource type",
t.RSRC_GRP AS "Resource group used for queue assignment",
t.UNAME AS "SAP user currently logged on to the resource",
t.RFIND AS "RF execution environment indicator",
t.GUID_HU AS "GUID of the handling unit the resource is currently carrying",
lower(hex(t.GUID_HU)) AS "GUID of the handling unit the resource is currently carrying (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.QUEUE AS "Queue the resource is assigned to",
t.ACT_QUEUE AS "Queue the resource is actually working",
t.LGTYP AS "Storage type of the resource's last removal",
t.ACTUAL_BIN AS "Bin where the resource currently is",
t.DEFAULT_BIN AS "The resource's default (home) bin",
t.LTRANSCHG_AT AS "Time of the last logical-transaction change", -- UTC
t.MFS_QUEUE AS "Queue assigned to the resource in material flow system scenarios",
t.EXCCODE_OVERALL AS "Overall exception code currently set on the resource"
FROM <catalog>.<schema>.scwm_rsrc t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.RSRC = '<RSRC>'
-- AND t.LTRANSCHG_AT >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.LTRANSCHG_AT <= <TS_TO>
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_who.MANDT = scwm_rsrc.MANDT AND scwm_who.RSRC = scwm_rsrc.RSRC AND scwm_who.LGNUM = scwm_rsrc.LGNUMON scwm_rsrc.MANDT = scwm_huhdr.MANDT AND scwm_rsrc.GUID_HU = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scwm_rsrc.MANDT = scwm_t346.MANDT AND scwm_rsrc.QUEUE = scwm_t346.QUEUE AND scwm_rsrc.LGNUM = scwm_t346.LGNUM -- the queue the resource is assigned to; ACT_QUEUE (the one it is actually working) resolves against the same masterthe queue the resource is assigned to; ACT_QUEUE (the one it is actually working) resolves against the same master
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.LGNUMON scwm_rsrc.MANDT = scwm_trsrc_typ.MANDT AND scwm_rsrc.RSRC_TYPE = scwm_trsrc_typ.RSRC_TYPE AND scwm_rsrc.LGNUM = scwm_trsrc_typ.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/MONThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resourcesRead accessList / Monitorwarehouse-tasks
- /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/RFUILog on to the RF environment — the radio-frequency screen an operator works warehouse orders fromRead/write accessList / Monitorresources
- /SCWM/RSRCMaintain resources — the operators, vehicles, and devices that execute warehouse orders, with their group, type, and assigned queueRead/write accessChangeresources
More Resources & RF Execution tables
- /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
- /SCWM/TRSRC_GRPResource groups — the grouping of resources that share a queue sequence; three columns, all key
- /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