EWM Reference
Delivery Processing (Warehouse Requests)
Supply chainThe /SCDL delivery layer — request and processing documents inbound and outbound, plus the shared status, reference-document, and date tables every category writes into
15 tables4 t-codes
Verified August 2026
In the business-problem map Customer Service & Fulfillment
Tables
Transaction · 15
- /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 keytransaction
- /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 keytransaction
- /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 keytransaction
- /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 keytransaction
- /SCDL/DB_HUIDENTAlternative handling unit identifiers — the other numbers an HU is known by, one row per identifier typeMixed keytransaction
- /SCDL/DB_HUITEMDelivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unitMixed keytransaction
- /SCDL/DB_HUREFHUDelivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing elseGUID keytransaction
- /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 keytransaction
- /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 keytransaction
- /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 keytransaction
- /SCDL/DB_PROCI_OOutbound delivery order item — the line grain outbound: product, quantity, entitled party, stock owner, and the picking and goods-issue statusesGUID keytransaction
- /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 keytransaction
- /SCDL/DB_REQHDelivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)GUID keytransaction
- /SCDL/DB_REQIDelivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled partyGUID keytransaction
- /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 keytransaction
Transaction Codes
The EWM transactions that work this module, each linked to the tables behind it.
- /SCWM/IDNMaintain the inbound delivery notification — the request document that arrives from the connected ERP system before the inbound delivery existsChange
- /SCWM/ODRMaintain the outbound delivery request — the request document that precedes the outbound delivery orderChange
- /SCWM/PRDIMaintain the inbound delivery — the EWM-side receipt document goods receipt is posted againstChange
- /SCWM/PRDOMaintain the outbound delivery order — the document EWM plans, picks, and stages against before goods issueChange