7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI)

Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI)

Once an outbound delivery document is created, commercial sales processing pauses and physical warehouse execution takes command. The warehouse team must locate the inventory, stage it for transport, securely pack it into containers or pallets, and dispatch it through the facility gates.

In SAP S/4HANA, warehouse execution is structured around three sequential operational milestones:

1. Picking: Locating stock within the warehouse, retrieving the required quantities, and confirming them into the delivery.
2. Packing: Encapsulating picked materials into physical packaging containers using Handling Unit Management (HUM).
3. Post Goods Issue (PGI): The step that reduces inventory, posts the accounting document, and makes the delivery relevant for billing.

---

The Picking Process and Storage Location Determination

Picking is the physical retrieval of goods from warehouse storage bins and their transfer to the outbound staging bay. In SAP S/4HANA, an item cannot be goods-issued until picking is 100% complete (unless the item category is explicitly configured as not relevant for picking).

                                PICKING LOCATION DETERMINATION (MALA RULE)

     [ Shipping Point (LIKP-VSTEL) ]       [ Delivering Plant (LIPS-WERKS) ]       [ Material Master: MARA-RAUBE ]
              Shipping Point                             Plant                                Storage Condition
                  (e.g., 1000)                        (e.g., 1000)                             (e.g., 01 - Cold)
                       │                                   │                                          │
                       └───────────────────────────┬───────┴──────────────────────────────────────────┘
                                                   ▼
                                     [ Customizing Table TVKOL ]
                                                   │
                                                   ▼
                                        Picking Storage Location
                                          (e.g., LGORT 0002 - Cold Vault)

Picking Location Determination: The MALA Rule

When an outbound delivery is created, the line items often lack a specific storage location in the sales order. The system automatically derives the picking storage location (LIPS-LGORT) using the rule configured in the delivery type.

The common rule is MALA, which evaluates a 3-part key in Customizing (Logistics Execution → Shipping → Picking → Determine Picking Location, table TVKOL). Rule RIMO uses plant + situation + storage condition instead, and MARE tries MALA first and then RIMO:

$$\text{Shipping Point} + \text{Delivering Plant} + \text{Storage Condition} \Longrightarrow \text{Storage Location}$$

• Shipping Point (VSTEL): Derived at delivery header level.
• Delivering Plant (WERKS): Sourced from the delivery line item.
• Storage Condition (RAUBE): Maintained in the Material Master on the Plant Data / Storage 1 view (MARA-RAUBE, a client-level field). Describes environmental storage requirements (e.g., 01 Ambient Dry, 02 Refrigerated 2–8°C, 03 Deep Frozen -20°C, 04 Flammable Hazmat).

Tracking Picking Status in Delivery Documents

Picking progress is tracked in the delivery status fields (in SAP S/4HANA directly in LIKP/LIPS, because VBUK/VBUP no longer exist):

• LIPS-KOSTA / LIKP-KOSTK (Picking Status):
  • ' ' — Not relevant for picking (e.g., text items, digital software licenses, or BOM headers).
  • 'A' — Not yet picked (Picked Quantity = 0).
  • 'B' — Partially picked ($0 < \text{Picked Qty} < \text{Delivery Qty}$).
  • 'C' — Completely picked ($\text{Picked Qty} = \text{Delivery Qty}$).

Warehouse Execution Architectures: Standard SD, Lean WM, and EWM

Depending on facility complexity, SAP S/4HANA supports three ways to execute picking:

┌─────────────────────────────────────────────────────────────────────────────────┐
│                     WAREHOUSE EXECUTION ARCHITECTURE TIERS                      │
├────────────────────────┬───────────────────────────┬────────────────────────────┤
│  Inventory Mgmt Only   │  Stock Room Management    │  Embedded EWM              │
│  (Basic Inventory)     │  (Lightweight Picking)    │  (Advanced High-Volume)    │
├────────────────────────┼───────────────────────────┼────────────────────────────┤
│ - Direct entry in VL02N│ - Transfer Orders (LT03)  │ - Outbound Delivery Order  │
│ - Pick list print EK00 │ - Pick confirmation LT12  │ - Warehouse Tasks & Orders │
│ - No bin inventory     │ - Fixed picking bins only │ - Wave Mgmt & RF Scanners  │
└────────────────────────┴───────────────────────────┴────────────────────────────┘

1. Standard SD Picking (Inventory Management Only):
   • Used in small depots with simple storage locations.
   • Warehouse clerk generates a picking sheet output (EK00). Workers pull stock manually, and the clerk enters the picked quantity directly into the delivery document on the Picking tab (VL02N).
2. Stock Room Management (lean version of legacy WM):
   • Legacy Warehouse Management is no longer developed; a lean version remains available as Stock Room Management for simple warehouses.
   • A Transfer Order (TO) is generated referencing the outbound delivery (LT03). The TO specifies fixed picking bins.
   • Once physically picked, the TO is confirmed (LT12). Confirmation automatically updates the picked quantity (LIPS-PIKMG) in the delivery document.
