What Is SAP MIGO (Goods Movement)?
Also known as: MIGO transaction, SAP goods receipt, MIGO goods movement
Definition
MIGO is the SAP transaction that posts goods movements in one screen: goods receipts against purchase orders, goods issues to production orders or cost centers, stock transfers and returns. Each posting creates a material document and an accounting document.
SAP MIGO (Goods Movement) Explained
MIGO replaced the older single-purpose transactions such as MB01 (receipt for purchase order), MB1A (goods issue) and MB1B (transfer posting). It has an action dropdown (Goods Receipt, Goods Issue, Transfer Posting, Return Delivery) and a reference dropdown (Purchase Order, Production Order, Delivery, Material Document, Other). The combination of action and reference drives the default movement type, for example Goods Receipt against Purchase Order proposes movement type 101.
The movement type is the real control object. It decides which stock type is updated (unrestricted, quality inspection, blocked), which general ledger accounts are posted through automatic account determination (transaction OBYC), and which fields are mandatory. Common types are 101 (receipt for PO), 122 (return to vendor), 201 (issue to cost center), 261 (issue to production order), 311 (transfer within plant between storage locations), 501 (receipt without PO) and 561 (initial stock load).
Every successful post writes a material document (tables MKPF header and MSEG items) and, for valuated materials, an accounting document (BKPF and BSEG) in the same logical unit of work. Quantity updates land in MARD (storage location stock) and valuation updates in MBEW. In S/4HANA the material document is stored in MATDOC, and MIGO is still available, with Fiori apps such as Post Goods Receipt for Purchase Order as the modern front end.
Typical failures are period not open (MMPV), missing account determination for a movement type and valuation class, over-delivery tolerance exceeded on the purchase order item, and negative stock when negative stock is not allowed at plant level. The fix is almost always configuration or master data, not a retry of the posting.
Why It Matters
- Every inventory quantity and inventory value change in SAP flows through a goods movement, so MIGO errors become stock and ledger errors.
- Movement types determine ledger impact, which means a wrong type silently posts value to the wrong account.
- Goods receipt is the trigger for three-way match, so late or missing MIGO postings block vendor invoices.
- It is the main write-back surface that shop floor, scanner and automation integrations imitate, usually through BAPI_GOODSMVT_CREATE.
In Practice
A purchase order for 500 bearings is received as 480 pieces. The receiver opens MIGO, picks Goods Receipt and Purchase Order, enters the PO number, sets quantity 480 on the item and ticks Item OK. Movement type 101 posts 480 to unrestricted stock, and the open PO quantity drops to 20. If the plant uses quality inspection stock, the same posting lands in QI stock until the inspection lot is decided.
Frequently Asked Questions
What is the difference between MIGO and MB1A?
MB1A was a single-purpose goods issue transaction. MIGO combines goods receipt, goods issue, transfer posting and returns in one screen, and SAP has marked the older MB-series transactions as obsolete.
How do I reverse a MIGO posting?
Use MIGO with the Cancellation action (movement type 102 reverses 101) and reference the original material document, or use transaction MBST. A reversal creates a new material document rather than deleting the original.
Which tables store MIGO postings?
Material documents sit in MKPF and MSEG in ECC, and in MATDOC in S/4HANA. Stock quantities are in MARD and valuation in MBEW, with accounting documents in BKPF and BSEG.
Related Terms
Three-Way Match
A three-way match is the accounts payable control that compares the purchase order, the goods receipt, and the supplier invoice on quantity and price before releasing payment, ensuring a company pays only for what it ordered and actually received.
Goods Received Not Invoiced (GRNI)
Goods received not invoiced, also called GRNI or GR/IR, is the accrued liability for items received into stock for which the supplier invoice has not yet been matched or posted. It is cleared when the invoice is verified.
Cycle Counting
Cycle counting is the practice of continuously verifying inventory accuracy by counting a small subset of items each day or week, rather than shutting down for one annual wall-to-wall physical inventory.
Inventory Valuation Methods (FIFO, Average, Standard)
Inventory valuation methods determine the cost assigned to stock on hand and to items sold. The common ones are FIFO, LIFO where allowed, weighted or moving average, specific identification and standard cost.
Purchase Requisition
A purchase requisition is an internal request to procure goods or services, routed for approval against budget and authority limits before a buyer sources it and converts it into a purchase order sent to a supplier.
Working with SAP MIGO (Goods Movement) in a live environment? Our engineers do this every day - and our AI agents automate most of it.