/SCWM/TMFSCP
configSemantic keyCommunication points — the identification points, scanners, and segments of the conveyor network a controller reports against, each mapped to a storage bin, with its capacity and the clarification point faults are routed to
Configuration with live state mixed in — the telegram columns on this table hold the last message exchanged and are overwritten continuously, so nothing here is a history of conveyor traffic
The map of the conveyor: each point is a place on the network the controller can report a handling unit at, and LGPLA ties it to a real storage bin so a conveyor movement looks like an ordinary bin movement in the task tables. The DDIC page carries 49 columns; this catalog curates the network's shape (point type, group, bin, leg flags, capacity, clarification routing) and leaves the telegram buffers, sequence numbers, and counters out — they are runtime state, not analysis. The two long-form DEC(21) telegram stamps on the page are not the DEC(15) shape this reference's timestamp convention is built for.
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
18 fields · 4 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | PLC | Controller the communication point reports to | CHAR(8) | Key |
| 4 | CP | Communication point — a place on the conveyor network the controller can report a handling unit at | CHAR(18) | Key |
| 5 | CP_TYPE | Type of communication point | CHAR(4) | |
| 6 | CPGRP | Communication point group the point belongs to | CHAR(4) | |
| 7 | LGPLA | Storage bin the point maps to — what makes a conveyor movement look like an ordinary bin movement in the task tables | CHAR(18) | |
| 8 | FLG_START | Whether the point is the identification point that starts a conveyor leg | CHAR(1) | |
| 9 | FLG_END | Whether the point ends a conveyor leg | CHAR(1) | |
| 10 | FLG_SCAN | Whether the point is a scanner point on the leg | CHAR(1) | |
| 11 | FLG_NIO | Whether the point is a clarification bin faulted units are routed to | CHAR(1) | |
| 12 | CP_CLARIFY | Communication point faults at this point are clarified at | CHAR(18) | |
| 13 | LGPLA_CLF | Storage bin used as the clarification bin | CHAR(18) | |
| 14 | CAPACITY | Capacity of the segment behind the point, in handling units | INT2(5) | |
| 15 | CAPA_MODE | How that capacity is interpreted | CHAR(1) | |
| 16 | EXCCODE_CAPA | Exception code raised when the segment's capacity is exceeded | CHAR(4) | |
| 17 | PROCTYPE | Warehouse process type used for putaways initiated at this point | CHAR(4) | |
| 18 | NO_FOLLUP | Whether a follow-up warehouse task is suppressed at this point | CHAR(1) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TMFSCPon 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/TMFSCP — Communication points — the identification points, scanners, and segments of the conveyor network a controller reports against, each mapped to a storage bin, with its capacity and the clarification point faults are routed to
-- Purpose: Column-selected read of /SCWM/TMFSCP — auto-generated from field metadata
-- Grain : One row per client + LGNUM + PLC + CP
-- Caution: Configuration with live state mixed in — the telegram columns on this table hold the last message exchanged and are overwritten continuously, so nothing here is a history of conveyor traffic
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TMFSCP; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tmfscp — 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",
t.PLC AS "Controller the communication point reports to",
t.CP AS "Communication point — a place on the conveyor network the controller can report a handling unit at",
t.CP_TYPE AS "Type of communication point",
t.CPGRP AS "Communication point group the point belongs to",
t.LGPLA AS "Storage bin the point maps to — what makes a conveyor movement look like an ordinary bin movement in the task tables",
t.FLG_START AS "Whether the point is the identification point that starts a conveyor leg",
t.FLG_END AS "Whether the point ends a conveyor leg",
t.FLG_SCAN AS "Whether the point is a scanner point on the leg",
t.FLG_NIO AS "Whether the point is a clarification bin faulted units are routed to",
t.CP_CLARIFY AS "Communication point faults at this point are clarified at",
t.LGPLA_CLF AS "Storage bin used as the clarification bin",
t.CAPACITY AS "Capacity of the segment behind the point, in handling units",
t.CAPA_MODE AS "How that capacity is interpreted",
t.EXCCODE_CAPA AS "Exception code raised when the segment's capacity is exceeded",
t.PROCTYPE AS "Warehouse process type used for putaways initiated at this point",
t.NO_FOLLUP AS "Whether a follow-up warehouse task is suppressed at this point"
FROM <catalog>.<schema>.scwm_tmfscp 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_tmfscp.MANDT = scwm_tmfsplc.MANDT AND scwm_tmfscp.PLC = scwm_tmfsplc.PLC AND scwm_tmfscp.LGNUM = scwm_tmfsplc.LGNUMON scwm_tmfscp.MANDT = scwm_lagp.MANDT AND scwm_tmfscp.LGPLA = scwm_lagp.LGPLA AND scwm_tmfscp.LGNUM = scwm_lagp.LGNUM -- the bin behind a communication point — what makes a conveyor movement land in the task tables as an ordinary bin movementthe bin behind a communication point — what makes a conveyor movement land in the task tables as an ordinary bin movement
More Yard & Material Flow tables
- /SCWM/TMFSPLCProgrammable 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
- /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