Skip to content
EWM Reference

/SCWM/T346

configSemantic key

Queue 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

Grain note

Configuration as it stands now — a queue definition is overwritten in place, so it describes today's routing, never the routing a historic task was created under

Notes

This is the queue master, under a name most community table lists get wrong: /SCWM/TQUEUE resolves as a name on the public mirrors but renders no data-dictionary content on any of them, while T346 renders in full and was verified on two. The queue columns on open and confirmed tasks, on warehouse orders, and on resources (both the assigned QUEUE and the ACT_QUEUE actually being worked) resolve here on warehouse number plus queue. One column deliberately does not: /SCWM/RSRC.MFS_QUEUE is plainly a queue, but no public source says material-flow queues are maintained in this master, so no edge is drawn from it and the reading is left to verify in your own system. PLC is the one column here that reaches the automation layer: it names the programmable logic controller a queue is driven by.

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.

Text companion

/SCWM/T346 keeps its readable descriptions in /SCWM/T346T — one row per language. Filter to one SPRAS or rows multiply.

Fields

8 fields · 3 key

8 fields.

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse number — queues are unique only within itCHAR(4)
Key
3QUEUEQueue code — the value every queue column on tasks, orders, and resources carriesCHAR(10)
Key
4RFRSRCOperating environment the queue serves — which execution channel picks its work upCHAR(1)
5PLCProgrammable logic controller the queue's work is driven by, where the queue belongs to the material flow systemCHAR(8)
6QTYPEQueue type used for RF task interleaving — how work from this queue may be mixed with work from anotherCHAR(4)
7SEMI_SGUIDWhether semi-system-guided processing is allowed for RF tasks in the queueCHAR(1)
8QUEUE_PRINTPrinting behavior for work issued from the queueCHAR(1)

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

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

5 parameters not filled: <catalog>, <schema>, <language>, <client>, <LGNUM>

-- ============================================================
-- Table  : /SCWM/T346 — Queue 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
-- Purpose: Column-selected read of /SCWM/T346 — auto-generated from field metadata
-- Grain  : One row per client + LGNUM + QUEUE
-- Caution: Configuration as it stands now — a queue definition is overwritten in place, so it describes today's routing, never the routing a historic task was created under
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T346; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t346 — 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 — queues are unique only within it",
  t.QUEUE AS "Queue code — the value every queue column on tasks, orders, and resources carries",
  t.RFRSRC AS "Operating environment the queue serves — which execution channel picks its work up",
  t.PLC AS "Programmable logic controller the queue's work is driven by, where the queue belongs to the material flow system",
  t.QTYPE AS "Queue type used for RF task interleaving — how work from this queue may be mixed with work from another",
  t.SEMI_SGUID AS "Whether semi-system-guided processing is allowed for RF tasks in the queue",
  t.QUEUE_PRINT AS "Printing behavior for work issued from the queue",
  tx.TEXT AS "Queue description in the row's language"
FROM <catalog>.<schema>.scwm_t346 t
LEFT JOIN <catalog>.<schema>.scwm_t346t tx
  ON tx.MANDT = t.MANDT
 AND tx.QUEUE = t.QUEUE
 AND tx.LGNUM = t.LGNUM
 AND tx.SPRAS = '<language>'  -- one language or rows multiply
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/T346/SCWM/T346Ttext table · 1:N
    ON scwm_t346.MANDT = scwm_t346t.MANDT AND scwm_t346.QUEUE = scwm_t346t.QUEUE AND scwm_t346.LGNUM = scwm_t346t.LGNUM AND scwm_t346t.SPRAS = '<language>'
  • /SCWM/ORDIM_O/SCWM/T346foreign key · N:1
    ON scwm_ordim_o.MANDT = scwm_t346.MANDT AND scwm_ordim_o.QUEUE = scwm_t346.QUEUE AND scwm_ordim_o.LGNUM = scwm_t346.LGNUM
  • /SCWM/ORDIM_C/SCWM/T346foreign key · N:1
    ON scwm_ordim_c.MANDT = scwm_t346.MANDT AND scwm_ordim_c.QUEUE = scwm_t346.QUEUE AND scwm_ordim_c.LGNUM = scwm_t346.LGNUM
  • /SCWM/ORDIM_L/SCWM/T346foreign key · N:1
    ON scwm_ordim_l.MANDT = scwm_t346.MANDT AND scwm_ordim_l.QUEUE = scwm_t346.QUEUE AND scwm_ordim_l.LGNUM = scwm_t346.LGNUM
  • /SCWM/WHO/SCWM/T346foreign key · N:1
    ON scwm_who.MANDT = scwm_t346.MANDT AND scwm_who.QUEUE = scwm_t346.QUEUE AND scwm_who.LGNUM = scwm_t346.LGNUM
  • /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/T346/SCWM/TMFSPLCforeign key · N:1
    ON scwm_t346.MANDT = scwm_tmfsplc.MANDT AND scwm_t346.PLC = scwm_tmfsplc.PLC AND scwm_t346.LGNUM = scwm_tmfsplc.LGNUM -- the one column where the queue master reaches the automation layer — populated only on queues driven by the material flow system

    the one column where the queue master reaches the automation layer — populated only on queues driven by the material flow system

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.