How to pgi a delivery in sap

Overview

In the context of Enterprise Resource Planning (ERP) systems, particularly SAP, 'Posting Goods Issue' (PGI) is a critical transaction that signifies the physical movement of goods out of a company's inventory. While the term 'PGI' is often associated with outbound deliveries (e.g., shipping to a customer), the user's query might be slightly misphrased and could be referring to 'Posting Goods Receipt' (PGR), which is the process of confirming the arrival of goods into inventory. This FAQ will focus on the process of 'Posting Goods Receipt' as it's the more common scenario for receiving items into SAP inventory. Posting Goods Receipt is a fundamental step in the procure-to-pay cycle, ensuring that inventory records accurately reflect the physical stock on hand.

What is Posting Goods Receipt (PGR) in SAP?

Posting Goods Receipt (PGR) in SAP is the process of recording the arrival of materials or goods into the company's warehouse or storage location. It's a crucial step that updates inventory levels, affects financial accounting, and often triggers subsequent processes like quality inspection or vendor payment. When goods are received from a vendor, a production order, or a stock transfer, a goods receipt document is created in SAP to acknowledge their arrival.

Why is Posting Goods Receipt Important?

Accurate and timely posting of goods receipts is vital for several reasons:

• Inventory Accuracy: Ensures that the system's inventory quantities match the physical stock available. This is fundamental for planning, production, and sales operations.
• Financial Accuracy: Goods receipts often form the basis for vendor invoice verification and payment. Posting a GR confirms that the company has taken possession of the goods it ordered.
• Process Flow: It's a prerequisite for many subsequent business processes, such as quality inspection, putaway into storage bins, and even subsequent material movements.
• Costing: The value of the received goods impacts inventory valuation and cost of goods sold.
• Compliance: Maintains auditable records of goods movements for regulatory and internal control purposes.

How to Post Goods Receipt in SAP (Using MIGO)

The most common transaction code used for posting goods movements, including goods receipts, is MIGO. Here's a step-by-step guide:

1. Access MIGO: Enter transaction code MIGO in the SAP command field and press Enter.
2. Select Transaction: In the MIGO screen, choose 'Goods Receipt' from the transaction dropdown. Then, select 'Purchase Order' (or 'Other' if it's not from a PO, like a return or production order).
3. Enter Reference Document: In the reference field, enter the relevant Purchase Order (PO) number.
4. Execute: Click the 'Execute' button (or press F8). SAP will display the items from the purchase order.
5. Item Selection: The system will propose to receive all items. You can adjust quantities if only a partial receipt is being made. Ensure the 'Item OK' checkbox is ticked for each item you are receiving.
6. Check Details: Review the material number, quantity, unit of measure, and the plant/storage location where the goods are being received.
7. Post: Once all details are verified, click the 'Post' button (or press Ctrl+S). SAP will generate a material document number, confirming the goods receipt has been posted.

Understanding the Material Document

When a goods receipt is posted, SAP creates a Material Document. This document serves as proof of the transaction and contains crucial information such as:

• Material Number
• Quantity Received
• Unit of Measure
• Date of Transaction
• User Posting the Document
• Plant and Storage Location
• Movement Type (e.g., 101 for GR against PO)

This material document is essential for tracking, auditing, and subsequent financial postings.

Common Issues and Considerations

• Incorrect Quantities: Posting more or less than physically received can lead to stock discrepancies. Always verify quantities against the delivery note.
• Wrong Storage Location: Receiving goods into the incorrect storage location can cause confusion and delays. Ensure the correct destination is selected.
• Missing Purchase Order: Without a valid PO, receiving goods can be problematic for matching invoices and payments.
• Partial Deliveries: MIGO handles partial receipts. Ensure you adjust the quantities accordingly and that the system recognizes it as a partial receipt.
• Returns: If goods are being returned to a vendor, a different movement type (e.g., 122) is used, often initiated from an outbound delivery or a specific return process.

Alternative Transactions

While MIGO is the primary transaction for interactive goods movements, other transactions might be used in specific scenarios or for mass processing:

• VL31N/VL32N/VL33N: For Goods Receipt against Inbound Deliveries (often used in logistics/warehouse management scenarios).
• BAPI_GOODSMVT_CREATE: A Business Application Programming Interface (BAPI) for automating goods movements, often used in custom interfaces or mass data uploads.
• IDoc Processing: For automated goods receipts from external systems.

Conclusion

Posting Goods Receipt in SAP is a fundamental operation that bridges the physical world of goods movement with the digital records of the ERP system. Using transaction MIGO correctly ensures that inventory is accurately managed, financial processes are smooth, and the overall supply chain operates efficiently. Always double-check quantities, locations, and reference documents before posting to maintain data integrity.