Picking Fundamentals: Purpose, Documents, and Process Flow
Introduces why picking exists as a distinct warehouse step, the documents that drive it (transfer orders vs warehouse tasks), and the end-to-end flow from outbound delivery to goods issue.
Explanation
Picking is the physical and system process of removing specified quantities of material from storage bins so they can be packed, staged, and shipped or consumed. It sits between demand creation (a sales order, stock transport order, or production order that generates an outbound delivery) and goods issue. Without a controlled picking process, warehouses risk shipping wrong quantities, wrong batches, or wrong storage bins being depleted incorrectly, which cascades into inventory inaccuracy and customer complaints. In classic ECC Warehouse Management (WM), picking is executed through Transfer Orders (TOs). A TO is created with reference to a delivery (or other source document) and instructs a warehouse worker to move stock from a source storage bin to a destination, typically a staging area or a picking-to-goods-issue interim area. The TO carries source storage type, source bin, quantity, and unit of measure, and its confirmation triggers the actual stock movement in WM and, depending on configuration, posts goods issue automatically or requires a separate GI step. In EWM (embedded in S/4HANA or decentralized), the equivalent document is the Warehouse Task (WT). Warehouse tasks are more granular and flexible than WM transfer orders: they can be generated from Warehouse Requests derived from deliveries, and they support more sophisticated determination logic (storage type search, quantity classification, resource determination) baked into EWM's own customizing rather than reusing pure WM movement types. The generic process flow is: outbound delivery created → picking-relevant document generated (TO or WT) → wave or group assignment (optional, covered in the next lesson) → picker receives instructions (paper, RF gun, pick list) → picker travels to bin, picks quantity → confirms pick (full, partial, or with difference) → stock moves to interim/staging location → packing (if applicable) → goods issue posts, reducing warehouse and company code stock. A critical beginner-level distinction is between picking quantity confirmation and goods issue posting. Confirming a TO/WT tells the system the physical pick happened; it does not necessarily mean stock has left the plant/company code. Goods issue is typically a separate step (either automatic upon TO confirmation, or manual/batch later), and understanding this separation prevents confusion when inventory reports show stock 'in transit' within the warehouse (in an interim storage type) even though picking is complete. Picking can be single-order (one TO/WT per delivery) or multi-order via waves/groups, and it can target different storage types depending on where stock resides: fixed bins, random high-rack storage, or fast-moving pick faces. Understanding these fundamentals is essential before moving into strategy configuration, because the strategy determines which bin the system proposes for picking, not whether picking happens. Finally, picking differs by deployment: in ECC WM, picking logic is tightly coupled to movement types and storage type search sequences defined in customizing tables; in EWM, picking is governed by Process-Oriented Storage Control (POSC) and warehouse process types, giving more flexibility for parallel processing steps like quality inspection or value-added services integrated into the pick sequence.
Real project scenario
A mid-size distribution company running ECC WM was experiencing frequent short-picks because pickers were being directed to bins that had been counted as available but were physically empty due to a cycle count backlog. The consulting team traced the issue to the TO creation logic pulling from a storage type that hadn't been re-synced after a count discrepancy correction. The fix involved adjusting the count frequency for that storage type and adding a check step before wave release to flag bins with pending count discrepancies, reducing short-picks by a significant margin over the following month.
Common mistakes
• Assuming TO/warehouse task confirmation always equals goods issue, leading to incorrect assumptions about stock availability downstream • Not distinguishing between quantity picked and quantity confirmed when differences occur, causing reconciliation issues • Overlooking that picking documents can target multiple storage types in one delivery, causing confusion when a single delivery generates multiple TOs/WTs • Ignoring the interim storage type/area concept, resulting in stock appearing 'lost' between pick and goods issue • Treating EWM warehouse tasks as functionally identical to WM transfer orders without accounting for POSC differences
Best practices
• Always confirm whether the deployment is ECC WM or EWM before describing document flow, since terminology and structures differ • Map interim storage types/areas explicitly in solution documentation so support teams understand where 'picked but not issued' stock sits • Validate that goods issue automation settings (auto-GI on TO confirmation vs manual) match business expectations before go-live • Include short-pick and quantity difference handling in initial process design rather than treating it as an afterthought • Document the mapping between delivery item, TO/WT, and storage bin for traceability during audits
Interview angle
Interviewers commonly ask candidates to explain the difference between transfer order confirmation and goods issue, and to describe what document drives picking in ECC WM versus EWM. Be ready to explain the role of interim storage areas/types and why stock can be 'picked but not yet issued.' A strong answer also mentions that EWM warehouse tasks are generated from warehouse requests, not directly from deliveries, showing awareness of the layered document model in EWM versus the more direct TO-delivery link in WM.