3. Extended Warehouse Management (Embedded or Decentralized EWM):
   • SAP develops warehouse functions only in EWM, which is also available inside SAP S/4HANA as embedded EWM (section 7.5 covers the EWM steps).
   • The SD outbound delivery replicates to EWM as an Outbound Delivery Order (ODO).
   • EWM executes dynamic wave planning, storage bin search algorithms, slotting, and task interleaving. Warehouse operators execute Warehouse Tasks (WT) aggregated into Warehouse Orders (WO) using mobile Radio Frequency (RF) handhelds.
   • When loading completes, goods issue is triggered in EWM, which reports it back to the outbound delivery in SAP S/4HANA (section 7.5).

The Packing Process and Handling Unit Management (HUM)

Packing is the operational assignment of delivery items to physical packaging materials (cartons, drums, pallets, shipping containers). In SAP S/4HANA, packing can be handled via basic delivery packing or through Handling Unit Management (HUM).

Packaging Materials (Material Type VERP)

Packaging materials are maintained in the Material Master under material type VERP (e.g., Euro-Pallet PAL-01, Cardboard Box BOX-10, Shrink Film FILM-02). In the Sales: General/Plant Data view, two crucial fields govern packing behavior:

• Packaging Material Type (MARA-VHART): Maintained on the packaging material itself; classifies the container (e.g., pallet, crate, carton) and controls how it is used in packing.
• Material Group for Packaging Materials (MARA-MAGRV): Maintained on the goods to be packed and on packaging materials; groups materials with similar packaging requirements so the system can check which packaging materials are allowed.

The Handling Unit (HU) Concept

A Handling Unit is an autonomous physical unit consisting of packaging materials and the goods contained within. Every Handling Unit possesses a globally unique identification number (typically formatted according to the GS1 standard SSCC-18 / Serial Shipping Container Code).

Handling Units support Multi-Level / Nested Packaging:

Handling Unit 100450000001 (Euro-Pallet - SSCC Level 1)
  ├── Handling Unit 100450000010 (Master Carton 1 - SSCC Level 2)
  │     └── 20 Units Material A (Serial Numbers SN001 - SN020)
  ├── Handling Unit 100450000011 (Master Carton 2 - SSCC Level 2)
  │     └── 20 Units Material A (Serial Numbers SN021 - SN040)
  └── Packaging Material FILM-02 (Shrink Wrap)

Packing Execution and Tolerance Validations

• Manual Packing (VL02N): Inside the delivery, navigating to Edit $\rightarrow$ Pack opens the packing cockpit. Operators select packaging materials, assign quantities, and build nested structures.
• Automatic Packing via Packing Instructions (create with POP1, determination records with POF1): Predefined rules define how materials should be packaged (e.g., "Pack 10 units of Material X into Box B; stack 20 Box B onto Pallet P"). When the delivery is saved, the system automatically generates complete multi-level Handling Units.
• Weight and Volume Check: The system calculates the tare weight of containers plus the net weight of packed materials. If the total weight exceeds the Maximum Allowed Weight configured for the packaging material, the system issues a warning or rejects packing, preventing vehicle overload and shipping violations.

Post Goods Issue (PGI): Multi-Module Operational Impact

Post Goods Issue (PGI) is the final step in shipping execution, posted via transaction VL02N or collectively via VL06O / background jobs.

The outbound delivery monitor (VL06O) lists the deliveries that are still to be processed or have been processed, for example deliveries waiting for picking, loading, transportation planning, confirmation, or goods issue. Users save their own selection and display variants and run follow-on functions in collective processing, such as posting goods issue for many deliveries at once. An inbound delivery monitor works the same way for inbound deliveries.

PGI records that the goods have physically left the company's stock. When ownership passes to the customer is a contractual question (for example, governed by the agreed Incoterms), not a system status. Because this milestone bridges physical logistics, financial accounting, and commercial sales, posting goods issue triggers simultaneous updates across the entire enterprise system.

                                  POST GOODS ISSUE (VL02N / Movement 601)
 ┌───────────────────────────────────────────────────┬───────────────────────────────────────────────────┐
 │ 1. INVENTORY MANAGEMENT (MM-IM)                   │ 2. FINANCIAL ACCOUNTING (FI-GL & ACDOCA)          │
 │ - Stock quantity reduced in MARD (Movement 601)   │ - Accounting Document posted in Universal Journal │
 │ - Material Document created (MATDOC)              │ - Debit: Cost of Goods Sold (COGS) Account        │
 │ - Valuated Stock reduced                          │ - Credit: Finished Goods Inventory Asset Account  │
 ├───────────────────────────────────────────────────┼───────────────────────────────────────────────────┤
 │ 3. COMMERCIAL BILLING (SD-BIL)                    │ 4. LOGISTICS EXECUTION STATUS (SD-SHP)            │
 │ - Billing Due Index (VKDFS) updated               │ - Goods Movement Status: Complete (WBSTK = 'C')   │
 │ - Billing Status updated to Open (FKSTK = 'A')    │ - Delivery Document locked against changes        │
 │ - Delivery becomes eligible for VF01 / VF04       │ - Preceding Sales Order line updated in VBFA      │
 ├───────────────────────────────────────────────────┼───────────────────────────────────────────────────┤
 │ 5. DEMAND & REQUIREMENTS PLANNING (PP-MRP)        │ 6. CONTROLLING & PROFITABILITY (CO-PA)            │
 │ - Material reservations and open requirements     │ - Cost of sales passed to CO-PA segment           │
 │   generated by sales order schedule lines cleared │ - Real-time revenue matching enabled              │
 └───────────────────────────────────────────────────┴───────────────────────────────────────────────────┘

