EWM Reference
/SCWM/TODLV_I
CreateCreate warehouse tasks for an inbound delivery — the putaway work behind a receipt
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 scwm_ordim_o.MANDT = scwm_who.MANDT AND scwm_ordim_o.WHO = scwm_who.WHO AND scwm_ordim_o.LGNUM = scwm_who.LGNUMON scwm_ordim_o.MANDT = scwm_lagp.MANDT AND scwm_ordim_o.VLPLA = scwm_lagp.LGPLA AND scwm_ordim_o.LGNUM = scwm_lagp.LGNUMON scwm_ordim_o.MANDT = scwm_lagp.MANDT AND scwm_ordim_o.NLPLA = scwm_lagp.LGPLA AND scwm_ordim_o.LGNUM = scwm_lagp.LGNUMON scwm_ordim_o.MANDT = scdl_db_proci_i.MANDT AND scwm_ordim_o.RDOCID = scdl_db_proci_i.DOCID AND scwm_ordim_o.RITMID = scdl_db_proci_i.ITEMID -- RAW16 GUID equality — join raw; hex is for display/conformance only · applies when RDOCCAT identifies an inbound deliveryapplies when RDOCCAT identifies an inbound delivery
ON scdl_db_proch_i.MANDT = scdl_db_proci_i.MANDT AND scdl_db_proch_i.DOCID = scdl_db_proci_i.DOCID
R read · W write · R/W read + write
Primary tables
- /SCDL/DB_PROCI_IInbound delivery item — the line grain of the inbound delivery: product, batch, quantity, entitled party, and the goods-receipt and completion statusesRead accessGUID keytransaction
- /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 forWrite accessMixed keytransaction
Secondary tables
- /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 dateRead accessGUID keytransaction
- /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 fromRead accessSemantic keymaster
- /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 executionWrite accessMixed keytransaction
More Warehouse Tasks & Orders t-codes
- /SCWM/TODLV_OCreate warehouse tasks for an outbound delivery order — the picking work behind a shipment
- /SCWM/WAVEMaintain waves — group outbound delivery items into a release, then release them so warehouse tasks are created
- /SCWM/CANCPICKCancel picking — reverse picking work already created or confirmed for an outbound delivery
- /SCWM/MONThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resources
- /SCWM/TO_CONFConfirm a warehouse task — the transaction that records work as done and moves the row out of the open-task table