Skip to content
EWM Reference

/SCWM/RSRC

masterMixed key

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

Identity
Grain note

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

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.

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.
Used in the library

Fields

16 fields · 3 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3RSRCResource — an RF user, vehicle, or material-flow device that executes workCHAR(18)
Key
4RSRC_TYPEResource typeCHAR(4)
5RSRC_GRPResource group used for queue assignmentCHAR(4)
6UNAMESAP user currently logged on to the resourceCHAR(12)
7RFINDRF execution environment indicatorCHAR(1)
8GUID_HUGUID of the handling unit the resource is currently carryingRAW(16)
9QUEUEQueue the resource is assigned toCHAR(10)
10ACT_QUEUEQueue the resource is actually workingCHAR(10)
11LGTYPStorage type of the resource's last removalCHAR(4)
12ACTUAL_BINBin where the resource currently isCHAR(18)
13DEFAULT_BINThe resource's default (home) binCHAR(18)
14LTRANSCHG_ATTime of the last logical-transaction changeDEC(15)
UTCFilter date
15MFS_QUEUEQueue assigned to the resource in material flow system scenariosCHAR(10)
16EXCCODE_OVERALLOverall exception code currently set on the resourceCHAR(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.

Query parameters

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

  • /SCWM/WHO/SCWM/RSRCforeign key · N:1
    ON scwm_who.MANDT = scwm_rsrc.MANDT AND scwm_who.RSRC = scwm_rsrc.RSRC AND scwm_who.LGNUM = scwm_rsrc.LGNUM
  • /SCWM/RSRC/SCWM/HUHDRGUID join · N:1
    ON 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 only
  • /SCWM/RSRC/SCWM/T346foreign key · N:1
    ON 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 master

    the queue the resource is assigned to; ACT_QUEUE (the one it is actually working) resolves against the same master

  • /SCWM/RSRC/SCWM/TRSRC_GRPforeign key · N:1
    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
  • /SCWM/RSRC/SCWM/TRSRC_TYPforeign key · N:1
    ON 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

Browse more Resources & RF Execution tables

More Resources & RF Execution 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.