The 6 Core Consequences of Post Goods Issue

1. Materials Management — Physical Inventory Reduction (MM-IM)

• Physical inventory in table MARD (storage location stock) is decremented by the delivered quantity.
• Standard Movement Type: 601 (Goods Issue for Sales Order).
• Other standard movement types include 651 (Customer Returns - Non-valuated), 641 (Two-Step Stock Transport Order to In-Transit Stock), and 643 (Cross-Company Stock Transport Order).
• A Material Document is generated (stored in table MATDOC in SAP S/4HANA; MKPF and MSEG remain available as compatibility views), providing an audit trail of the stock movement.

2. Financial Accounting — General Ledger Posting (FI-GL / Universal Journal)

• An Accounting Document is created and posted directly to the Universal Journal (ACDOCA).
• The financial valuation uses standard cost (S) or moving average price (V) from the material master:
  • Debit: Cost of Goods Sold (COGS) account (derived via automatic account assignment key GBB-VAX in transaction OBYC).
  • Credit: Inventory Asset Account (derived via transaction key BSX in OBYC).

$$\begin{aligned} \mathbf{Debit:} & \quad \text{Cost of Goods Sold (COGS)} & \text{\textdollar}10{,}000 \\ \mathbf{Credit:} & \quad \text{Finished Goods Inventory (Asset)} & \text{\textdollar}10{,}000 \end{aligned}$$

3. Billing Due List Integration (SD-BIL)

• The delivery document is written to the Billing Due Index (table VKDFS).
• The billing status of the delivery (LIKP-FKSTK at header, LIPS-FKSTA at item) is 'A' (not yet billed).
• The delivery is now immediately visible to the billing engine (transactions VF01, VF04, or background billing jobs).

4. Delivery Document Flow and Status Locking (SD-SHP)

• The goods movement status (LIKP-WBSTK / LIPS-WBSTA) changes from 'A' (Not yet processed) to 'C' (Completely processed).
• The Document Flow table (VBFA) records the creation of the Material Document and Accounting Document linked to the outbound delivery.
• Change restriction: Once PGI is posted, quantities, items, and batches in the delivery can no longer be changed; to correct them, the goods issue must first be reversed (VL09).

5. Demand & Requirements Planning (PP-MRP)

• Customer requirements passed to MRP by the sales order schedule line (VBEP) are satisfied and cleared.
• The delivery requirement is removed at the same time as the stock is reduced, so the availability situation stays consistent.

6. Controlling and Profitability Analysis (CO-PA)

• In account-based Profitability Analysis (margin analysis), the cost of goods sold posting carries the profitability segment derived from the sales order item, so revenues and costs can be matched later.

Reversal of Post Goods Issue: Transaction VL09

In warehouse operations, errors inevitably happen: incorrect pallets are loaded, a carrier fails to arrive, or a customer cancels an order while the truck is still at the dock. Because a delivery with posted PGI is structurally locked, normal editing is impossible.

To correct this, SAP provides Transaction VL09 (Cancel Goods Issue for Outbound Delivery).

The Inviolable Prerequisite: The Billing Blockade

Before transaction VL09 can execute, an essential cross-module condition must be met:

If an invoice has already been created in transaction VF01 (billing status LIKP-FKSTK = 'C'), transaction VL09 rejects the reversal.

To reverse goods issue when an invoice exists, the exact reverse sequence must be executed:

   ERROR DISCOVERED AFTER INVOICING
                │
                ▼
   1. Cancel Billing Document (VF11)
      - Reverses Accounting Document (Credit AR, Debit Revenue)
      - Resets Delivery Billing Status (FKSTK reverts from 'C' to 'A')
                │
                ▼
   2. Cancel Goods Issue (VL09)
      - Executes Movement Type 602
      - Reverses FI COGS Entry (Debit Inventory, Credit COGS)
      - Restores Physical Stock in MARD
      - Resets Goods Movement Status (WBSTK reverts from 'C' to 'A')
                │
                ▼
   3. Correct Outbound Delivery (VL02N)
      - Adjust quantities, replace batches, or delete delivery document

Consequences of Executing VL09

1. Movement Type 602: Executes MM reversal movement type 602 (Reversal of Goods Issue for Sales Order).
2. Inventory Restored: Stock quantities are credited back to unrestricted inventory in table MARD.
3. Accounting Reversal: An offsetting financial document is posted in ACDOCA, Debiting Inventory Finished Goods and Crediting COGS.
4. Status Reversion: The Goods Movement Status (WBSTK) reverts from 'C' to 'A', unlocking the delivery document for corrections or deletion.