SAPFree referencePDF, Excel, Word exportSAPPharma and Life Sciences

SAP Batch Management T-Codes, Tables and Movement Types for GMP

In a GMP plant, SAP batch management is the backbone of traceability: every receipt, issue, inspection and release is tied to a batch number. This lookup lists the transactions, tables and movement types that quality and IT teams use most.

Download:

Code or table	Type	Description	GMP use
MSC1N	Transaction	Create Batch	Create a batch master record before goods receipt or production
MSC2N	Transaction	Change Batch	Update shelf life dates, status and batch characteristics
MSC3N	Transaction	Display Batch	Review batch master data during release or investigation
MSC4N	Transaction	Display Batch Changes	Review change documents for a batch master
MB56	Transaction	Batch Where-Used List	Trace a component batch forward or a finished batch backward
MB51	Transaction	Material Document List	List goods movements by material, plant and batch
MB52	Transaction	List of Warehouse Stocks on Hand	Stock by batch and storage location
MB5B	Transaction	Stock on Posting Date	Reconstruct batch stock as of a past date
MMBE	Transaction	Stock Overview	Check quality inspection, blocked and unrestricted stock by batch
COR3	Transaction	Display Process Order	Review components and batches consumed in a process order
CO03	Transaction	Display Production Order	Review components and batches consumed in a discrete order
QA32	Transaction	Inspection Lot List	List inspection lots by material and batch
QA03	Transaction	Display Inspection Lot	Review specification, results and status for a lot
QA11	Transaction	Record Usage Decision	Accept or reject the lot and trigger stock posting
QE51N	Transaction	Results Recording Worklist	Enter lab results against inspection characteristics
QM01	Transaction	Create Quality Notification	Raise a deviation or complaint record
QM03	Transaction	Display Quality Notification	Review a deviation or complaint record
QP01	Transaction	Create Inspection Plan	Define test steps for a material
QS21	Transaction	Create Master Inspection Characteristic	Define reusable test characteristics and limits
CT04	Transaction	Characteristics Maintenance	Define batch characteristics such as potency or assay
CL30N	Transaction	Find Objects in Classes	Search batches by characteristic values
BMBC	Transaction	Batch Cockpit	Review batch master, stocks and where-used in one screen
MCH1	Table	Batches, cross-plant	Batch master data at material level
MCHA	Table	Batches, plant level	Batch master data at plant level
MCHB	Table	Batch Stocks	Stock quantities by batch, plant and storage location
MKPF	Table	Material Document Header	Posting date and document header for goods movements
MSEG	Table	Material Document Segment	Material, batch, quantity, movement type and order number per line
AFKO	Table	Order Header Data	Order dates and header data for production and process orders
AFPO	Table	Order Item	Order item, material and planned quantity
QALS	Table	Inspection Lot Record	Inspection lot header with material, batch and plant
QAVE	Table	Inspection Usage Decision	Usage decision code and date per lot
QMEL	Table	Quality Notification	Notification header for deviations and complaints
KLAH	Table	Class Header Data	Class definitions used by batch classification
AUSP	Table	Characteristic Values	Stored characteristic values, including batch values
INOB	Table	Link Between Object and Classification	Links a batch object to its class
101	Movement type	Goods receipt	Receipt against a purchase order or process order
261	Movement type	Goods issue for order	Component consumption into a production or process order
262	Movement type	Reversal of goods issue for order	Return of components from an order
321	Movement type	Transfer posting, quality inspection to unrestricted	Release after a positive usage decision
322	Movement type	Transfer posting, unrestricted to quality inspection	Move stock back into inspection
343	Movement type	Transfer posting, blocked to unrestricted	Release blocked stock after investigation
344	Movement type	Transfer posting, unrestricted to blocked	Quarantine suspect stock
551	Movement type	Goods issue for scrapping	Destruction of rejected stock
601	Movement type	Goods issue for delivery	Shipment of released batches to customers

Transaction availability depends on SAP release, role design and add-ons. Table and field names are standard SAP, but custom enhancements are common in regulated plants. Verify in your system with SE11 and SE93.

Ask SAP batch questions in plain language

An optional review of a read-only, on-prem assistant for batch genealogy and release status.

Optional. The tool and every export work without this. No spam.

How to use the list

Search for a batch task such as where-used, release or scrap and the rows show the transaction, the tables behind it and the movement type it posts. Filter by type to list only tables when you are building a report, or only transactions when you are writing a work instruction for operators. Export the filtered list to Excel for a validation traceability matrix or a role design workshop.

Batch traceability in practice

Forward trace starts at a component batch and finds every order that consumed it through movement 261. Backward trace starts at a finished batch, finds the order that received it through movement 101, then reads the components consumed by that order. MB56 performs this in the SAP GUI, while a SQL or ABAP query over MSEG and MKPF can handle bulk traces during a recall.

Quality release and stock status

A batch usually enters inspection stock after goods receipt, an inspection lot is created, results are recorded and a usage decision moves the stock. Movement 321 releases inspection stock to unrestricted use, while 343 and 344 move stock between blocked and unrestricted status. Control who can post these movements, because they are the point where a quality decision becomes a stock change.

Restrict QA11 and release movements to authorised roles.
Review change documents with MSC4N for batch master edits.
Check stock status with MMBE before shipment.

Common mistakes

People trace only the plant they know and miss transfers between plants. Others rely on MCHB for history, but it holds current stock rather than movements. Use MSEG and MKPF for history. In validated systems, also remember that custom Z transactions and enhancements can change the standard behaviour listed here.

Frequently Asked Questions

Which SAP transaction shows where a batch was used?

MB56, the Batch Where-Used List, shows forward and backward relationships for a batch. For large recalls or custom reports, teams often query the material document tables MSEG and MKPF directly, filtering by batch and movement type.

What is the difference between MCHA and MCHB?

MCHA holds batch master data at plant level, such as dates and status. MCHB holds the stock quantities for each batch by plant, storage location and stock category. Neither holds the movement history, which is in MSEG and MKPF.

Which movement type releases a batch from quality inspection?

Movement 321 transfers stock from quality inspection to unrestricted use. It is normally posted automatically from the usage decision when a lot is accepted, but some plants post it manually under controlled authorisations.

Are these codes the same in S/4HANA?

Most are, but S/4HANA changes some data models, for example material documents and batch handling, and certain tables may be compatibility views. Check each object in your own release with SE11 and your vendor documentation.

Netray can build a private, read-only tracing assistant on top of your SAP batch data, so quality can ask for a forward or backward trace in plain language and see the query behind the answer.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

More SAP tools

See all

Back to All Tools