Batch Report in SAP PP: Where-Used and Traceability Tcodes
batch report in sap pp
Also searched as
- sap batch where used list
- sap batch traceability report
- MB56 batch where-used
- sap batch information cockpit
Short answer
For batch traceability in SAP PP use MB56 (batch where-used list, up and down), BMBC (batch information cockpit) and MSC3N (display batch master). For stock by batch use MMBE, MB52 or MB5B, and for movements MB51 with the batch filter. Batch master data sits in tables MCH1 (client level), MCHA (plant) and MCHB (stock per batch).
Applies to: SAP ECC 6.0 and S/4HANA with Batch Management active for the material and plant
Run a batch where-used report
- 1Confirm the material is batch managed (MM03, Plant data/stor.1 view, Batch management indicator).
- 2Run MB56 (Batch Where-Used List). Enter material, batch and plant.
- 3Choose the direction: where-used down shows consumption (which orders, deliveries and customers received the batch); up shows which component batches went into the finished batch.
- 4Display the tree, then drill into production orders, goods movements and deliveries from the nodes.
- 5For a single screen of everything about a batch, use BMBC (Batch Information Cockpit) with selection by material, batch, plant, characteristics or shelf life dates.
- 6For stock by batch: MMBE, MB52 (warehouse stocks of material) or MB5B (stock on a past date).
- 7For goods movements by batch, run MB51 and fill the Batch field in the selection.
Which report answers which question
MB56 is the recall report: given a finished batch, find the raw material batches (up) or the customers (down). BMBC is the cockpit for QA people who want stock, classification values and status in one place. MSC3N shows the batch master with classification (class type 023) values such as potency or supplier lot.
Production-side lists such as COOIS or CO24 help locate orders and components; combine them with MB51 filtered by order number to see actual batch consumption. Quality results per batch are available through QA32 and the inspection lot, see the QM reporting page.
Batch tables and a quick query
MCH1 holds batches at client level (material and batch), MCHA at plant level and MCHB the unrestricted, quality and blocked stock per storage location. MSEG carries the batch on each material document item, which is what MB51 reads.
In S/4HANA the same tables exist; MATDOC is the central document table, so MB51 style reports read from it. Use SE16N for a quick check but prefer standard reports in production.
SE16N MCHB: MATNR, WERKS, LGORT, CHARG, CLABS (unrestricted), CINSM (quality), CSPEM (blocked)
SE16N MSEG: filter CHARG = <batch>, AUFNR = <production order>
Setting up for recall readiness
Where-used lists only work if goods issues to orders and goods receipts carry the batch. Make batch entry mandatory with batch determination (strategy types in the PP/SD or MM setup) and avoid manual stock adjustments that skip the batch.
For traceability drills, run MB56 down from a raw material batch periodically on a test lot and check that every customer delivery appears. If it does not, there is a gap in the process, not in the report.
Try it here, free
SAP Batch Shelf Life Expiry Stock SQL Query Generator (MCH1, MCHB)
Build a SQL query that lists batches whose shelf life expiry date falls in a chosen window, with stock by status, for chemical and specialty products.
Common pitfalls
- !Using stock reports (MMBE) to answer a traceability question; stock shows what is on hand, not history.
- !Where-used going stale because goods receipts were posted without batches or via mass uploads that bypassed the batch.
- !Mixing plant-level and client-level batch settings (batch level) and wondering why a batch is not found.
- !Not retaining archived documents; where-used cannot read what has been archived.
How an ERP-grounded AI assistant handles this
Recall questions are usually phrased in plain language: which customers received anything made from this raw material lot. An assistant grounded in the SAP data can run the where-used logic across production orders and deliveries and return the answer with the query, read-only, within the user's authorizations.
Frequently asked questions
What is the main SAP tcode for batch where-used?
MB56 is the batch where-used list. It supports where-used up (what went into a batch) and down (where a batch went). BMBC gives a broader cockpit view with stock and classification.
Where is batch data stored in SAP?
Batch master data is in MCH1 at client level and MCHA at plant level. Stock per batch is in MCHB. Material document lines carry the batch in MSEG, and in S/4HANA also in MATDOC.
Can I see batch characteristics in a report?
Yes. Batch classification values are visible in MSC3N and BMBC. For lists with characteristics, use the batch selection by class in BMBC or classification reports based on the class type for batches.
Does this work in S/4HANA?
Yes. MB56, MSC3N and BMBC remain available, and batch tables continue to exist, although many material document reads now use MATDOC. Fiori apps for batch management are also available depending on release.
Related
SAP 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 QM inspection results report: which tcode shows what
Use QA32 for the list of inspection lots, QE51N or QE03 for recorded results, the QM information system (for example QM12) and QGC2 for evaluations of characteristics over time, and QA11 or QAVE for usage decisions. If none fits, read the tables QALS, QAMV, QAMR and QAVE directly.
How-toInspection Results and Inspection Plan Reports in SAP QM
For inspection results in SAP QM, list lots in QA32, display results per lot in QE03, and analyse them over time with the QM evaluation transactions such as QGC1. For inspection plans, QP01 to QP03 maintain and display plans and QP19 gives the where-used list that ties plans to materials. The data sits in QALS, QAMV, QAMR, QAVE, PLKO and MAPL.
How-toSAP PO Report by Creator: Transactions and EKKO-ERNAM
To list SAP purchase orders by who created them, run ME2N or ME80FN and filter on Created By (EKKO-ERNAM), using dynamic selections when the field is not on the selection screen. For a quick raw list, read table EKKO in SE16N with ERNAM set to the user ID. Save the selection as a variant so buyers and managers can rerun it.
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 Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting
AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.
Stuck on SAP ERP / S/4HANA?
Talk to engineers who work inside SAP ERP / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP Batch Shelf Life Expiry Stock SQL Query Generator (MCH1, MCHB)Build a SQL query that lists batches whose shelf life expiry date falls in a chosen window, with stock by status, for chemical and specialty products.
- SAP PP Database Tables ReferenceA lookup of the main SAP PP database tables, what each holds and the key fields to join on.
- SAP PP Production Order Variance CalculatorBreak the difference between target and actual production order cost into price, usage, rate and efficiency variances.
ERP fixes and how-tos
- SAP PP End to End Configuration: Steps, IMG Paths and Process FlowSAP PP end to end configuration in order: organizational structure, master data, MRP, order types, confirmation, costing and settlement, with IMG paths and tcodes.
- SAP PP Standard Reports: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRYThe standard SAP PP reports and transactions planners use: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRY, with what each shows and when to use it.
- SAP PM Reports: Key Plant Maintenance Tcodes and What They AnswerWhich SAP plant maintenance report answers which question: notifications IW28/IW29, orders IW38/IW39, equipment IH08, plans IP24 and operations IW49N.
AI on your ERP
- AI for SAP S/4HANA in Food and Beverage: Batch Traceability, Shelf Life and Recall ReadinessAI on SAP S/4HANA for food and beverage: batch traceability, shelf life, recalls and allergen data answered from live records, on-prem and read-only.
- AI on SAP Business One for Food and Beverage Manufacturers: Batch, Expiry and Recall Answers in SecondsPrivate AI on SAP Business One for food and beverage plants: batch and expiry lookups, recall tracing, recipe costing and yield variance, read-only and on-prem.