SAP EWM Short Picking: Trace Delivery and Task Quantities

A picker confirms fewer units than an outbound delivery requests. Before changing the delivery or creating more warehouse work, establish what was requested, what was actually confirmed, and what remains unresolved. Short picking is a useful diagnostic exercise because it touches stock, warehouse tasks and delivery processing without making those records interchangeable.

The following fictional example is suitable for learners considering SAP EWM training in Vizag. Exact screens, exception handling and permitted follow-up actions depend on the warehouse design, system release and configuration.

Separate the three quantities

An outbound delivery item requests 50 units. Warehouse task confirmation records a pick of 40 units. For the example, 50 − 40 = 10 units of delivery demand remain unresolved. The difference is a quantity to investigate, not proof of the reason for the shortage.

Fictional delivery request and confirmed pick quantities
Record or comparisonQuantityMeaning
Delivery request50 unitsDemand to fulfil
Confirmed pick40 unitsRecorded picked quantity
Unresolved difference10 unitsDemand requiring review

For a real item, first ensure all quantities use comparable units. A carton, a case and an individual piece may represent different quantities. Apply the material’s valid conversion before calculating a shortage.

Warehouse tasks and warehouse orders answer different questions

A warehouse task records a particular warehouse movement or activity. A warehouse order groups tasks for execution. One delivery item may relate to several tasks, and one warehouse order may contain work for multiple items. Reading only the warehouse order header cannot establish the picked quantity for this delivery item.

Inspect the relevant task items and statuses. Distinguish planned task quantity from confirmed quantity, cancelled work from active work, and replacement tasks from the original task. Otherwise, adding every visible row can count the same demand twice.

Investigate the source stock

  1. Identify the source bin and the material associated with the short confirmation.
  2. Check batch requirements and the batch actually selected.
  3. Compare required units with the stock units and their conversions.
  4. Inspect stock status and whether the stock is eligible for this outbound process.
  5. Read the recorded exception or confirmation message.

Ten units visible elsewhere in the warehouse are not automatically ten usable units. They may belong to a different batch, be unavailable for the required process, or be recorded in a different stock category. A physical count and system record can also disagree; investigate that discrepancy through the warehouse’s approved procedure.

Choose between additional picking and an approved shortage

If eligible stock exists and the process permits further picking, an authorised user may arrange additional work for the remaining 10 units. Confirm whether open tasks already cover that quantity before creating another task. The useful check is that intended additional demand is covered once.

If eligible stock does not exist, the warehouse may need an approved shortage process, a delivery adjustment or another agreed fulfilment decision. Which action is available depends on the business process. Do not assume a short confirmation automatically adjusts the delivery or authorises shipping the reduced quantity.

Keep picking, packing and goods issue separate

A confirmed pick records a picking event. Packing records how goods are assigned to packaging or handling units. Goods issue records the relevant outbound stock event. Completion at one stage is not evidence that the later stages have completed correctly.

In this example, the confirmed 40 units do not establish that 40 units have been packed or issued. Read those records independently. If the business approves shipping 40, verify that the delivery, packing quantities and goods-issue process reflect that decision before treating the order as resolved.

A small reconciliation to practise

Create one row for the delivery item and separate columns for requested quantity, active task quantity, confirmed picked quantity, packed quantity and issued quantity. Add references for the supporting documents. Explain why a 50-unit request and a 40-unit pick leave 10 unresolved, while avoiding a claim about downstream status that the records do not support.

Common question: should I just create a new task for 10 units?

Only after checking existing tasks, eligible stock and the permitted follow-up process. An additional task can be appropriate, but it can also duplicate open work or point to unsuitable stock. The task list and delivery history provide the evidence for that decision.

Remaining quantity and difference quantity need different follow-up

SAP’s documentation for manual product warehouse task confirmation distinguishes a remaining quantity from a difference quantity. In the documented flow, a remaining quantity stays open, while confirmation with a difference quantity and an exception code closes the whole task. Confirm the equivalent behaviour in your release before applying it. A closed task therefore does not, by itself, prove that the full delivery demand was physically picked.

For the 50-unit example, write down whether the screen records 40 actual plus 10 remaining, or 40 actual plus 10 difference. The arithmetic is identical, but the work status can differ. Keep that distinction in the handover note so the next person knows whether to inspect existing open work or an exception outcome.

Worked example: split tasks without double counting

Imagine the delivery is supplied from two bins. Task A targets 30 pieces and is confirmed for 30. Task B targets 20 pieces but records only 10 picked. The delivery has 40 picked pieces in total. Its unresolved demand is still 10 pieces, even though neither task has an original target of 50.

After investigation, the warehouse creates authorised replacement work for the missing 10 from another eligible bin. Before counting that as progress, record its status. An open replacement task is a plan; a confirmed replacement task provides the additional picking evidence. Once that task is confirmed for 10, the total picked quantity becomes 30 + 10 + 10 = 50. Retain the original exception in the history rather than treating it as another physical pick.

Diagnose the shortage using evidence

  • Stock exists but cannot be selected: compare the required batch and stock attributes with the available stock, then inspect the selection message. Record the actual restriction before proposing a change.
  • The bin is physically short: record what the picker counted and the system quantity at that time. Ask the responsible warehouse team to investigate through its discrepancy process.
  • Another task already covers the shortage: capture the task number, quantity and status. Coordinate its execution instead of creating duplicate work.
  • Quantities disagree between screens: check units, item references, refresh time and split items first. Compare the same delivery item at the same process stage.

A useful handover is specific: “Delivery item requests 50 EA; confirmed picking totals 40 EA; task B records a 10 EA difference; replacement task C is open for 10 EA.” Add the actual document references, observation time and responsible person. This gives the next shift an actionable starting point.

More short-picking questions

Does a difference of 10 always mean stock is missing?

No. It describes the gap in the selected comparison. Wrong units, unsuitable stock, incomplete work or a physical discrepancy require different evidence. Find the reason before changing stock records.

Can the customer receive only the 40 picked units?

That depends on the agreed fulfilment process and delivery controls. Picking alone is insufficient approval. Record the commercial decision and verify the resulting delivery, packing and goods-issue quantities.

What should a learner demonstrate in an interview?

Explain the document chain, show the quantity calculation and identify the next check. A strong answer can explain why task completion, delivery fulfilment and shipment completion are separate conclusions.

Official SAP references

Use SAP’s Confirmation of Product Warehouse Tasks documentation for the remaining-versus-difference distinction and the Using Mobile Devices lesson for execution examples. Match documentation versions and exception settings to your own warehouse.

Continue learning

EWM warehouse orders and tasks; EWM outbound picking, packing and goods issue. Explore the linked course page for the current training information.

Leave a Comment

Your email address will not be published. Required fields are marked *