JinJin48

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

June 27, 2026 · 13 min read

SAP EWM Batch Master

The Batch Master is the master data record that captures lot-specific information for batch-managed materials in SAP S/4HANA and EWM. Each batch is uniquely identified by the combination of Material, Plant, and Batch Number, and carries critical attributes such as manufacturing date, shelf life expiration date (SLED/BBD), classification values, and stock status. In SAP EWM, the Batch Master drives FEFO (First Expiry, First Out) picking strategy, batch-specific storage bin assignment, and batch split during putaway and packing. This article covers the Batch Master’s core concepts (Part 1) and the EWM-specific field details that warehouse consultants own or configure (Part 2).

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

1.1 What Is the Batch Master?#

A batch is a uniquely identifiable quantity of a material that shares the same production run, supplier lot, or quality characteristics. The Batch Master record stores the attributes of that specific lot — when it was made, when it expires, what classification values it carries, and what stock status it is in. Unlike the Material Master, which describes a material type, the Batch Master describes a particular physical instance of that material.

1.2 Batch Status Types#

The batch status (also called the batch classification status or restricted-use indicator in EWM) determines whether stock in a batch can be freely used in warehouse operations. Selecting the wrong status at goods receipt causes operational disruption — a batch that should be held for inspection may be picked before QM releases it.

Design principle: Define the initial stock status at goods receipt in the batch classification and QM integration settings during blueprint. Changing batch status after GR requires a special movement type (344/344-R) and leaves an audit trail.

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 a batch number is unique and cannot be changed afterward without complex data conversion.

Client scope
   │
   └── MCH1 — Batch Header (identity record)
          One row per (Material × Batch Number)
          Fields: batch number, material, creation date, external batch reference

Plant scope (per Plant: 1000, 2000, …)
   │
   └── MCHA — Batch per Plant (plant-specific attributes)
          One row per (Batch × Plant)
          Fields: Manufacturing date, SLED/BBD, total shelf life,
                  minimum remaining shelf life, vendor batch number,
                  country of origin, restricted-use indicator

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

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

Key design decision: Choose batch level (Client / Plant / Material) in Customizing (OMCT) before any production go-live. Changing it afterward requires a complex data conversion. Most process industry implementations use Plant level for batch number uniqueness.

1.4 Integration with Other Master Data Objects#

The Batch Master does not stand alone. It is the convergence point for quality, logistics, and warehouse data — every batch-triggered process in EWM traces back to data recorded here.

Part 2: EWM-Specific Field Details#

2.0 Scope of EWM Ownership#

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

2.1 Basic Batch Data#

Basic Batch Data forms the identity layer of the batch record — it establishes which material, which lot, and which plant the batch belongs to. This data is created in MM (MSC1N or automatically at GR) and is the anchor for all subsequent EWM operations.

2.2 Shelf Life Data#

Shelf Life Data is the most operationally critical section of the Batch Master in an EWM FEFO environment. These fields are the direct inputs to the FEFO picking strategy — if they are missing or incorrect at goods receipt, FEFO sort order breaks down silently and older batches may remain in stock past their expiry date.

2.3 Classification Data#

Classification Data stores the quality and specification values that distinguish one batch from another at the characteristic level. While the class and characteristic definitions are owned by QM/MM, EWM uses these values for batch determination during picking — selecting only batches that meet the outbound delivery’s required specification.

Prerequisite: Batch Classification cannot be used in EWM batch determination unless the batch class (023) is assigned to the material in the Material Master Classification View and characteristic values are populated on each batch. Missing values cause EWM to skip the batch in search criteria evaluation.

2.4 EWM Stock Control#

EWM Stock Control fields govern how the EWM system handles a specific batch within the warehouse — which stock type it occupies, whether it can be freely transferred, and whether it is assigned to a dedicated bin. These fields are EWM-specific and are the primary levers the warehouse consultant configures to enforce lot integrity and quality segregation.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction