MIGO_GR vs. MIGO_TR vs. MIGO_GI: Key Differences and Use Cases


 

Introduction

In SAP, the MIGO transaction is a central tool for managing goods movements. However, different transaction types exist within MIGO to handle various inventory movements. Among them, MIGO_GR, MIGO_TR, and MIGO_GI are commonly used, and understanding their differences is crucial for effective inventory management. This article provides a detailed comparison of these three transaction codes, explaining their purposes, key differences, and when to use them.

Understanding the Three Transaction Codes

Transaction Code Purpose Key Impact Common Movement Types
MIGO_GI (Goods Issue) Used when stock is issued from inventory Reduces stock quantity 201 (Cost Center), 543 (Subcontracting), 261 (Production Order)
MIGO_TR (Transfer Posting) Used for stock transfers and changes in stock status No physical movement required; only stock category changes 309 (Material to Material), 321 (Stock to Stock), 301 (Plant to Plant), 311 (Storage Location to Storage Location)
MIGO_GR (Goods Receipt) Used for recording incoming stock Increases stock quantity 101 (Goods Receipt with PO), 102 (Goods Return), 501 (Receipt w/o PO)

Detailed Breakdown of MIGO_GR, MIGO_TR, and MIGO_GI

1. MIGO_GI – Goods Issue (Stock Reduction)

MIGO_GI is used when materials are issued from stock, meaning the stock quantity decreases. This is typically required when goods are consumed for production, sent to subcontractors, or withdrawn for a specific cost center.

When to Use MIGO_GI?

  • Issuing goods for internal or external consumption.
  • Transferring materials to a subcontractor.
  • Adjusting stock levels for scrapping or other non-returnable purposes.

Common Movement Types:

  • 201 – Issue to cost center.
  • 543 – Issue to a subcontractor.
  • 261 – Issue for a production order.

2. MIGO_TR – Transfer Posting (Stock Reallocation)

MIGO_TR is used for changing stock status rather than physically moving goods. Unlike MIGO_GI, it does not reduce stock; it only changes stock categories.

When to Use MIGO_TR?

  • Moving stock between different categories (e.g., unrestricted to quality inspection).
  • Transferring stock between different storage locations or plants.
  • Reclassifying materials from one material code to another.

Common Movement Types:

  • 309 – Transfer posting from material to material.
  • 321 – Transfer from unrestricted to quality inspection stock.
  • 301 – Stock transfer between plants.
  • 311 – Stock transfer between storage locations.
If there is a valuation change in the stock transfer, SAP automatically generates an accounting document.

3. MIGO_GR – Goods Receipt (Stock Addition)

MIGO_GR is used for receiving materials into stock, either from a purchase order (PO) or without reference to a PO.

When to Use MIGO_GR?

  • Receiving goods from suppliers.
  • Adding stock from production.
  • Manually entering opening balances for new materials.

Common Movement Types:

  • 101 – Goods receipt against a purchase order.
  • 102 – Goods return to the vendor.
  • 501 – Goods receipt without a purchase order.

Comparing MIGO_GI, MIGO_TR, and MIGO_GR

Feature MIGO_GI (Goods Issue) MIGO_TR (Transfer Posting) MIGO_GR (Goods Receipt)
Stock Impact Stock decreases No change in stock quantity Stock increases
Physical Movement? Yes (issued from stock) No (only category change) Yes (goods added to stock)
Accounting Impact? Yes (expense incurred) Only if valuation changes Yes (stock value increases)
Common Use Cases Consumption, scrapping, subcontracting Stock status change, storage location transfer Goods receipt, production completion

Subcontracting in SAP: Where Do These Transactions Fit?

In subcontracting, raw materials are sent to a vendor for processing, and the finished product is received back. Here's how the different transactions fit in:
  • MIGO_TR (Transfer Posting) – Used to transfer components to subcontracting stock. The material remains in your inventory but is marked as "Material Provided to Vendor."
  • MIGO_GI (Goods Issue) – Used if the material is issued to the subcontractor (movement type 543).
  • MIGO_GR (Goods Receipt) – Used when the finished goods are received from the subcontractor.

FAQs

1. Can I use the MIGO transaction instead of MIGO_GI, MIGO_TR, and MIGO_GR?

Yes, MIGO is the universal transaction that allows users to perform all three actions. However, you must select the correct reference document and movement type for each transaction.

2. What happens if I use MIGO_GI instead of MIGO_TR?

If you mistakenly use MIGO_GI instead of MIGO_TR, your stock will be consumed rather than transferred, which can lead to incorrect stock valuation and shortages.

3. Is an accounting document generated for every MIGO transaction?

No, an accounting document is only generated when there is a stock valuation impact. For example, a simple transfer posting (MIGO_TR) does not generate an accounting document unless there is a change in valuation.

4. When should I use MIGO_GR without a purchase order?

Use MIGO_GR without a PO (Movement Type 501) when adding initial stock balances, donations, or adjustments that do not reference a purchase order.

5. What is the difference between stock transfer and transfer posting?

  • Stock Transfer (e.g., 301, 311) – Involves the physical movement of goods between locations.
  • Transfer Posting (e.g., 309, 321) – Only changes the stock status without physical movement.

6. Can MIGO_GI be reversed?

Yes, MIGO_GI can be reversed using the corresponding movement type (202 for cost center reversal, 262 for production order reversal).

Conclusion

Understanding the differences between MIGO_GI, MIGO_TR, and MIGO_GR is essential for managing SAP inventory efficiently.
  • Use MIGO_GI when issuing stock.
  • Use MIGO_TR when transferring stock without physical movement.
  • Use MIGO_GR when receiving stock.
By selecting the correct transaction and movement type, you ensure accurate stock records, proper accounting entries, and seamless inventory control in SAP. 

Goto:
SAP MM Purchasing

Back to:
SAP MM (Materials Management) Configuration Hints and Tips

Return to :-
SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

(c) www.gotothings.com All material on this site is Copyright.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
All product names are trademarks of their respective companies.  The site www.gotothings.com is in no way affiliated with SAP AG.
Any unauthorised copying or mirroring is prohibited.