JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 23, 2026 · 13 min read

SAP MM Batch Master

The Batch Master is the master data record that represents a uniquely identified lot, production run, or delivery unit of a material. Where the Material Master defines what a material is, the Batch Master defines a specific, traceable instance of it — capturing production dates, expiration dates, quality status, and vendor-assigned lot numbers. Every goods movement, quality inspection, and shelf-life check in SAP traces back to a Batch Master record. This article covers the object’s scope, types, organizational levels, integration points, and the MM-specific fields that consultants configure and maintain.

Part 1: Batch Master — Core Concepts (All Modules)#

1.1 What Is the Batch Master?#

A batch is a subset of a material’s total stock that is managed as a separate, uniquely identified unit throughout its lifecycle — from goods receipt through storage, consumption, and disposal. The Batch Master record stores the lot-specific attributes that distinguish one batch from another: when it was made, when it expires, who supplied it, and whether it is unrestricted, restricted, or blocked for use.

1.2 Batch Level Options#

The batch level setting controls at which organizational scope a batch number is unique. This is a client-wide Customizing setting (transaction OMCE) and cannot be changed after batches exist — making the batch level decision one of the most consequential configuration choices in an MM implementation.

Design principle: Batch level must be agreed between MM, QM, and PP during blueprint. Client-level batches are required when cross-plant stock transfers must preserve batch identity and when the same batch is inspected once and results must be visible plant-wide.

1.3 Organizational Levels and Data Hierarchy#

A Batch is not a single record but a set of related entries across four SAP tables, each maintained at a different organizational scope. The batch level (Client / Plant / Material) is a Customizing decision (OMCT) made before go-live — it controls how widely the batch number is unique and cannot be changed afterward without complex data conversion.

Client scope
   │
   └── Batch Header (MCH1) — identity record
          One row per (Material × Batch Number).
          Fields: batch number, material, batch status, creation date,
                  SLED (shelf life expiry), MHD (best-before date),
                  vendor batch number, date of manufacture.

Plant scope (per Plant)
   │
   └── Batch per Plant (MCHA) — plant-specific attributes
          One row per (Batch × Plant).
          Fields: plant-level batch status, plant-level shelf life,
                  last goods movement date, QM classification link,
                  restricted-use indicator.

Storage Location scope (per Plant + Storage Location)
   │
   └── Batch Stock per Storage Location (MCHB)
          One row per (Batch × Plant × Storage Location).
          Fields: unrestricted, quality inspection, blocked,
                  restricted-use stock quantities.

Cross-cutting (linked by batch number, optional)
   │
   └── Batch Classification (MCH7) — Class Type 023
          One row per (Batch × Characteristic).
          Fields: class assignment, characteristic values.

Key design decision: For regulated industries, shelf life dates (SLED) must be maintained at MCH1 level and are automatically proposed during goods receipt if the material’s shelf life settings are active in the Material Master (MRP / Purchasing views). Inconsistent shelf life data between MCH1 and MCHA is a common source of batch availability errors.

1.4 Integration with Other Master Data Objects#

The Batch Master is not created in isolation. It is downstream of the Material Master and Classification objects, and is consumed by QM, PP, and WM processes.

Part 2: MM-Specific Field Details#

2.0 Scope of MM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Basic Data#

Basic Data captures the identifying and sourcing information for each batch. These fields are typically populated at goods receipt and drive traceability reporting.

2.2 Shelf Life Data#

Shelf life management is the most operationally significant part of the Batch Master for food, pharma, chemical, and consumer goods industries. Fields in this section control batch availability and FEFO (First Expired First Out) picking.

2.3 Batch Status#

Batch status controls which stock category a batch’s inventory falls into and determines which transactions can consume or move the batch. It is the primary mechanism for quality hold management in MM.

Design principle: Batch status changes should be governed by a clear process — either through QM usage decisions (system-driven) or through an MM-authorized change in MSC2N (manual). Uncontrolled manual status changes are an audit risk in GxP environments. Establish a change log and approval workflow for batch status changes as part of the QM-MM integration design.

2.4 Classification (Characteristic Values)#

Batch classification enables capturing lot-specific quality, compositional, or process attributes and using them for batch search, selection, and reporting. It is the bridge between the Batch Master and the Classification module (Phase 3).

Prerequisite: Class and Characteristic objects (Phase 3 — MM-A04-01, MM-A04-02) must be created and class type 023 activated before batch classification can be used. Batch classification setup should be included in the Phase 3 workbook even though it is used in Phase 4.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction