# SAP MMBE Stock Overview: How to Run It, Read It and When to Use MB52 or MD04 > Source: https://netray.co/erp-help/sap-mmbe-stock-overview-report-tcode-tables-alternatives > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module Inventory Management / Stock Reporting ## Query mmbe sap tcode ## Alternate Queries - sap mmbe report - mmbr report in sap - mmbe table in sap - mmbe vs mb52 vs md04 ## 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. ## Steps ### How to run MMBE and read the result **Items:** - Open transaction MMBE and enter the material number. Add plant, storage location or batch if you want to narrow the tree. - Execute. The result is a hierarchy: client, company code, plant, storage location, then batch if the material is batch-managed. - Read the columns: unrestricted use, quality inspection, blocked, stock in transfer, restricted-use and returns, depending on layout. - Expand a plant or storage location node to drill down. Double click a quantity to see the underlying stock record. - Open the special stock nodes (vendor consignment, sales order stock, project stock) if the material uses them. - For a list across many materials, switch to MB52. For stock versus requirements, use MD04. - Download or export the screen if you need to share it; use the layout button to change columns. ## Sections ### What the stock types mean **Body:** 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 **Body:** 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. **Code:** - 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is the MMBE transaction in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms mmbe sap tcode, sap mmbe report, sap stock overview, mmbe table sap, mmbe vs mb52, sap stock by batch, mb52 sap, sap stock unrestricted quality inspection blocked --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json