JinJin48

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

June 27, 2026 · 14 min read

SAP EWM Batch Characteristics

Batch Characteristics are classification attributes assigned to batch-managed materials through SAP’s classification system (class type 023). Each characteristic defines a data type and value range — for example, an expiry date, purity percentage, or storage temperature. Values are entered per individual batch and are then read by EWM during warehouse task creation to sort and filter batches according to FEFO, class-based search strategies, and quality inspection relevance. This article covers the three-step setup sequence (Characteristic → Class → Class-Material Assignment) and the per-batch value entry that activates classification-driven warehouse processes.

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

1.1 What Are Batch Characteristics?#

A Batch Characteristic is a descriptor — a named attribute with a defined data type and allowed values — that classifies individual batches of a material. Rather than storing every possible attribute directly on the batch record, SAP delegates classification to the general Classification System: characteristics are defined once in CT04, grouped into classes of type 023 in CL01, the class is assigned to a material-plant combination, and values are entered per batch on the Classification tab of MSC2N. EWM reads these values at task creation time to rank, filter, or sequence batches.

1.2 Characteristic Data Types#

The data type of a characteristic determines how values are stored, compared, and sorted. Choosing the wrong data type causes sort failures in FEFO strategies and breaks class-based batch searches.

Design principle: Always use DATE type for expiry-date characteristics — not CHAR. A CHAR expiry date cannot be sorted correctly by EWM’s FEFO strategy, and numeric comparisons on date strings produce incorrect results.

1.3 Organizational Levels and Data Hierarchy#

Batch Classification follows SAP’s Classification System using Class Type 023. The data lives at three layers, each populated via different transactions and stored in different tables:

Layer 1 — Definition (Client scope)
   │
   ├── Characteristic — CT04 → table CABN
   │      Defines a measurable attribute: name, data type, unit,
   │      allowed values, decimal places.
   │      Shared across all classes and materials that use it.
   │
   └── Class (Class Type 023) — CL01 → table KLAH
          Container for one or more characteristics.
          Class type MUST be 023 — EWM only reads this type.

       Class ↔ Characteristic link — table KSML
          Many-to-many: a Class can contain multiple Characteristics;
          a Characteristic can belong to multiple Classes.

Layer 2 — Activation (Material + Plant scope)
   │
   └── Material × Plant → Class — table KSSK
          Activates batch classification for this Material in this Plant.
          Without a KSSK row, the Classification tab in MSC2N is hidden
          and batch values cannot be entered.

Layer 3 — Values (Batch scope)
   │
   └── Batch × Characteristic → Value — table AUSP
          One row per (Batch × Characteristic).
          Maintained via MSC2N (Classification tab).
          Read by EWM at task creation for batch determination scoring.

Key design decision: Define characteristics before classes, and lock the data type and value range before go-live. A characteristic cannot be changed once values exist for it in production — plan the data type and value range during blueprint and lock them in before go-live.

1.4 Integration with Other Master Data Objects#

Batch Characteristics do not operate in isolation. Their values are meaningful only when the surrounding master data — Batch Master, Material Master classification tab, and EWM picking strategy — is configured consistently.

Part 2: EWM-Specific Field Details#

2.0 Scope of EWM Ownership#

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

2.1 Characteristic Definition#

A characteristic definition in CT04 is the foundation of the entire batch classification system. Every attribute that EWM will use to sort, filter, or evaluate batches must be defined here as a named characteristic with an explicit data type before it can be assigned to a class or receive values.

2.2 Class Definition#

A class of type 023 is the container that groups related batch characteristics and connects them to materials. The class definition controls which attributes are available for batch value entry and which EWM picking strategy configurations can reference.

2.3 Class-Material Assignment#

Assigning a type-023 class to a material-plant combination is the activation step that enables batch value entry for that material. Without this assignment, the Classification tab does not appear in MSC2N and EWM cannot read characteristic values for batch selection.

2.4 Batch Value Entry#

Batch value entry is the operational step where characteristic values are recorded for each individual batch. These values are the data that EWM reads at task creation to execute FEFO sorting, class-based batch selection, and quality-relevant batch routing.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction