EWM Reference

/SCWM/T346T

textSemantic key

Queue descriptions — one row per queue per language; the readable name behind a queue code

Identity

Module: Resources & RF ExecutionBronze: scwm_t346t

Notes

Standard text-table layout with SPRAS directly after the client. Filter to one language or every queue join multiplies by the number of installed languages.

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 — LGNUM plus 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 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.

Text companion

/SCWM/T346T holds the per-language descriptions for /SCWM/T346 — one row per SPRAS. Filter to one language or rows multiply.

Fields

5 fields · 4 key

5 fields.

Table fields: position, field name, description, data type, and flags. 5 fields.
#	Field	Description	Type	Flags
1	MANDT	Client	CLNT(3)	Key
2	SPRAS	Language key of the description row	LANG(1)	Key
3	LGNUM	EWM warehouse number	CHAR(4)	Key
4	QUEUE	Queue the description belongs to	CHAR(10)	Key
5	TEXT	Queue description in the row's language	CHAR(40)

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

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

CatalogSchemaClient (MANDT)Warehouse number (LGNUM)

Include optional filters (1)

4 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>

-- ============================================================
-- Table  : /SCWM/T346T — Queue descriptions — one row per queue per language; the readable name behind a queue code
-- Purpose: Column-selected read of /SCWM/T346T — auto-generated from field metadata
-- Grain  : One row per client + SPRAS + LGNUM + QUEUE
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T346T; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t346t — 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.SPRAS AS "Language key of the description row",
  t.LGNUM AS "EWM warehouse number",
  t.QUEUE AS "Queue the description belongs to",
  t.TEXT AS "Queue description in the row's language"
FROM <catalog>.<schema>.scwm_t346t t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.LGNUM = '<LGNUM>'
ORDER BY t.SPRAS;

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>'

Browse more Resources & RF Execution tables