EWM Reference
/SCWM/IDN
ChangeMaintain the inbound delivery notification — the request document that arrives from the connected ERP system before the inbound delivery exists
Tables behind this transaction
Curated: these are the tables an analyst reads to see what this transaction did, and how it touches each of them. Every table page carries its own field list and Databricks SQL.
How these tables connect — join details in the list below. GUID joins and text-table joins are highlighted.
Join details
ON scdl_db_reqh.MANDT = scdl_db_reqi.MANDT AND scdl_db_reqh.DOCID = scdl_db_reqi.DOCID
R read · W write · R/W read + write
Primary tables
- /SCDL/DB_REQHDelivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)Read/write accessGUID keytransaction
- /SCDL/DB_REQIDelivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled partyRead/write accessGUID keytransaction
Secondary tables
- /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 itemRead accessMixed 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 windowRead/write accessMixed keytransaction
More Delivery Processing (Warehouse Requests) t-codes
- /SCWM/ODRMaintain the outbound delivery request — the request document that precedes the outbound delivery order
- /SCWM/PRDIMaintain the inbound delivery — the EWM-side receipt document goods receipt is posted against
- /SCWM/PRDOMaintain the outbound delivery order — the document EWM plans, picks, and stages against before goods issue