Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 6 of 6

Testing outbound with sales: partial and short picks

9 min

Listen to this lesson

0:00 / 5:46

Outbound tests are integration tests by nature. A single delivery touches sales, warehouse, inventory, finance and often transportation. This lesson builds Contoso's outbound test set with Maria and Marcus, explains the evidence that proves each case, and shows how to handle the cases that most often go wrong: partial picks, short picks and late changes.

The outbound test set

IDScenarioExpected resultKey evidence
OUT-01Full order, quantity-dependent picking (48 from 0010, 2 from 0020)Three tasks from the right storage types; goods issue 50Tasks, source bins, material document, journal entry
OUT-02Wave release for route GL-NORTH with three customersOne wave; tasks and orders created at releaseWave, warehouse orders, queue
OUT-03Partial pick denial with other stock availableReplacement task from P-02-05; full quantity shipsException code, new task, count document
OUT-04Short pick with no stock anywhereDelivery split or reduced per business ruleDelivery documents, sales order backorder
OUT-05Pack at PK01 into shipping HUsHUs closed, weight and label correctHU numbers, weight, label scan
OUT-06Staging at the determined doorHUs in the DR05 staging binStaging bin, delivery order header
OUT-07Goods issue at departureMovement type 601 from 171A; billing dueMaterial document, journal entry, billing due list
OUT-08Goods issue reversal before billingDelivery and stock back to pre-issue stateReversal documents, stock
OUT-09Sales order quantity change after wave releaseDefined behavior: blocked change or adjusted tasksChange log, tasks, delivery
OUT-10Stock transport from Detroit to ChicagoOutbound from plant 1710 (EWM), receipt in plant 1720 (IM)Delivery, goods issue, receipt in 172A

Outbound test cases for warehouse 1710.

Late sales order changes are tested at each outbound stage, and the expected behavior at each stage is written down before the test.
The Sign-Off Table · thesignofftable.com/academy/sap-ewm-203

Short and partial picks are business decisions

A short pick tests more than the scanner. It asks what the business wants: replace from reserve, ship partial, hold the delivery, or cancel the rest. Write that decision into the expected result before testing, signed by Maria and Marcus together. Otherwise the test "passes" whatever the system does, and the real decision is made at 15:55 on the first busy day after go-live.

  1. Set upPrepare stock so 0010 holds one full pallet plus 18 in 02-07-1 and P-02-05 only 2, for OUT-04
  2. RunRelease the wave; picker confirms 18 at 02-07-1 with the partial pick denial code
  3. ObserveNo replacement task is possible; delivery order shows 6 open
  4. Decide per ruleGreat Lakes accepts partials: split, ship 44, 6 on a new delivery
  5. VerifyGoods issue 44; new delivery for 6; sales order shows the open 6; count document for 02-07-1
  6. ReconcileEWM and inventory management stock agree; billing for 44 only
Running the short-pick test end to end.
The Sign-Off Table · thesignofftable.com/academy/sap-ewm-203

Evidence that convinces both sides

Maria wants to see the sales view: document flow from order to delivery to billing, quantities, and the customer-facing output. Marcus wants the warehouse view: wave, warehouse orders, tasks with user and device, handling units, bins and exception codes. Dan wants the material document and journal entry. A good outbound test record holds all three, linked by delivery number, so nobody needs to rerun the test to answer a question. In SAP Cloud ALM, attach them to the test step where each was produced.

One outbound test record serves three owners, all linked by the delivery number and attached to the test step in SAP Cloud ALM.
The Sign-Off Table · thesignofftable.com/academy/sap-ewm-203
Spot checkStock transport to Chicago: a few per week, internal customer.
Test deeply onceGoods issue reversal: rare, but wrong stock and billing if it fails.
Regression setLabel reprints and packing variants: frequent, recoverable.
Every cycle, real devicesWave release, picking, short picks and goods issue for customer orders.
Where to spend outbound testing effort.
The Sign-Off Table · thesignofftable.com/academy/sap-ewm-203

What would you do?

OUT-04 (short pick with no stock) "passed" because the tester saw a delivery split. Priya reviews the evidence and finds the sales order shows no open quantity: the 6 alternators silently disappeared from the customer's order. What is the right call?

Key points
  • Outbound tests are integration tests: sales, warehouse, inventory, finance.
  • Agree short-pick and partial-delivery rules before testing and write them as expected results.
  • Evidence links the sales, warehouse and finance views by delivery number.
  • Test late sales order changes at every outbound stage.

Check your understanding · not graded

Lesson check

  1. 1. Why must short-pick rules be agreed before testing?

  2. 2. Which evidence does Dan need from an outbound test?

  3. 3. Why test sales order changes after wave release?

  4. 4. A split shipped 44 but the sales order lost the open 6. What is the test result?