Picking and PGI Fundamentals: Business Purpose and Process Flow
Introduces why picking and Post Goods Issue exist in the Order-to-Cash cycle, what business and system events they represent, and how they connect sales, warehouse and finance.
Explanation
Picking and Post Goods Issue (PGI) sit between delivery creation and billing in the Order-to-Cash (O2C) process. Once a sales order is created and a delivery document is generated (via a delivery due list or manually), the goods must physically leave the warehouse before the customer can be invoiced for a goods movement–relevant item. Picking is the warehouse activity of confirming which stock, from which storage location, bin, or batch, will be taken to fulfill the delivery. PGI is the system event that records the actual goods issue: it reduces unrestricted-use inventory, updates the delivery status, and posts a financial document that recognizes the cost of goods sold (COGS) and reduces inventory value in Finance. Why this matters: revenue recognition and legal shipping documents in most industries depend on actual movement of goods, not just paperwork. A sales order alone does not change stock. A delivery document allows planning and picking, but stock quantity is not reduced until PGI happens. This separation lets a business plan warehouse work, confirm short picks or substitutions, and only commit the inventory reduction when goods physically leave the dock. It also cleanly separates SD (sales visibility) from MM (inventory control) and FI (financial impact), while keeping a single document flow chain that consultants and auditors can trace: Sales Order → Outbound Delivery → Picking Confirmation → PGI → Billing Document → Accounting Document. At a technical level, the delivery document header carries overall status fields for picking and goods movement. Each delivery item carries a picking quantity field and a goods movement status. Picking can be recorded in two main ways depending on warehouse complexity: a simple confirmation of the delivery quantity directly on the delivery (common for non-warehouse-managed storage locations), or a formal Warehouse Management / Extended Warehouse Management (EWM) transfer order process where a separate document instructs putaway/picking at bin level and confirms back to the delivery. In S/4HANA, embedded EWM or decentralized EWM is increasingly the standard for complex warehouses, while simple storage locations can still use basic delivery-based picking. PGI itself triggers a goods movement (conceptually a 601 movement type for outbound delivery-related goods issue in many standard scenarios), which is posted in Inventory Management. This movement decreases the quantity in the shipping storage location, creates a material document, and simultaneously creates or updates an accounting document if the material is valuated: debiting Cost of Goods Sold and crediting Inventory (finished goods or trading goods) using automatic account determination. Once PGI succeeds, the delivery is no longer changeable (in terms of quantity) and becomes eligible for billing due list processing. For a beginner-level understanding, it is essential to remember three checkpoints: (1) picking must be complete or at least confirmed as required by the item category and delivery type before PGI is allowed, (2) PGI requires available stock in the specified storage location/batch, and (3) PGI is the point of no easy return — reversing it requires a formal goods movement reversal (return delivery or cancellation of the material document), not a simple document change. This governs why many production support issues (stock shortages, blocked storage locations, batch determination failures) surface exactly at the PGI step, making it one of the most operationally sensitive events in O2C.
Real project scenario
A consumer goods company running S/4HANA On-Premise processes several thousand outbound deliveries daily from a distribution center using basic storage-location-based picking (no EWM). Warehouse staff use a picking list report to identify what to pick, physically move goods, and a warehouse clerk then confirms the picked quantity on the delivery and executes PGI in a batch job scheduled every two hours. During a peak season, the business escalated a recurring issue: deliveries would sit picked but not goods-issued because the batch job skipped them when stock was in the process of being replenished, causing intermittent negative stock warnings. The consulting team introduced a pre-check report to validate available stock before the delivery due list ran, reducing PGI batch job failures by identifying shortages before picking labor was spent.
Common mistakes
• Assuming picking and PGI are the same step; teams sometimes try to force PGI without confirming picking quantities, causing inconsistent status combinations. • Not distinguishing between delivery quantity and picked quantity fields when troubleshooting partial deliveries. • Treating PGI as reversible via simple document change; forgetting it requires a proper goods movement reversal or return process. • Ignoring that some item categories (e.g., non-stock or service items) are not relevant for picking or goods movement at all, leading to confusion when such items never show a picking requirement. • Overlooking that batch job scheduling for PGI must respect stock availability timing, especially in high-volume, high-velocity warehouses.
Best practices
• Always verify delivery item category settings to confirm whether an item is truly picking-relevant and goods-movement relevant before troubleshooting. • Educate warehouse users that PGI is a financial event, not just a logistics checkbox, to reduce careless reversals. • Document the exact document flow (order-delivery-PGI-billing) in project runbooks so support teams can trace issues quickly. • Use standard delivery monitor style reports to identify deliveries stuck between picking and PGI rather than querying tables ad hoc. • Align batch job scheduling for PGI with actual warehouse operating hours and stock replenishment cycles.
Interview angle
Interviewers commonly probe whether a candidate understands the distinct roles of the sales order, delivery, picking, and PGI, and can explain why stock is not reduced until PGI. A strong answer explains the document flow chain, states clearly that PGI creates a material document and (for valuated materials) an accounting document, and can describe the difference between simple delivery-based confirmation and warehouse-managed picking without conflating them. Being able to state the operational risk point (PGI as a near-irreversible event) also signals real project exposure rather than textbook knowledge.