/SCWM/TUNIT
masterMixed keyTransportation 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
The master record carries no times and no status: a transportation unit's arrival, docking, loading, and departure all live on its shipping-and-receiving activity rows, which is the grain the yard is actually analyzed at. Three RAW16 columns tie the TU into the stock model — a location GUID and two handling-unit GUIDs — because a TU is modeled as a place goods can sit as well as a vehicle. Only one of them, HU_ID, is drawn as an edge to the handling-unit header: LIME_ID and LIME_ID_UNPACKED share their data elements with the location and HU key spaces, but nothing public states how each is populated or which object it resolves to, and a shared type is not evidence of a join — treat them as leads to verify in your own system. FIXED_VEH_NUM is the tractor or vehicle permanently coupled to the unit, where the yard works that way.
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
15 fields · 2 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | TU_NUM | Internal transportation unit number — the key the activity and assignment tables join on | CHAR(18) | Key |
| 3 | TU_NUM_EXT | External transportation unit number — what the yard and the carrier call the trailer | CHAR(20) | |
| 4 | LIME_ID | Location GUID of the transportation unit — a TU is a place stock can sit, so it exists as a location in the stock engine | RAW(16) | |
| 5 | LIME_ID_UNPACKED | Handling-unit GUID of the transportation unit in its unpacked form | RAW(16) | |
| 6 | HU_ID | Handling-unit GUID of the transportation unit — the TU seen as an HU, which is how loaded stock hangs off it | RAW(16) | |
| 7 | MTR | Means of transport the unit represents | CHAR(10) | |
| 8 | OWNER | Business partner that owns the transportation unit | CHAR(10) | |
| 9 | TSP | Carrier assigned to the transportation unit on the master record | CHAR(10) | |
| 10 | SCAC | Standard carrier alpha code of that carrier | CHAR(4) | |
| 11 | MAX_SEAL_NUM | Maximum number of seals the unit takes | INT2(5) | |
| 12 | FIXED_VEH_NUM | Vehicle permanently coupled to the unit, where the yard works with fixed pairings | CHAR(20) | |
| 13 | LIC_PLATE_CNTRY | Country or region the license plate is registered in | CHAR(3) | |
| 14 | LIC_PLATE | License plate number | CHAR(20) | |
| 15 | TU_PERMANENT | Whether the unit is permanently needed for shipping and receiving activities rather than created per visit | CHAR(1) |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TUNITon 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.
3 parameters not filled: <catalog>, <schema>, <client>
-- ============================================================
-- Table : /SCWM/TUNIT — Transportation 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
-- Purpose: Column-selected read of /SCWM/TUNIT — auto-generated from field metadata
-- Grain : One row per client + TU_NUM
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TUNIT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tunit — adjust to your landing convention (see quirks #namespace-slashes). RAW16 GUID columns are joined raw; the hex aliases are for display only (#guid-keys). Timestamps flagged UTC are DEC(15) yyyymmddhhmmss values in UTC, not warehouse local time (#utc-timestamps).
-- ============================================================
SELECT
t.MANDT AS "Client",
t.TU_NUM AS "Internal transportation unit number — the key the activity and assignment tables join on",
t.TU_NUM_EXT AS "External transportation unit number — what the yard and the carrier call the trailer",
t.LIME_ID AS "Location GUID of the transportation unit — a TU is a place stock can sit, so it exists as a location in the stock engine",
lower(hex(t.LIME_ID)) AS "Location GUID of the transportation unit — a TU is a place stock can sit, so it exists as a location in the stock engine (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.LIME_ID_UNPACKED AS "Handling-unit GUID of the transportation unit in its unpacked form",
lower(hex(t.LIME_ID_UNPACKED)) AS "Handling-unit GUID of the transportation unit in its unpacked form (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.HU_ID AS "Handling-unit GUID of the transportation unit — the TU seen as an HU, which is how loaded stock hangs off it",
lower(hex(t.HU_ID)) AS "Handling-unit GUID of the transportation unit — the TU seen as an HU, which is how loaded stock hangs off it (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.MTR AS "Means of transport the unit represents",
t.OWNER AS "Business partner that owns the transportation unit",
t.TSP AS "Carrier assigned to the transportation unit on the master record",
t.SCAC AS "Standard carrier alpha code of that carrier",
t.MAX_SEAL_NUM AS "Maximum number of seals the unit takes",
t.FIXED_VEH_NUM AS "Vehicle permanently coupled to the unit, where the yard works with fixed pairings",
t.LIC_PLATE_CNTRY AS "Country or region the license plate is registered in",
t.LIC_PLATE AS "License plate number",
t.TU_PERMANENT AS "Whether the unit is permanently needed for shipping and receiving activities rather than created per visit"
FROM <catalog>.<schema>.scwm_tunit t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
ORDER BY t.TU_NUM;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_tu_sr_act.MANDT = scwm_tunit.MANDT AND scwm_tu_sr_act.TU_NUM = scwm_tunit.TU_NUM -- many visits per transportation unit — a per-TU count is not a count of visitsmany visits per transportation unit — a per-TU count is not a count of visits
ON scwm_tunit.MANDT = scwm_vehicle.MANDT AND scwm_tunit.FIXED_VEH_NUM = scwm_vehicle.VEH_NUM -- the PERMANENT pairing only, and the two columns share a data element; the vehicle actually pulling a trailer on a given visit is not on this row — that pairing lives in the two activity tablesthe PERMANENT pairing only, and the two columns share a data element; the vehicle actually pulling a trailer on a given visit is not on this row — that pairing lives in the two activity tables
ON scwm_tunit.MANDT = scwm_huhdr.MANDT AND scwm_tunit.HU_ID = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance only · the transportation unit seen as a handling unit, which is how loaded stock hangs off itthe transportation unit seen as a handling unit, which is how loaded stock hangs off it
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
More Yard & Material Flow tables
- /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
- /SCWM/DOOR_SRACTDoor activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy window
- /SCWM/TMFSCPCommunication 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
- /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