Lesson 1 of 6
Coverage: mapping warehouse scenarios and exceptions
10 min
Listen to this lesson
A warehouse test plan fails in one of two ways. Either it tests the happy path of every process and misses the exceptions that happen fifty times a day, or it drowns in variants nobody uses. This course builds the test and sign-off plan for Contoso Motor Co.'s Detroit warehouse (EWM warehouse number 1710), which moves from classic warehouse management in ECC to embedded EWM as part of the SAP S/4HANA conversion. The first job is coverage: a map of what must be proven before Marcus, the warehouse manager and process owner, can sign.
Start from processes, not transactions
Coverage starts with the business processes in scope, grouped into four families: inbound, outbound, internal and inventory. SAP Best Practices for embedded EWM organize scope items the same way, with items for inbound processing from suppliers, outbound processing to customers, physical inventory, replenishment, scrapping and the initial stock upload. Scope item names and numbers vary by release, so use SAP Signavio Process Navigator for your release as a checklist, then tailor it to what Contoso actually does. In SAP Cloud ALM, the solution processes in scope become the backbone of test preparation: test cases are created from process activities and linked back to them.
Add the exceptions deliberately
For each process, list what goes wrong on the floor and how often. Exceptions are not edge cases in a warehouse; a 2% pick denial rate on 1,200 lines a day is 24 exceptions daily. The courses on inbound, outbound and internal processes (sap-ewm-202 to sap-ewm-204) list the exception codes; the coverage map decides which ones are tested, how, and with what evidence.
| Process | Main exceptions to cover | Why it matters |
|---|---|---|
| Supplier receipt | Short delivery, over-delivery, damage, wrong product, bin full | Stock and supplier liability |
| Putaway | Overflow to the next storage type, bin blocked, breakage | Stock accuracy, FIFO |
| Picking | Partial and full pick denial, no stock anywhere | Customer shipments |
| Packing and staging | Wrong door, label reprint, weight mismatch | Carrier and customer receiving |
| Goods issue | Partial shipment, early posting and reversal | Billing and finance |
| Counting | Recount, offsetting differences, above-tolerance difference | Financial statements |
Exceptions the Contoso coverage map includes.
Prioritize by risk
Contoso's map has 64 warehouse test cases: 18 inbound, 22 outbound, 12 internal and 12 inventory, plus cross-cutting RF and volume checks. Priya, the test lead, links each to its solution process in SAP Cloud ALM so that coverage can be reported per process, not as a raw count of passed scripts.
What one line of the coverage map looks like
| ID | Process and variant | Exception | Data and devices | Evidence | Cycle |
|---|---|---|---|---|---|
| IB-04 | Supplier receipt with ASN: Lakeside regulator kits CMC-RGL-050 | Short delivery: 38 of 40 | Inbound delivery from ASN; handheld RF-07; dock door 3 | Inbound delivery, difference record, GR material document into 171R, putaway task to 171A | Every cycle |
| IB-09 | Receipt from production: CMC-ALT-100 from 171B | Bin full in the high-rack | Production order 1001200 receipt; forklift terminal | Putaway task with overflow bin, stock in 171A | Cycles 2 and 3 |
| OB-03 | Wave picking for sales order 1000457 / delivery 80001234 | Partial pick denial | Wave in the PM release; picker role | Warehouse tasks with exception code, delivery quantity, goods issue | Every cycle |
| IN-07 | Cycle count, A products in 0020 | Above-tolerance difference | PI area 0020; two counters | PI document, recount, analyzer entry, cleared 711 document | Cycles 2 and 3 |
Four lines from Contoso's warehouse coverage map: each names the variant, the exception, the data, the evidence and how often it runs.
- Map coverage by process family: inbound, outbound, internal, inventory, plus cross-cutting items.
- Use SAP Best Practices scope items for your release as a checklist, then tailor.
- Add exceptions deliberately; in a warehouse they are daily events.
- Prioritize by frequency and impact, and link test cases to processes in SAP Cloud ALM.
Check your understanding · not graded
Lesson check
1. Why are warehouse exceptions part of core coverage rather than edge cases?
2. Where should Contoso check the SAP Best Practices EWM scope items for its release?
3. Wave picking with short picks is frequent and high impact. How is it tested?
4. Why rewrite expected results from Contoso's classic WM suite?
5. Why does Contoso report warehouse coverage per process and exception rather than as a pass rate?