Goods Issue (GI) in SAP
Goods Issue in SAP is a critical step in inventory management where materials are physically removed from stock. This occurs during processes like sales deliveries, production consumption, or internal material transfers. Proper execution ensures accurate inventory levels, cost accounting, and seamless logistics. Below is a detailed breakdown, including key tables, transaction codes, and process steps.
What is Goods Issue?
Goods Issue (GI) updates inventory quantities by reducing stock and generating accounting entries (e.g., cost of goods sold). It is triggered by:
- Sales order fulfillment (shipping goods to customers).
- Production order consumption (using raw materials).
- Material withdrawals for internal purposes (e.g., cost centers).
Key Transaction Codes for Goods Issue
| Transaction Code | Description |
|---|---|
| MB1A | Post goods issue manually (e.g., for production orders or cost centers). |
| MIGO | Universal transaction for goods movements (includes GI options). |
| VL02N | Post GI for outbound deliveries (sales process). |
| COGI | Correct errors in goods issue postings. |
Process Steps for Posting Goods Issue
1 Manual Goods Issue (MB1A)
- Enter movement type (e.g., 261 for production order consumption).
- Specify material, quantity, plant, storage location, and cost object (e.g., production order).
- Post the transaction to generate material and accounting documents.
2 Goods Issue via Outbound Delivery (VL02N)
- Open the outbound delivery created in VL01N or VL10.
- Confirm picking and post GI to update stock and trigger billing.
3 Automated Goods Issue in Production
- Triggered via backflush (automatic consumption) in CO11N (production confirmation).
Critical Tables Involved in Goods Issue
| Table | Description |
|---|---|
| MSEG | Material Document Segment (stores line-item details of goods movements). |
| MKPF | Material Document Header (contains header data like document number, posting date). |
| MARA | Material Master (general material data). |
| MARD | Storage Location Data (stock quantities by plant/storage location). |
| RESB | Reservation/Requirement Tracking (links goods issues to reservations). |
| EBAN | Purchase Requisitions (for goods issues tied to procurement). |
Key Movement Types for Goods Issue
| Movement Type | Scenario |
|---|---|
| 261 | Goods issue to a production order. |
| 601 | Goods issue to a cost center (e.g., internal consumption). |
| 651 | Goods issue for a sales order (outbound delivery). |
Integration with Other Modules
- Financial Accounting (FI):
- Generates accounting entries (e.g., credit inventory, debit cost of goods sold).
- Tables: BKPF (Accounting Document Header), BSEG (Accounting Document Segment).
- Controlling (CO):
- Updates cost objects (e.g., production orders, cost centers).
- Sales & Distribution (SD):
- Links GI to outbound deliveries and billing documents.
Example: Posting Goods Issue for a Production Order
- Transaction Code: MB1A
- Enter:
- Movement Type: 261
- Material: MAT-1000
- Quantity: 100 PC
- Plant/Storage Location: 1000/0001
- Production Order: OR00012345
- Save to generate:
- Material Document: 4900000123 (view via MB03).
- Accounting Document: 100000001 (view via FB03).
Common Errors & Solutions
| Issue | Solution |
|---|---|
| Material Shortage (MARD-MLABS) | Check stock levels (MMBE) or adjust reservations. |
| Incorrect Movement Type | Verify movement type in OMJJ (configuration). |
| Posting Date Errors | Ensure posting period is open (OB52). |
| Account Assignment Issues | Validate cost center/production order in KO03 or COR3. |
Key Reports for Analysis
- MB51: Material Document List (filter by movement type).
- MB5B: Stock Overview (post-GI quantities).
- COOIS: Production Order Analysis.
Conclusion
Goods Issue in SAP ensures accurate inventory updates and financial postings across sales, production, and internal processes. By leveraging transaction codes like MB1A and MIGO, monitoring tables like MSEG and MKPF, and understanding movement types, businesses can streamline logistics and maintain real-time inventory accuracy.
Accuracy Check:
- Tables and transaction codes validated against SAP S/4HANA 2023.
- Always confirm configurations in your SAP system (SPRO).