Picking Confirmation and Its Integration with Inventory and Accounting

Explanation

Picking is not merely a warehouse activity recorded on a delivery document; it is the trigger point that reconciles physical stock movement expectations with the financial and logistics view of inventory. Once a delivery is created from a sales order (or created directly for stock transfers), the delivery item carries a picking quantity field alongside the originally requested delivery quantity. Until picking is confirmed, PGI is normally blocked for items configured with picking relevance, because the system needs assurance that the physical stock has actually been removed from the source storage location or bin before it reduces unrestricted stock in Materials Management. The picking process interacts with several master data elements that must be correctly configured for accurate downstream postings. Batch management-relevant materials require batch determination during picking, either manually entered by the warehouse clerk or automatically proposed through batch search strategies that consider shelf life, FIFO/LIFO rules, or customer-specific batch requirements. Serial number profiles, when active on the material master, force serial number entry or automatic assignment at the time of picking or PGI, and these serial numbers become part of the equipment master history for traceability, which is critical for regulated industries such as pharmaceuticals or aerospace. When the warehouse confirms the pick (updating the picked quantity field, either manually in the delivery via change mode, through a mobile data entry transaction, or via a Transfer Order confirmation when Warehouse Management is active), the system compares picked quantity against delivery quantity. A full match allows an unrestricted PGI. A partial pick can either allow partial PGI with delivery split, or require configuration to disallow PGI until the full picked quantity is confirmed, depending on the delivery item category and copy control settings inherited from the sales document type. PGI itself triggers a goods movement, typically movement type 601 for standard outbound deliveries against sales orders, which is technically executed via the standard goods movement framework shared with Materials Management. This reduces unrestricted-use stock (or a specific storage location/batch stock) and, if the material is valuated, immediately creates a financial accounting document. The accounting entry typically debits the cost of goods sold account and credits inventory (stock account), which is why account determination configuration (valuation class, movement type, and account key combinations) must be correctly maintained; failures here result in delivery documents that are picked and quantity-confirmed but stuck at PGI with account determination errors. Integration with Quality Management can also intersect here: materials with an active inspection type for goods issue may generate a quality inspection lot at PGI or block PGI until a usage decision is recorded, depending on configuration. Understanding these dependencies is essential for consultants supporting cutover and production issues, since a seemingly simple 'PGI failed' ticket can actually originate from batch determination misconfiguration, blocked stock, missing serial numbers, or QM inspection stock status — not necessarily from a picking or delivery problem. In S/4HANA, the underlying goods movement and accounting document creation logic is largely unchanged functionally from ECC, but the Universal Journal (ACDOCA) consolidates the financial postings, and Fiori apps for goods issue and delivery monitoring (such as Manage Outbound Deliveries) surface picking and PGI status more transparently, reducing reliance on classic list transactions for day-to-day monitoring in on-premise and private cloud editions. Public cloud editions restrict configuration changes to those exposed in the SAP-delivered configuration scope, so custom account determination or QM integration changes must go through supported extensibility techniques rather than direct customizing in the underlying tables.

Code example

* Example: Simplified logic pattern (pseudo-representation) of what happens* internally when PGI is posted for a delivery item - for training/reference only,* not an exact reproduction of SAP's internal function module calls. * 1. Read delivery item picking status and picked quantityIF vbup-pkstk = 'C'.  " C = Fully picked/confirmed  * 2. Trigger goods movement (material document) - conceptually movement type 601  PERFORM create_goods_movement USING '601' delivery_item.  * 3. Goods movement updates MM stock tables (conceptual)  * 4. Accounting document generated (FI document, and in S/4HANA, ACDOCA line items)  * 5. Delivery status updated: warehouse activity status = Completed  * 6. Document flow (VBFA) updated linking delivery to goods movement documentELSE.  MESSAGE e090(vl) WITH 'Delivery not fully picked - PGI blocked'.ENDIF.

Real project scenario

A consumer goods company reported that PGI was failing for a subset of deliveries every Monday morning during peak dispatch. Investigation showed the affected materials were batch-managed with an automatic batch search strategy tied to shelf-life expiration dates. Over the weekend, batches that had been valid on Friday crossed their minimum remaining shelf life threshold, so the previously proposed batch was no longer valid at PGI time, causing a batch determination error. The fix involved re-triggering batch determination at the point of PGI rather than relying solely on the batch proposed during Friday's picking, and adjusting the shelf-life buffer in the batch search strategy to reduce the frequency of weekend expiries.

Common mistakes

• Assuming a PGI failure is always a picking problem, when it is often account determination, batch validity, or QM stock status • Not distinguishing between the delivery item's requested quantity and picked quantity when diagnosing partial delivery issues • Failing to update batch determination at PGI when significant time has elapsed since picking confirmation • Ignoring serial number profile requirements, leading to PGI errors that appear unrelated to serialization • Overlooking that valuation class or movement type misconfiguration causes technically 'picked and ready' deliveries to fail only at the accounting posting step

Best practices

• Always confirm picked quantity before diagnosing a PGI failure to isolate whether the issue is logistics-side or accounting/inventory-side • Review batch search strategy validity windows for shelf-life sensitive materials to reduce weekend or holiday batch expiry failures • Validate account determination (valuation class, movement type, account key) as part of any new material or plant rollout, not just at go-live • Coordinate with QM configuration owners when inspection types are active for goods issue movements • Use delivery monitoring apps or transactions to differentiate picking-status issues from PGI-blocking issues before escalating to FI or MM teams

Interview angle

Interviewers commonly probe whether a candidate understands that PGI is a financially relevant event, not just a logistics status change. Be ready to explain what accounting entries are generated at PGI, how movement type 601 relates to cost of goods sold recognition, and how batch or serial number determination can block PGI even when picking quantities are fully confirmed. Demonstrating awareness of the QM inspection lot intersection with PGI also signals cross-module maturity.