Warehouse Stock vs Inventory Management Mismatch

Warehouse operations report that the system says a bin is full or empty, but the physical count and the IM stock overview disagree with what the warehouse screen shows. Sometimes it surfaces as picking failing because 'system stock is zero' while a delivery clearly has material allocated against it. Sometimes finance flags it during a stock valuation run because quantities used for valuation do not tie out to what the warehouse team confirms is on the floor. It is also reported after a physical inventory count is entered but the variance report still shows the old numbers days later, or after a goods receipt is posted and the receiving team insists the pallet is sitting in the dock but MMBE shows it already in storage.

Pull MMBE and LS24 for the same material, plant, storage location, and batch at the same point in time and show the delta as a single number. Cross-reference LB01 for open TOs on that material and storage location for the same quantity or timeframe. If the delta lines up with an open TO or a queue entry with a timestamp matching the complaint window, the cause is proven without further investigation; if it does not line up with any open document, escalate as an actual physical loss or master data issue rather than a timing mismatch.

If the cause is an unconfirmed TO, confirm it (LT12) if the physical movement genuinely happened, or cancel it if it does not reflect reality — this is a data action, no transport needed. If stock is sitting in an interim storage type, complete the putaway or picking step that was interrupted rather than adjusting quantities; this is also a data fix. If a queue is stuck, reprocess it in SMQ2 or resend the failed IDoc after fixing the underlying error (often a missing storage bin or blocked material master) — an operational data fix, though the underlying cause (for example a bin determination failure) may point to a configuration gap in storage type search strategy or interim storage type assignment, which does need a transport. Manual IM postings against WM-managed storage locations should be corrected by reversing the posting and re-entering it through a proper TO-driven movement; blocking direct postings against WM storage locations is a configuration change in movement type control. Physical inventory differences need the corresponding warehouse-side difference document confirmed, not just the IM count document.

Do not close the discrepancy by adjusting one side's stock without finding which of the above created the delta; that converts a temporary timing issue into a permanent false stock position.

The reflex is a manual stock adjustment in Inventory Management — a 701/702 movement or a manual MIGO adjustment — to force MMBE to agree with whatever the warehouse team says is physically there. This clears the complaint for the moment but does not touch the bin quant, the open TO, or the stuck queue that caused the divergence. The next time that TO confirms or the queue processes, the original movement posts on top of the manual adjustment and the discrepancy reappears, usually larger and harder to trace because there is now an unexplained adjustment document in the material's history.

Warehouse operations owns clearing open transfer orders and completing interrupted putaway or picking. Basis or the interface team owns stuck qRFC/tRFC queues and failed IDocs in a decentralized or EWM landscape. The WM/EWM configuration consultant owns storage type search strategy and interim storage type assignment if the root cause is structural rather than a one-off stuck document. The handover note should include material, plant, storage location, batch, the exact delta quantity, the MMBE and LS24 screenshots used to prove it, and the open TO or queue ID responsible.