MB52 — Warehouse Stock Overview by Plant and Storage Location

MB52 pulls current on-hand quantities for selected materials across plant, storage location and batch, split by stock category: unrestricted use, quality inspection, blocked, stock in transfer, and stock in transit between plants. The single structural fact that causes most confusion is that MB52 is a quantity report, not a value report and not a document history. It aggregates whatever is currently sitting in the underlying stock tables at the moment the report runs. It does not show what was posted yesterday, what is on open purchase orders, or what is reserved for a sales order unless that special stock type is explicitly included in the selection. Anyone expecting a running balance or a value figure from MB52 is looking at the wrong transaction.

MB52 is the first stop when a user says stock looks wrong after a goods movement, before a physical inventory count is scheduled, or before manually adjusting stock to confirm what the system actually holds versus what the warehouse reports. It is also used to sanity-check MRP or availability results by seeing raw on-hand quantity without ATP logic applied. Consultants reach for MB52 over MMBE when the question spans many materials or many plants at once, since MB52 is a flat list suited to mass extraction and sorting; MMBE is better for drilling into one material's full stock picture including special stocks in a hierarchical tree. Neither shows financial value.

Open SE16 on MARD, filter by material number and plant, and compare the unrestricted-use quantity field, the quality inspection quantity field, and the blocked stock quantity field against the corresponding column in the MB52 output for the same selection. If the material is batch-managed, the MARD total should equal the sum of the matching rows in MCHB for that plant and storage location; a mismatch usually means a batch split that MB52 is displaying correctly but the user is reading as one line. If special stock is involved, check MSKA or MKOL separately, since those quantities sit outside MARD entirely.

MB52 continues to work in S/4HANA without functional change to its selection screen or logic. A Fiori app covering stock overview is available for users on the Fiori launchpad, offering similar quantity-by-category views with better filtering, but the underlying read logic and the quantity-only nature of the report are unchanged. Consultants supporting an S/4HANA client can still rely on MB52 directly when the Fiori app is not yet rolled out to a given user group.

This is a functional MM inventory management issue in almost every case; FI gets involved only if the complaint is actually about stock value rather than stock quantity. A good handover includes the material, plant, storage location, batch if relevant, the stock category in question, a screenshot of the MB52 output, and the expected quantity with the reasoning behind that expectation.

Once MB52 confirms a quantity discrepancy, the next step is usually checking the goods movement transactions that created or should have created the stock: MB1C for goods receipt without reference, MB1B for transfer postings between storage locations or plants, and MB03 to inspect the specific material document that posted the movement in question. If the complaint is actually about value rather than quantity, MB5L gives the stock value view instead of the quantity-only view MB52 provides, and is the correct next stop for that class of question.