Physical Inventory
MM / P2Padvanced

MM Physical Inventory Part 4: Zero Count, Recount and Freeze Book Inventory

Key takeaway

Handle tricky counts: zero counts (counted quantity 0 vs not counted), recounts for large differences, freeze book inventory versus posting block, goods movements during counting, batches and special stocks in counts, and late counts after the key date.

Explanation

📌 KEY POINTS
✅ A zero count must be entered explicitly (zero count flag); an empty field means "not counted".

✅ Recount (MI11) creates a new document item for re-verification of large differences.

✅ Freeze book inventory fixes the book quantity at document creation; posting block prevents movements entirely.

✅ Movements between count and posting must be considered (cut-off, freeze, or timing of posting).

⚠️ Treating "not counted" as zero posts full stock as loss.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 3 covered methods. Now special situations.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ZERO COUNTS

  • Explicit zero count indicator; review before posting.

━━━━━━━━━━━━━━━━━━━━
▶ 2. RECOUNT

  • MI11 for items above thresholds; audit trail.

━━━━━━━━━━━━━━━━━━━━
▶ 3. FREEZE VS BLOCK

  • Freeze: movements allowed, comparison with frozen book qty.
  • Block: movements blocked for the items.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MOVEMENTS DURING COUNT

  • Cut-off procedures; count date vs posting date.

━━━━━━━━━━━━━━━━━━━━
▶ 5. BATCHES AND SPECIAL STOCK

  • Count per batch; special stocks with own documents.

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

  1. Enter a zero count for one item.
  2. Recount an item with big difference.
  3. Test movements with freeze vs block.

✅ CHECKPOINT: zero counts are explicit and recounts documented.

Code example

ABAP Code
===== STEP 1: zero count =====MI04: counted quantity blank + zero count flag X → counted as 0 ===== STEP 2: recount =====MI20 difference list → MI11 recount → new count → MI07 post ===== STEP 3: freeze vs block =====Freeze book inventory: book qty frozen, movements allowed | posting block: movements not possible for item

Real project scenario

A material was physically zero, but the counter left the quantity blank. Later the item was posted as "not counted" and excluded, leaving phantom stock for months. Training and a mandatory zero-count flag in the count procedure fixed it.

Common mistakes

  • Blank instead of zero.
  • No recount thresholds.
  • Confusing freeze and block.
  • Ignoring movements after count.
  • Counting batches in total.

Best practices

  • Train zero count entry.
  • Define recount thresholds.
  • Choose freeze/block deliberately.
  • Apply cut-off rules.
  • Count batches separately.

Interview angle

Questions: "How do you enter a zero count?", "What is a recount?", "Freeze book inventory vs posting block?"
Strong answer: zero count flag, MI11 recount, freeze vs block, cut-off, batches/special stock.

Practice this lesson

Quick check

1. What is the effect of activating the posting/stock block indicator when creating a physical inventory document?

2. If a counted quantity entered for a physical inventory document is later found to be incorrect before the difference is posted, what function should be used to correct it?

3. A material is physically zero, but the counter left the quantity blank. What happens?

Interview questions

1. During an active physical inventory count freeze at a plant with Material Ledger running in the background, a warehouse team posts a goods issue (movement type 201) for an urgent production need before the count is finalized. The Material Ledger quantity and value later appear inconsistent with the physical count results. How would you troubleshoot this?

Answer it in your own words first, then compare.

2. During a physical inventory count of blocked stock (movement type 344), which transaction key determines the GL account for the count difference, and how does configuration differ from unrestricted-use stock differences?

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.

More lessons in this topic

Interview questions on this topic

Related SAP topics