Skip to content
EWM Reference

/SCWM/VEHICLE

masterMixed key

Vehicles — 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

Identity
Module: Yard & Material FlowBronze: scwm_vehicle
Notes

The vehicle and the transportation unit are separate objects on purpose: one tractor pulls many trailers over a day, and each pairing is its own activity. Like the TU master, this table holds no yard movements — those hang off the vehicle's own activity table. VEH_ID is the GUID the rest of the shipping-and-receiving layer identifies the vehicle by.

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

15 fields · 2 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2VEH_NUMInternal vehicle number — the key the vehicle's activity rows join onCHAR(20)
Key
3VEH_NUM_EXTExternal vehicle number — what the yard and the carrier call itCHAR(20)
4VEH_IDVehicle GUID — the identifier the rest of the shipping-and-receiving layer carriesRAW(16)
5MTRMeans of transport the vehicle representsCHAR(10)
6OWNERBusiness partner that owns the vehicleCHAR(10)
7TSPCarrier operating the vehicle on the master recordCHAR(10)
8SCACStandard carrier alpha code of that carrierCHAR(4)
9LIC_PLATE_CNTRYCountry or region the license plate is registered inCHAR(3)
10LIC_PLATELicense plate numberCHAR(20)
11FIXED_ASSIGNMENTWhether a transportation unit is permanently coupled to this vehicleCHAR(1)
12VEH_PERMANENTWhether the vehicle is permanently needed for shipping and receiving activities rather than created per visitCHAR(1)
13CREATED_BYUser who created the vehicle master recordCHAR(12)
14CREATED_ATCreation time of the vehicle master recordDEC(15)
UTCFilter date
15CHANGED_ATLast change time of the vehicle master recordDEC(15)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/VEHICLEon 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

5 parameters not filled: <catalog>, <schema>, <client>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCWM/VEHICLE — Vehicles — 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
-- Purpose: Column-selected read of /SCWM/VEHICLE — auto-generated from field metadata
-- Grain  : One row per client + VEH_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/VEHICLE; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_vehicle — 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.VEH_NUM AS "Internal vehicle number — the key the vehicle's activity rows join on",
  t.VEH_NUM_EXT AS "External vehicle number — what the yard and the carrier call it",
  t.VEH_ID AS "Vehicle GUID — the identifier the rest of the shipping-and-receiving layer carries",
  lower(hex(t.VEH_ID)) AS "Vehicle GUID — the identifier the rest of the shipping-and-receiving layer carries (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.MTR AS "Means of transport the vehicle represents",
  t.OWNER AS "Business partner that owns the vehicle",
  t.TSP AS "Carrier operating the vehicle on the master record",
  t.SCAC AS "Standard carrier alpha code of that carrier",
  t.LIC_PLATE_CNTRY AS "Country or region the license plate is registered in",
  t.LIC_PLATE AS "License plate number",
  t.FIXED_ASSIGNMENT AS "Whether a transportation unit is permanently coupled to this vehicle",
  t.VEH_PERMANENT AS "Whether the vehicle is permanently needed for shipping and receiving activities rather than created per visit",
  t.CREATED_BY AS "User who created the vehicle master record",
  t.CREATED_AT AS "Creation time of the vehicle master record",  -- UTC
  t.CHANGED_AT AS "Last change time of the vehicle master record"  -- UTC
FROM <catalog>.<schema>.scwm_vehicle t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.CREATED_AT >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.CREATED_AT <= <TS_TO>
ORDER BY t.VEH_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

  • /SCWM/VEH_SR_ACT/SCWM/VEHICLEforeign key · N:1
    ON scwm_veh_sr_act.MANDT = scwm_vehicle.MANDT AND scwm_veh_sr_act.VEH_NUM = scwm_vehicle.VEH_NUM
  • /SCWM/TUNIT/SCWM/VEHICLEforeign key · N:1
    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 tables

    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 tables

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 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.