Skip to content
EWM Reference

/SCWM/TMFSPLC

configSemantic key

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

Identity
Module: Yard & Material FlowBronze: scwm_tmfsplc
Notes

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.

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.

Fields

14 fields · 3 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse number the controller belongs toCHAR(4)
Key
3PLCProgrammable logic controller code — what the queue master's PLC column points atCHAR(8)
Key
4PROCTYPEWarehouse process type used for putaways over the conveyor — the reason automated warehouses show process types nobody chose by handCHAR(4)
5PROCTYPE_ERRWarehouse process type used when a handling unit ends up in fault handlingCHAR(4)
6PROCTYPE_ATFWarehouse process type used for movement postings raised by the material flow systemCHAR(4)
7PROCTYPE_STOCK_TRANSWarehouse process type used for stock transfers by material-flow resourcesCHAR(4)
8CL_MODECommunication layer mode EWM talks to the controller throughCHAR(1)
9RFCDSTLogical destination the telegrams are sent toCHAR(32)
10PLCIFTYPEInterface type of the controllerCHAR(1)
11PLC_MODEOperating mode the controller is inCHAR(1)
12EXCCODEException code raised when the material flow system changes a destination binCHAR(4)
13EWM_IDIdentification EWM sends as the telegram senderCHAR(8)
14LOGGINGWhether telegram traffic for this controller is loggedCHAR(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.

Query parameters

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

  • /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

  • /SCWM/TMFSCP/SCWM/TMFSPLCforeign key · N:1
    ON scwm_tmfscp.MANDT = scwm_tmfsplc.MANDT AND scwm_tmfscp.PLC = scwm_tmfsplc.PLC AND scwm_tmfscp.LGNUM = scwm_tmfsplc.LGNUM

Browse more Yard & Material Flow tables

More Yard & Material Flow 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.