/SCWM/TMFSPLC
configSemantic keyProgrammable logic controllers — the material flow system's definition of each controller EWM exchanges telegrams with, including the warehouse process types used for conveyor putaway, fault handling, and stock transfer
This is where the automation layer is configured, and it is the reason a warehouse with conveyors and cranes shows process types in the task data that no operator ever chose. The communication-layer columns (the destination, the interface type, the mode) describe how EWM talks to the controller; the function-module columns on the DDIC page are implementation plumbing and are not curated. Queues reach a controller through the queue master's PLC column.
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
14 fields · 3 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number the controller belongs to | CHAR(4) | Key |
| 3 | PLC | Programmable logic controller code — what the queue master's PLC column points at | CHAR(8) | Key |
| 4 | PROCTYPE | Warehouse process type used for putaways over the conveyor — the reason automated warehouses show process types nobody chose by hand | CHAR(4) | |
| 5 | PROCTYPE_ERR | Warehouse process type used when a handling unit ends up in fault handling | CHAR(4) | |
| 6 | PROCTYPE_ATF | Warehouse process type used for movement postings raised by the material flow system | CHAR(4) | |
| 7 | PROCTYPE_STOCK_TRANS | Warehouse process type used for stock transfers by material-flow resources | CHAR(4) | |
| 8 | CL_MODE | Communication layer mode EWM talks to the controller through | CHAR(1) | |
| 9 | RFCDST | Logical destination the telegrams are sent to | CHAR(32) | |
| 10 | PLCIFTYPE | Interface type of the controller | CHAR(1) | |
| 11 | PLC_MODE | Operating mode the controller is in | CHAR(1) | |
| 12 | EXCCODE | Exception code raised when the material flow system changes a destination bin | CHAR(4) | |
| 13 | EWM_ID | Identification EWM sends as the telegram sender | CHAR(8) | |
| 14 | LOGGING | Whether telegram traffic for this controller is logged | CHAR(1) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TMFSPLCon 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/TMFSPLC — Programmable logic controllers — the material flow system's definition of each controller EWM exchanges telegrams with, including the warehouse process types used for conveyor putaway, fault handling, and stock transfer
-- Purpose: Column-selected read of /SCWM/TMFSPLC — auto-generated from field metadata
-- Grain : One row per client + LGNUM + PLC
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TMFSPLC; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tmfsplc — 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 the controller belongs to",
t.PLC AS "Programmable logic controller code — what the queue master's PLC column points at",
t.PROCTYPE AS "Warehouse process type used for putaways over the conveyor — the reason automated warehouses show process types nobody chose by hand",
t.PROCTYPE_ERR AS "Warehouse process type used when a handling unit ends up in fault handling",
t.PROCTYPE_ATF AS "Warehouse process type used for movement postings raised by the material flow system",
t.PROCTYPE_STOCK_TRANS AS "Warehouse process type used for stock transfers by material-flow resources",
t.CL_MODE AS "Communication layer mode EWM talks to the controller through",
t.RFCDST AS "Logical destination the telegrams are sent to",
t.PLCIFTYPE AS "Interface type of the controller",
t.PLC_MODE AS "Operating mode the controller is in",
t.EXCCODE AS "Exception code raised when the material flow system changes a destination bin",
t.EWM_ID AS "Identification EWM sends as the telegram sender",
t.LOGGING AS "Whether telegram traffic for this controller is logged"
FROM <catalog>.<schema>.scwm_tmfsplc 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_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 systemthe one column where the queue master reaches the automation layer — populated only on queues driven by the material flow system
ON scwm_tmfscp.MANDT = scwm_tmfsplc.MANDT AND scwm_tmfscp.PLC = scwm_tmfsplc.PLC AND scwm_tmfscp.LGNUM = scwm_tmfsplc.LGNUM
More Yard & Material Flow tables
- /SCWM/TU_DLVTransportation unit assignments — one row per delivery or handling unit loaded onto (or unloaded from) a transportation unit for one shipping-and-receiving activity
- /SCWM/TU_SR_ACTTransportation unit activities — one row per shipping-and-receiving activity of a transportation unit, carrying the planned and actual start and end times, the activity type, category and direction, the carrier of the day, and the weighed weight
- /SCWM/TU_STATUSTransportation unit activity statuses — one row per activity per status type, with its value, the posting time, and a reason code
- /SCWM/TUNITTransportation units — the trailers, containers, and swap bodies goods are loaded into, with the internal and external number, the means of transport, the carrier, and the license plate
- /SCWM/VEH_SR_ACTVehicle activities — the same shipping-and-receiving activity shape for a vehicle: planned and actual times, activity type and direction, the driver, the carrier, and the weighed weight
- /SCWM/VEHICLEVehicles — the tractors and trucks that move transportation units through the yard, with the means of transport, carrier, license plate, and the flag that marks a permanently coupled transportation unit