/SCWM/MON
List / MonitorThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resources
Filed under warehouse tasks because that is where most analysts open it, but the monitor spans effectively the whole warehouse: its node tree reaches every module in this reference. When a business user says "I can see it in the monitor," this is the transaction, and the underlying rows are the ones mapped below.
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_aqua.MANDT = scwm_huhdr.MANDT AND scwm_aqua.HUIDENT = scwm_huhdr.HUIDENT AND scwm_aqua.LGNUM = scwm_huhdr.LGNUMON 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_c.MANDT = scwm_who.MANDT AND scwm_ordim_c.WHO = scwm_who.WHO AND scwm_ordim_c.LGNUM = scwm_who.LGNUMON scwm_who.MANDT = scwm_rsrc.MANDT AND scwm_who.RSRC = scwm_rsrc.RSRC AND scwm_who.LGNUM = scwm_rsrc.LGNUMON scwm_rsrc.MANDT = scwm_huhdr.MANDT AND scwm_rsrc.GUID_HU = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance only
R read · W write · R/W read + write
Primary tables
- /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 timeRead accessMixed 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 forRead accessMixed keytransaction
- /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 executionRead accessMixed keytransaction
Secondary tables
- /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 organizationRead accessGUID keytransaction
- /SCWM/AQUAAvailable quants — the stock that warehouse task creation can actually consume, with the bin, handling unit, product, stock type, batch, owner, and entitled party all resolved onto one rowRead accessGUID keytransaction
- /SCWM/HUHDRHandling unit header — one row per HU with its external number, packaging material, current storage type and bin, weights, volumes, and the entitled party whose stock it holdsRead accessGUID keytransaction
- /SCWM/RSRCResources — the operators, vehicles, and devices that execute warehouse orders, with the queue each is working, the bin it is currently at, and the handling unit it is carryingRead accessMixed keymaster
More Warehouse Tasks & Orders t-codes
- /SCWM/TO_CONFConfirm a warehouse task — the transaction that records work as done and moves the row out of the open-task table
- /SCWM/TODLV_ICreate warehouse tasks for an inbound delivery — the putaway work behind a receipt
- /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