Lesson 6 of 6
Testing warehouse master data with probe tasks
9 min
Listen to this lesson
Warehouse master data is tested by watching what the system does with it. A bin list that looks right in a spreadsheet can still send pallets to the wrong aisle. The practical method is the probe task: create a warehouse task for a known product and quantity, read the source and destination the system proposes, compare with the design, and then confirm or cancel the task. Done systematically, probe tasks prove the structure, product data, packaging and resource setup before any end-to-end test.
- BuildStructure and binsStorage types, sections, bins generated, bin sorting run; counts reconciled to the layout drawing
- LoadProduct dataWarehouse products with indicators, min/max, packaging specifications and condition records
- ProbePutaway probesOne probe task per product family and storage type path; record proposed bins
- ProbeRemoval probesPicking probes against fixed bins and reserve; record source bins
- AssignResource probesEach real user logs on with the real device and receives work from the expected queue
- SignMaster data sign-offMarcus signs the master data readiness before integration testing starts
What a putaway probe tests
When EWM creates a putaway task, it takes quantities from handling units or the packaging specification, determines the storage type search sequence, optionally searches sections and bin types, applies the putaway rule of each storage type (empty bin, addition to existing stock, fixed bin, bulk and others) and optionally checks capacity. If no bin is found in one storage type, it moves to the next in the sequence. A probe tells you whether each of those steps behaves as designed.
| Probe | Expected result (Contoso design) | Evidence |
|---|---|---|
| 1 pallet CMC-ALT-100 (24 pc), standard receipt | Empty bin in 0010, fast-mover section (aisles 01–02) | Task with destination bin; bin before and after |
| 48 pc CMC-ALT-100 | Two tasks of 24 each, two different 0010 bins | Two tasks; packaging specification determined |
| 0010 fast-mover section full (test data prepared) | Next section or next storage type 0030 per sequence | Task destination in fallback area |
| 3 pallets CMC-RGL-050 | Bulk floor 0030, existing row for the product | Task to the row bin; quant count in the row |
| Product with no warehouse product | Error or fallback per design, never a silent wrong bin | Error message or fallback documented |
Putaway probes for warehouse 1710.
Probe tasks are usually created as ad hoc warehouse tasks (for example with /SCWM/ADPROD for products or /SCWM/ADHU for handling units) using the putaway warehouse process type, or through a real inbound delivery in the test client. Use the same warehouse process type the real process uses: the process type is itself an input to the search sequence, so a probe with a different type proves nothing about the real flow.
Removal and resource probes
Removal probes create picking tasks and check the source bin: fixed bin 0020 first for CMC-ALT-100, reserve 0010 only when the fixed bin is empty. Resource probes are human: each picker and driver logs on with their own user and device and must receive work from the expected queue. Record the user, resource, queue and warehouse order number.
- Is the proposed storage type wrong?Yes → check putaway control indicator, process type and the search sequence entry · No → next
- Is the storage type right but the section wrong?Yes → check section indicator and section search activation · No → next
- Is the section right but the bin wrong or not found?Yes → check the putaway rule, bin type, capacity and existing quants · No → next
- Is the quantity per task wrong?Yes → check the packaging specification and its condition record · No → probe passes
What would you do?
Kenji's team wants to save time by testing putaway with a generic test product that has every indicator filled. Priya objects. Who is right?
- A probe task shows what the system does with the master data; compare its proposal with the design.
- Use the real warehouse process type and real products, or the probe proves nothing about production.
- Triage failures in order: storage type, section, bin, quantity.
- Resource probes need real users on real devices receiving work from the expected queues.
Check your understanding · not graded
Lesson check
1. Why must a putaway probe use the same warehouse process type as the real process?
2. A probe proposes the right storage type but the wrong section. What do you check?
3. What evidence best shows a putaway probe passed?
4. Probe results show the right bin but tasks of 48 instead of 24. Where do you look?