SAP MMBE Stock Overview: How to Run It, Read It and When to Use MB52 or MD04
mmbe sap tcode
Also searched as
- sap mmbe report
- mmbr report in sap
- mmbe table in sap
- mmbe vs mb52 vs md04
Short answer
MMBE is the SAP stock overview transaction. Enter a material (and optionally plant) and it shows stock in a tree by company code, plant, storage location and batch, split into unrestricted, quality inspection, blocked, in transit and special stocks. It is a single-material view. For lists across many materials use MB52, and for stock against demand use MD04. If you searched MMBR, you almost certainly meant MMBE.
Applies to: SAP ECC 6.0 and S/4HANA. In S/4HANA stock is derived from the material document table MATDOC, and the older table names are compatibility views.
How to run MMBE and read the result
- 1Open transaction MMBE and enter the material number. Add plant, storage location or batch if you want to narrow the tree.
- 2Execute. The result is a hierarchy: client, company code, plant, storage location, then batch if the material is batch-managed.
- 3Read the columns: unrestricted use, quality inspection, blocked, stock in transfer, restricted-use and returns, depending on layout.
- 4Expand a plant or storage location node to drill down. Double click a quantity to see the underlying stock record.
- 5Open the special stock nodes (vendor consignment, sales order stock, project stock) if the material uses them.
- 6For a list across many materials, switch to MB52. For stock versus requirements, use MD04.
- 7Download or export the screen if you need to share it; use the layout button to change columns.
What the stock types mean
Unrestricted-use stock is what can be issued, sold or consumed. Quality inspection stock is held until a usage decision is made. Blocked stock is unavailable by decision, such as damaged or under hold. Stock in transfer covers transfers between storage locations or plants that are not yet fully posted, and restricted-use applies to batches with limited use.
Planners should read availability from MD04 as well, since MMBE shows physical stock only, not the reservations, planned receipts and demand that drive what is actually available to promise.
Tables behind the report
In classic ECC, plant-level stock is in MARC, storage location stock in MARD (fields such as LABST for unrestricted, INSME for quality inspection, SPEME for blocked), batch stock in MCHB, and special stocks in tables such as MSKA (sales order stock) and MSLB (vendor special stock). The material master valuation lives in MBEW.
In S/4HANA the movements are stored in MATDOC and aggregate stock is calculated from it, with compatibility views keeping the old table names readable. Do not write to these tables, and check your release before building custom reports that assume the old structure.
MMBE Stock overview (one material, tree view)
MB52 Warehouse stocks of material (list view)
MD04 Stock/requirements list
MB5B Stock on posting date
MB51 Material document list
Tables: MARC, MARD, MCHB, MSKA, MSLB, MBEW
S/4HANA: MATDOC
Choosing between MMBE, MB52 and MD04
Use MMBE when you ask 'where is the stock for this one material, in which batch and state?'. Use MB52 when you need a list of many materials by plant and storage location, with value, exportable to a spreadsheet. Use MD04 when you ask whether there is enough, since it nets stock against requirements and shows planned receipts.
For history, MB5B gives stock on a past date, and MB51 shows the movements that explain a change. These cover most stock questions without custom reports.
Try it here, free
SAP ABAP Stock Below Safety Stock Report Generator
Produces a small ABAP report that joins MARC and MARD to list materials with unrestricted stock under the safety stock for a plant and MRP controller.
Common pitfalls
- !Reading unrestricted stock as available to promise without checking reservations and open orders in MD04.
- !Searching MMBR: the correct transaction is MMBE.
- !Forgetting that batch-managed materials need the batch node expanded to see the real split.
- !Reporting directly off MARD in S/4HANA and expecting write access or old behaviour.
- !Ignoring special stock nodes, so consignment or project stock appears missing.
How an ERP-grounded AI assistant handles this
Stock questions are the most common thing planners ask SAP. A grounded assistant can answer 'how much of material X is unrestricted at plant 1000, and what is on order?' in one step by reading the same sources as MMBE and MD04 under the asker's authorizations, and it shows the query it ran. Netray's ERPray layer can run on-prem, read-only.
Frequently asked questions
What is the MMBE transaction in SAP?
MMBE is the stock overview transaction. You enter a material and it displays stock in a hierarchy of company code, plant, storage location and batch, with quantities by stock type such as unrestricted, quality inspection and blocked.
What is the difference between MMBE and MB52?
MMBE is a single-material tree view that is good for drilling into batches and stock types. MB52 is a list report across many materials, plants and storage locations, with values, and it is easier to export and filter.
Which tables does MMBE read?
In ECC, mainly MARC, MARD and MCHB for plant, storage location and batch stock, plus special stock tables such as MSKA and MSLB. In S/4HANA the data is derived from the material document table MATDOC through compatibility views.
Is MMBR a real SAP transaction?
People often type MMBR when they mean MMBE. If you meant the stock overview, use MMBE. For multi-material stock lists use MB52 and for requirements planning use MD04.
Related
How to Read MD04 Exception Messages in SAP
The exception indicator in MD04 flags procurement elements whose date or quantity no longer matches the current demand situation - it is SAP's built-in change signal, read element by element in the detail screen, not just the header icon. Triage by exception group first, then decide to reschedule, cancel, or accept each one.
How-toAPI_MATERIAL_STOCK_SRV: reading SAP stock by plant and storage location with OData
API_MATERIAL_STOCK_SRV is the released OData V2 service for reading material stock in S/4HANA. Its main entity set, A_MatlStkInAcctMod, returns stock quantities by material, plant, storage location, batch and stock type. Activate the service, authorize a technical user and filter with $filter on Material and Plant.
How-toSAP PP Standard Reports: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRY
The core standard reports in SAP PP are COOIS (order information system), CO46 (order progress), MD04 (stock and requirements list), CM01 (capacity load by work center), CS12 (multilevel BOM) and COGI (goods movement errors). PPIO_ENTRY is an entry point to the order information system with list-based selection for orders, operations and components.
How-toSAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables
Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP ABAP Stock Below Safety Stock Report GeneratorProduces a small ABAP report that joins MARC and MARD to list materials with unrestricted stock under the safety stock for a plant and MRP controller.
- SAP MD04 Exception Messages and MRP Elements ReferenceA searchable lookup of MD04 element abbreviations, key exception messages and the MRP transactions you use to act on them.
- SAP QM Tables Map: Notification, Inspection Plan and ResultsFind the SAP QM table for a quality notification, inspection plan, sample or result, with key fields and the table it joins to.
ERP fixes and how-tos
- Contract, MMBE and PPV Reports in SAP MMRun contract reports in SAP MM with ME2M and ME2N, check stock with MMBE, report purchase price variance and build custom MM reports with SQ01 and CDS views.
- SAP M7 021: Deficit of SL Stock QuantitySAP M7 021 Deficit of SL stock quantity means you are issuing more stock than exists for that batch. Here is the fix and the OMJ1 config behind it.
- How to Read MD04 Exception Messages in SAPMD04 exception icons tell a planner why a procurement element no longer matches demand. Read the element detail and act on it, not just rerun MRP.
AI on your ERP
- AI for SAP Business One Inventory: Stock, Batches, Bins and ValuationPrivate AI over SAP Business One inventory: OITW stock, batches, serials, bins and valuation. Answers grounded in live data via Service Layer or SQL views.
- AI Agents for SAP Production Planning, MRP, and Exception TriageAI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.