MM / P2Pintermediate

MM Inventory Management Part 2: Goods Movements, Material Documents and Accounting Documents

Key takeaway

What each goods movement records: the material document with header and items, the accounting document for valuated movements, the link between them, reversals, document display and lists, and how movements update stock, value and reservations.

Explanation

📌 KEY POINTS
✅ Every goods movement creates a material document (header + items with movement type, quantity, sloc, batch).
✅ Valuated movements also create an accounting document linked to the material document.
✅ Movement types define quantity/value updates and which accounts are hit.
✅ Reversals create new documents with the reversal movement type, not deletions.
⚠️ Material documents can't be changed after posting (except texts); correct with reversals.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered stock. Now documents.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MATERIAL DOCUMENT

Header (date, reference), items (movement type, qty, plant, sloc, batch, special stock).

━━━━━━━━━━━━━━━━━━━━
▶ 2. ACCOUNTING DOCUMENT

Created for value updates; FI document linked to material document.

━━━━━━━━━━━━━━━━━━━━
▶ 3. UPDATES

Stock quantity/value, reservations, PO history, orders.

━━━━━━━━━━━━━━━━━━━━
▶ 4. REVERSALS

Cancellation creates reversal document (e.g. 102, 202, 262).

━━━━━━━━━━━━━━━━━━━━
▶ 5. DISPLAY AND LISTS

MIGO display, MB51 list, FI follow-on documents.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Post 201 with reference to a reservation.
Display material and FI documents.
Reverse the posting.

✅ CHECKPOINT: document flow shows original and reversal, and the reservation is reopened.

Code example

ABAP Code

===== STEP 1: documents =====MIGO post → material document 4900000123 (year) → accounting document 5000000456MB51: list by material/movement type/date ===== STEP 2: updates =====201 with reservation → stock ↓, value ↓, reservation withdrawn qty ↑ ===== STEP 3: reversal =====MIGO cancellation → 202 document → stock and value restored, reservation reopened

Real project scenario

Finance saw an unexpected inventory credit posting. Tracing the accounting document back to its material document showed a 561 initial entry reversal posted by mistake during go-live corrections. The team restricted initialization movement types and introduced document reviews.

Common mistakes

Trying to change documents.
Not linking FI to material docs in analysis.
Deleting instead of reversing.
Wrong reference data.
Ignoring reservation updates.

Best practices

Correct via reversals.
Use document flow in analysis.
Enter references (delivery note).
Restrict sensitive movement types.
Review MB51 exceptions.

Interview angle

Questions: "What documents does a goods movement create?", "How do you reverse a movement?", "Can you change a material document?"
Strong answer: material and accounting documents, updates, reversals, display and lists.

Practice this lesson

Quick check

1. A warehouse worker mistakenly posts a goods receipt against the wrong purchase order using movement type 101. What is the correct standard approach to correct this in Inventory Management?

2. In the Procure-to-Pay process, what is the primary purpose of the GR/IR clearing account in Inventory Management and Invoice Verification?

3. Finance sees an unexpected inventory credit. How do you trace its cause?

Interview questions

1. In a scenario where reservations for production orders are not being consumed correctly and stock appears reserved but unavailable for other orders, what root causes would you investigate from an inventory management perspective?

Answer it in your own words first, then compare.

2. How would you analyse a wrong inventory posting from finance back to its logistics origin?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.