EWM Reference
All SAP EWM Tables
Every table in the reference, sorted alphabetically by namespace. Use the jump-bar to skip to a letter, or filter by module, data class, and key model.
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
In field listings, the Key chip marks a primary-key field, and UTC marks a timestamp stored in UTC rather than warehouse-local time.
FilterShowing 68 of 68 tables
Module
Tables starting with A
Tables starting with B
Tables starting with D
- /SCDL/DB_DATEDelivery dates — the typed date table for the /SCDL layer, one row per document, item, schedule line, date type, and category, each carrying a from/to timestamp pairMixed keytransactiondelivery-processing
- /SCDL/DB_DLVH_OFinal outbound delivery header — the document that exists after goods issue, carrying the shipped delivery's number, type, incoterms, sales organization, and the flags that mark corrections, pickups, and scrappingGUID keytransactiondelivery-processing
- /SCDL/DB_DLVI_OFinal outbound delivery item — the shipped line, carrying its own item GUID plus the reference document and item it was created from in both GUID and readable formGUID keytransactiondelivery-processing
- /SCDL/DB_HUDelivery handling units — the HUs attached to a delivery document, with the readable HU number, the packaging material, and the packaging specification and packing instruction that built themGUID keytransactiondelivery-processing
- /SCDL/DB_HUIDENTAlternative handling unit identifiers — the other numbers an HU is known by, one row per identifier typeMixed keytransactiondelivery-processing
- /SCDL/DB_HUITEMDelivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unitMixed keytransactiondelivery-processing
- /SCDL/DB_HUREFHUDelivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing elseGUID keytransactiondelivery-processing
- /SCDL/DB_PROCH_IInbound delivery header — the EWM-side inbound delivery document with its readable number, type, warehouse, vendor and carrier parties, status, and delivery dateGUID keytransactiondelivery-processing
- /SCDL/DB_PROCH_OOutbound delivery order header — the EWM-side outbound document with its readable number, type, warehouse, ship-to and carrier parties, route, and sales organizationGUID keytransactiondelivery-processing
- /SCDL/DB_PROCI_IInbound delivery item — the line grain of the inbound delivery: product, batch, quantity, entitled party, and the goods-receipt and completion statusesGUID keytransactiondelivery-processing
- /SCDL/DB_PROCI_OOutbound delivery order item — the line grain outbound: product, quantity, entitled party, stock owner, and the picking and goods-issue statusesGUID keytransactiondelivery-processing
- /SCDL/DB_REFDOCReference documents — the bridge from an EWM delivery document to the document that caused it in the connected ERP system, with the readable reference number and itemMixed keytransactiondelivery-processing
- /SCDL/DB_REQHDelivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)GUID keytransactiondelivery-processing
- /SCDL/DB_REQIDelivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled partyGUID keytransactiondelivery-processing
- /SCDL/DB_STATUSDelivery status — the long, narrow status table every /SCDL document writes into, one row per document or item per status type with its value and validity windowMixed keytransactiondelivery-processing
- /SCWM/DOOR_SRACTDoor activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy windowMixed keytransactionyard-mfs
Tables starting with H
Tables starting with L
- /SCWM/LAGPThe storage bin master — one row per bin in a warehouse, with its storage type and section, the three block indicators, capacity limits, empty/full flags, and the layout coordinates the pick path is built fromSemantic keymasterstorage-bins
- /SCWM/LAGPSBin assignments to activity areas — one row per bin per activity, carrying the sort sequence that determines the order an operator walks the binsSemantic keyconfigstorage-bins
Tables starting with M
- /SAPAPO/MATKEYThe product master key table — the bridge between the internal product GUID every EWM table carries and the readable material number, with the base unit, weights, volumes, and shelf-life controlGUID keymastermaster-data
- /SAPAPO/MATLWHWarehouse product — the warehouse-level settings for a product: putaway and stock-removal control, storage section and bin type indicators, stock determination, two-step picking relevance, and the slotting demand quantityGUID keymastermaster-data
- /SAPAPO/MATLWHSTWarehouse product at storage-type level — the same product's parameters narrowed to one storage type: preferred section and bin type, maximum fixed bins, and the min/max/replenishment quantity setMixed keymastermaster-data
Tables starting with N
- /LIME/NQUANThe LIME stock quantities table — the physical quantity of a stock item hanging on one node of the location/handling-unit tree, one row per stock GUID per node per unit of measureMixed keytransactionstock-hu
- /LIME/NTREEThe LIME tree structure — one row per node of the location and handling-unit hierarchy stock hangs on, with its object type, its parent node, and the nested-set interval bookkeeping the engine walks the tree withMixed keytransactionstock-hu
Tables starting with O
- /SCWM/ORDIM_CConfirmed warehouse tasks — the same movement after execution, carrying the actual quantity, the confirmation timestamp, and (with the creation stamp) the task cycle timeMixed keytransactionwarehouse-tasks
- /SCWM/ORDIM_LWarehouse task log — the historical record of tasks that left the open table without a normal confirmation; generally where cancelled and logged tasks are foundMixed keytransactionwarehouse-tasks
- /SCWM/ORDIM_OOpen warehouse tasks — the work still to be done: source and destination bin, product, target quantity, process type, queue, and the delivery item the move was created forMixed keytransactionwarehouse-tasks
Tables starting with P
- /LIME/PI_DOC_ITPhysical inventory document item — the countable line: its type and status, when it was created, counted, and posted, who counted it, the physical inventory area it belongs to, and the completeness flags that say whether a bin or handling unit was counted wholeMixed keytransactionphysical-inventory
- /LIME/PI_DOC_TBPhysical inventory quantities — the book and counted quantities behind a document item, one row per quantity parameter per unit of measureMixed keytransactionphysical-inventory
- /LIME/PI_IT_BIZPhysical inventory item business keys — the readable stock identity behind a document item: product, batch, stock type, owner and entitled party, plus the location and handling unit the stock was counted inMixed keytransactionphysical-inventory
- /LIME/PI_LOGHEADPhysical inventory document header — the log header that resolves a counting document's GUID to its readable year and number, its process type, and the warehouse it was raised forGUID keytransactionphysical-inventory
- /LIME/PI_PAR_BIZPhysical inventory parent business keys — the readable location behind a document item's parent object: warehouse, storage type, bin, handling unit, resource, or transportation unitMixed keytransactionphysical-inventory
- /SCWM/PNPAKHPackaging specification header — the packing recipe as an iPPE node, with its status, the time it was activated, its group, and the rounding limits that decide how demand quantities are rounded to whole packsMixed keymastermaster-data
- /SCWM/PVPAKCPackaging specification content — what is packed at a level: the product, the quantity and unit, and the mixing rules that say whether different products or batches may share the packMixed keymastermaster-data
- /SCWM/PVPAKLPackaging specification element — one level of the packing recipe as an iPPE variant: what packaging material is used, how much of it, and whether the level creates a handling unitMixed keymastermaster-data
Tables starting with Q
Tables starting with R
Tables starting with T
- /SCMB/TOENTITYSupply chain unit header — the location object EWM resolves warehouse, door, and party GUIDs against, carrying the readable identifier, the time zone, and the geo-coordinatesGUID keymastermaster-data
- /SCWM/T300The warehouse number definition — one row per EWM warehouse, the four-character key every structure, bin, stock, and task row is striped bySemantic keyconfigwarehouse-structure
- /SCWM/T300_MDWarehouse-to-party assignment — the supply chain unit the warehouse maps to plus the default entitled-to-dispose and ship-to partiesMixed keyconfigwarehouse-structure
- /SCWM/T300TWarehouse number descriptions — one row per warehouse per language; the readable name behind LGNUMSemantic keytextwarehouse-structure
- /SCWM/T301Storage type definition — one row per storage type in a warehouse; the first level of structure below the warehouse numberSemantic keyconfigwarehouse-structure
- /SCWM/T301GStorage type groups — the grouping of storage types that share one stock-removal rule, putaway rule, and maximum-quantity checkSemantic keyconfigwarehouse-structure
- /SCWM/T301MStorage type group assignment — which storage types belong to a group and in what sequence they are searchedSemantic keyconfigwarehouse-structure
- /SCWM/T301TStorage type descriptions — one row per storage type per languageSemantic keytextwarehouse-structure
- /SCWM/T302Storage sections — the subdivision of a storage type used to group bins for putaway strategySemantic keyconfigwarehouse-structure
- /SCWM/T303Storage bin types — the weight, volume, capacity, and packing-dimension limits a bin of each type acceptsSemantic keyconfigstorage-bins
- /SCWM/T331Storage type control — the behavior of a storage type: its role, whether handling units are mandatory, the capacity check method and availability group, the putaway and stock-removal rules, replenishment level and tolerance, and the mixing rules that decide what may share a binSemantic keyconfigwarehouse-structure
- /SCWM/T346Queue definition — the execution queues warehouse tasks, warehouse orders, and resources are routed through, with the operating environment each queue serves and the material-flow controller behind it where the queue drives automationSemantic keyconfigresources
- /SCWM/T346TQueue descriptions — one row per queue per language; the readable name behind a queue codeSemantic keytextresources
- /SCWM/TAAREAActivity area definition — the execution-oriented grouping of bins that warehouse-order creation and pick-path sorting work againstSemantic keyconfigwarehouse-structure
- /SCWM/TDOORDoors — the loading and unloading points of the warehouse, each mapped to a bin, a default staging area, and (where a yard exists) the matching yard binMixed keyconfigwarehouse-structure
- /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 toSemantic keyconfigyard-mfs
- /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 transferSemantic keyconfigyard-mfs
- /SCWM/TRSRC_GRPResource groups — the grouping of resources that share a queue sequence; three columns, all keySemantic keyconfigresources
- /SCWM/TRSRC_TYPResource 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 aislesSemantic keyconfigresources
- /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 activityMixed keytransactionyard-mfs
- /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 weightMixed keytransactionyard-mfs
- /SCWM/TU_STATUSTransportation unit activity statuses — one row per activity per status type, with its value, the posting time, and a reason codeSemantic keytransactionyard-mfs
- /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 plateMixed keymasteryard-mfs
- /SCWM/TWORKSTWork centers — the packing, deconsolidation, value-added-service, and counting stations in the warehouse, each modeled as a storage type and binMixed keyconfigwarehouse-structure
Tables starting with V
- /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 weightMixed keytransactionyard-mfs
- /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 unitMixed keymasteryard-mfs
Tables starting with W
- /SCWM/WAVEHDRWave header — the planned release of outbound work, with its template, type, cutoff and release times, and the planned picking and loading completion timesSemantic keytransactionwarehouse-tasks
- /SCWM/WAVEITMWave item — one delivery item assigned to a wave, with the task-creation status that says whether the wave actually produced work for itMixed keytransactionwarehouse-tasks
- /SCWM/WHOWarehouse order header — the bundle of tasks one operator executes as a unit, with the creation rule that produced it, the wave it came from, its queue, activity area, assigned resource, and the timestamps that bound executionMixed keytransactionwarehouse-tasks