Skip to content
EWM Reference

/SCWM/TMFSCP

configSemantic key

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

Identity
Module: Yard & Material FlowBronze: scwm_tmfscp
Grain note

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

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.

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

18 fields · 4 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3PLCController the communication point reports toCHAR(8)
Key
4CPCommunication point — a place on the conveyor network the controller can report a handling unit atCHAR(18)
Key
5CP_TYPEType of communication pointCHAR(4)
6CPGRPCommunication point group the point belongs toCHAR(4)
7LGPLAStorage bin the point maps to — what makes a conveyor movement look like an ordinary bin movement in the task tablesCHAR(18)
8FLG_STARTWhether the point is the identification point that starts a conveyor legCHAR(1)
9FLG_ENDWhether the point ends a conveyor legCHAR(1)
10FLG_SCANWhether the point is a scanner point on the legCHAR(1)
11FLG_NIOWhether the point is a clarification bin faulted units are routed toCHAR(1)
12CP_CLARIFYCommunication point faults at this point are clarified atCHAR(18)
13LGPLA_CLFStorage bin used as the clarification binCHAR(18)
14CAPACITYCapacity of the segment behind the point, in handling unitsINT2(5)
15CAPA_MODEHow that capacity is interpretedCHAR(1)
16EXCCODE_CAPAException code raised when the segment's capacity is exceededCHAR(4)
17PROCTYPEWarehouse process type used for putaways initiated at this pointCHAR(4)
18NO_FOLLUPWhether a follow-up warehouse task is suppressed at this pointCHAR(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.

Query parameters

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

  • /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
  • /SCWM/TMFSCP/SCWM/LAGPforeign key · N:1
    ON 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 movement

    the bin behind a communication point — what makes a conveyor movement land in the task tables as an ordinary bin movement

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.