EWM Reference
/SCWM/TO_CONF
ChangeConfirm a warehouse task — the transaction that records work as done and moves the row out of the open-task table
Notes
The transaction behind the open/confirmed split: after confirmation the task is written to the confirmed table and no longer appears in the open one, which is why throughput analysis reads both. Exceptions raised here are what put a task into the log table instead.
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_c.MANDT = scwm_who.MANDT AND scwm_ordim_c.WHO = scwm_who.WHO AND scwm_ordim_c.LGNUM = scwm_who.LGNUMON scwm_ordim_l.MANDT = scwm_who.MANDT AND scwm_ordim_l.WHO = scwm_who.WHO AND scwm_ordim_l.LGNUM = scwm_who.LGNUM
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 timeWrite 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/write accessMixed keytransaction
Secondary tables
- /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 rowWrite accessGUID keytransaction
- /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 foundWrite 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/write accessMixed keytransaction
More Warehouse Tasks & Orders t-codes
- /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
- /SCWM/MONThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resources