Lesson 5 of 5
Test scope
10 min
Listen to this lesson
The warehouse option you choose decides what you must test. Inventory management only means testing stock postings. EWM means testing a whole operation: bins, tasks, devices, labels, deliveries and the hand-offs to sales, purchasing and production. This lesson gives a test map for each option that the following warehouse courses build on.
Four scenario families
- Inbound: goods receipt from a supplier such as Lakeside Components, unloading, putaway to the right bin, receipt from production.
- Outbound: picking, packing and goods issue for a customer delivery, for example alternators for Great Lakes Fleet Services.
- Internal: replenishment of picking bins, stock transfers between bins or storage types, posting changes such as quality release.
- Inventory: physical inventory counts per bin or storage location, differences and their posting.
| Scenario | Inventory management only | Embedded EWM | Decentralized EWM |
|---|---|---|---|
| Inbound | Goods receipt posting to storage location | Inbound delivery, warehouse tasks, putaway bin rules | As embedded, plus delivery transfer to the EWM system |
| Outbound | Goods issue posting for the delivery | Warehouse request, picking tasks, packing, goods issue updates delivery | As embedded, plus delivery and goods issue messages between systems |
| Internal | Transfer postings | Replenishment, bin transfers, posting changes | As embedded |
| Inventory | Count per storage location | Count per bin and handling unit | As embedded, plus stock comparison between ERP and EWM |
| Extra checks | Stock and value per storage location | Roles, RF devices, labels, printers, monitor | Master data distribution, queues, ERP downtime behavior |
Test at three levels, as in any SAP program. Unit and configuration checks prove single rules, for example that putaway for CMC-ALT-100 proposes a rack bin rather than bulk. Integration tests prove the hand-offs: a sales order from Maria's team creates a delivery that EWM picks, and the goods issue updates the delivery, inventory and finance. Acceptance tests on the warehouse floor prove that real people with real devices can run a shift. When Contoso later brings Alternadores del Norte's Monterrey plant (1910) into SAP S/4HANA, the same map applies: decide the warehouse option first, then derive the scope from it.
Things teams forget
- Devices and printers: mobile (radio frequency) screens, label layouts and printers in the warehouse, tested with real hardware.
- Roles: warehouse workers, supervisors and clerks each see only their tasks and apps.
- Data migration: bins, stock per bin and handling units loaded and reconciled against the old warehouse.
- Exceptions: short picks, damaged goods, wrong bin, cancelled delivery after picking.
- Volume: a busy shift's worth of tasks, not just one order.
- Integration: sales, purchasing, production and finance see the same stock as the warehouse.
- InboundDelivery from Lakeside Components received and put away to a rack bin
- InternalPicking bin replenished from bulk storage
- OutboundOrder from Great Lakes Fleet Services picked, packed and goods-issued
- InventoryBin count with a difference, posted and reconciled
- Finance checkStock value per plant and storage location matches the warehouse
Plan the evidence as well as the tests. For each scenario, keep the business document numbers (delivery, warehouse tasks, material document), the bins involved and the stock before and after. That evidence lets the process owner and auditors follow a pallet from the dock to the customer, which is exactly the question they will ask when something goes wrong after go-live.
What would you do?
Detroit's EWM test plan covers inbound, outbound and internal flows with one order each in the office. What is the most important gap to close before sign-off?
Exceptions per scenario family
| Family | Exception to test at Contoso | Expected handling |
|---|---|---|
| Inbound | Lakeside delivers 38 regulator kits against 40 on the inbound delivery | Difference recorded in EWM; goods receipt for 38; buyer Omar informed |
| Inbound | Pallet arrives damaged | Stock posted to blocked or quality stock, not to an available bin |
| Outbound | Short pick: bin holds 18 alternators, task asks for 20 | Exception code on confirmation; delivery quantity adjusted or remaining quantity picked from another bin |
| Outbound | Delivery 80001234 changed after picking started | Change reaches the warehouse request; picked goods returned or repacked |
| Internal | Replenishment triggered while the bulk bin is empty | No task, or exception visible in the monitor |
| Inventory | Count finds 2 pieces fewer than book in bin 02-03-1 | Difference posted in EWM, then cleared to inventory management with Marcus's approval |
Each scenario family has a few exceptions that cause most go-live problems.
- Test four scenario families: inbound, outbound, internal and inventory.
- EWM adds bins, tasks, devices, labels and roles; decentralized EWM adds system integration.
- Include exceptions, volume, data migration reconciliation and real warehouse hardware.
- Warehouse sign-off needs the process owner and evidence from the floor.
Check your understanding · not graded
Lesson check
1. Which scenario family covers replenishing a picking bin from bulk storage?
2. What extra testing does decentralized EWM need compared with embedded?
3. Why test with real devices and printers on the warehouse floor?
4. Which evidence lets an auditor follow a pallet from the bin to the customer after an outbound test?