MM / P2Padvanced

MM Goods Receipt and Goods Issue Part 5: Troubleshooting Goods Movements — Quantity, UoM, Batch, Period and Authorization

Key takeaway

Diagnose failed or wrong goods movements: deficit of stock, closed posting periods, unit of measure conversions, batch and serial number requirements, missing account determination, tolerance errors, authorization and stock type issues — with messages and fixes.

Explanation

📌 KEY POINTS
✅ "Deficit of stock" usually means the stock is in another stock type, storage location, batch or special stock.
✅ Posting period errors come from MM period not opened (MMPV) or FI periods closed.
✅ Unit conversions (order unit vs base unit) and batch requirements cause wrong quantities or blocks.
✅ Account determination errors stop valuated postings.
⚠️ Posting corrections without understanding the cause creates new stock and value differences.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered finance. Now troubleshooting.

━━━━━━━━━━━━━━━━━━━━
▶ 1. STOCK ERRORS

Deficit: check MMBE by sloc, stock type, batch, special stock.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PERIOD ERRORS

MMPV/MMRV current period; FI posting periods (OB52).

━━━━━━━━━━━━━━━━━━━━
▶ 3. UOM AND BATCH

Conversion factors; batch mandatory; serial numbers.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ACCOUNT DETERMINATION

Missing OBYC entries for valuation class/modifier.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TOLERANCES AND AUTHORIZATIONS

Over-/underdelivery; movement type authorizations; plant restrictions.

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

Reproduce an error; read the message long text.
Check stock/period/UoM/batch/account data.
Fix at source and repost.

✅ CHECKPOINT: every recurring error has a documented cause and fix.

Code example

ABAP Code

===== STEP 1: common messages =====M7 021 deficit of stock → MMBE stock by sloc/type/batch/special stockPosting only possible in periods … → MMPV (MM period) / OB52 (FI)Account determination for entry … not possible → OBYC (BSX/GBB/WRX) for valuation class ===== STEP 2: UoM/batch =====Order unit PAL = 40 CS, CS = 12 EA → check conversions in material master | batch mandatory → enter batch ===== STEP 3: authorizations =====Movement type/plant authorizations (e.g. M_MSEG_BWA, M_MSEG_WWA)

Real project scenario

Warehouse reported "deficit of stock" while 500 units sat on shelves. MMBE showed them in quality inspection stock from an earlier GR without usage decision. Completing the QM usage decision released stock to unrestricted and the issue posted; the team added a daily list of old quality stock.

Common mistakes

Posting workarounds (501/561).
Ignoring stock types.
Wrong UoM conversions.
Periods not opened.
Missing OBYC entries.

Best practices

Read message long texts.
Check stock by type and sloc.
Validate UoM conversions.
Automate period opening.
Keep a troubleshooting runbook.

Interview angle

Questions: "Deficit of stock although stock exists — why?", "Posting period error?", "Account determination error?"
Strong answer: stock type/sloc/batch/special stock, MMPV/OB52, UoM and batch, OBYC, tolerances and authorizations, runbook.

Practice this lesson

Quick check

1. A goods movement fails with "posting only possible in periods…". What should be checked?

2. A goods issue fails with an account determination error. Where is the missing entry usually found?

3. Warehouse gets "deficit of stock" although units are on the shelf. What should be checked first?

Interview questions

1. Warehouse goods receipts processed in a decentralized EWM system are arriving in ERP/S4 with a noticeable delay, causing GR/IR aging reports to show open items that later resolve automatically once the EWM confirmation syncs. How would you architect monitoring to distinguish this from real reconciliation issues?

Answer it in your own words first, then compare.

2. Your MDG system pushes vendor master changes into the SAP ERP backend nightly, but a batch of GR/IR clearing postings failed overnight because vendor bank data updates from MDG created a lock on vendor master records mid-posting run. How would you diagnose and resolve this integration conflict?

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.