Skip to content
EWM Reference

/SCWM/TRSRC_TYP

configSemantic key

Resource types — the physical characteristics of a class of resource: travel velocities and their unit, position management, RF task-interleaving behavior, and the layout type used for automated aisles

Identity
Module: Resources & RF ExecutionBronze: scwm_trsrc_typ
Notes

The velocities are what turn a bin-to-bin distance into an expected travel time, which makes this table the configuration side of any labor or travel-time analysis built on the task tables. A separate vertical velocity exists because high-bay equipment moves at different speeds along and up the aisle. Two interleaving flags are curated here as activation switches only: the general one is typed on an MFS-namespaced data element and the page does not state which movements it governs, while the second is explicitly the RF-side suppression.

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 numberCHAR(4)
Key
3RSRC_TYPEResource type — the class of equipment or operator a resource belongs toCHAR(4)
Key
4VELOCITYHorizontal travel velocity of the resource type — the input that turns a bin-to-bin distance into an expected travel timeQUAN(5,2)
5VELOCITY_ZVertical travel velocity, for equipment that also moves up the aisleQUAN(5,2)
6VELOCITY_UOMUnit the two velocities are expressed inUNIT(3)
7POSTN_MNGMNTWhether the resource's position in the warehouse is tracked, and howCHAR(1)
8INTLEAVActivation flag for interleaving on the resource type — the data element is MFS-namespaced and the page does not state the scope, so read it as the switch rather than as a definition of which movements may be interleavedCHAR(1)
9NOINTERLEAVWhether interleaving is suppressed in the RF environment specificallyCHAR(1)
10RSRC_MOVE_MODEHow warehouse task confirmation is controlled for the resource typeCHAR(1)
11MFSMAXTELMaximum number of telegrams the resource type may hold, in material flow scenariosNUMC(3)
12MFS_MAX_STOCKTRANSMaximum number of stock transfers allowed in an automated aisle at onceNUMC(2)
13LAYOUT_TYPELayout type the resource type works in, used for automated aislesCHAR(4)
14RSRC_TYPE_CATCategory of the resource type — the broad class it falls intoCHAR(1)

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/TRSRC_TYPon 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/TRSRC_TYP — Resource types — the physical characteristics of a class of resource: travel velocities and their unit, position management, RF task-interleaving behavior, and the layout type used for automated aisles
-- Purpose: Column-selected read of /SCWM/TRSRC_TYP — auto-generated from field metadata
-- Grain  : One row per client + LGNUM + RSRC_TYPE
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TRSRC_TYP; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_trsrc_typ — 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.RSRC_TYPE AS "Resource type — the class of equipment or operator a resource belongs to",
  t.VELOCITY AS "Horizontal travel velocity of the resource type — the input that turns a bin-to-bin distance into an expected travel time",
  t.VELOCITY_Z AS "Vertical travel velocity, for equipment that also moves up the aisle",
  t.VELOCITY_UOM AS "Unit the two velocities are expressed in",
  t.POSTN_MNGMNT AS "Whether the resource's position in the warehouse is tracked, and how",
  t.INTLEAV AS "Activation flag for interleaving on the resource type — the data element is MFS-namespaced and the page does not state the scope, so read it as the switch rather than as a definition of which movements may be interleaved",
  t.NOINTERLEAV AS "Whether interleaving is suppressed in the RF environment specifically",
  t.RSRC_MOVE_MODE AS "How warehouse task confirmation is controlled for the resource type",
  t.MFSMAXTEL AS "Maximum number of telegrams the resource type may hold, in material flow scenarios",
  t.MFS_MAX_STOCKTRANS AS "Maximum number of stock transfers allowed in an automated aisle at once",
  t.LAYOUT_TYPE AS "Layout type the resource type works in, used for automated aisles",
  t.RSRC_TYPE_CAT AS "Category of the resource type — the broad class it falls into"
FROM <catalog>.<schema>.scwm_trsrc_typ 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/RSRC/SCWM/TRSRC_TYPforeign key · N:1
    ON scwm_rsrc.MANDT = scwm_trsrc_typ.MANDT AND scwm_rsrc.RSRC_TYPE = scwm_trsrc_typ.RSRC_TYPE AND scwm_rsrc.LGNUM = scwm_trsrc_typ.LGNUM

Transaction codes that touch this table

Curated: the EWM transactions an analyst would trace back to these rows, and how each one touches them.

R read · W write · R/W read + write

Browse more Resources & RF Execution tables

More Resources & RF Execution 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.