📦 SAP Batch Management — When to Use vs Standard

1. What SAP standard already does — WITHOUT batch management

Before reaching for batch management, know what standard MM gives you for free:

• ✅ Stock per plant + storage location (quantity)
• ✅ Stock status — unrestricted, quality, blocked, returns
• ✅ Movement type history (which transactions moved stock)
• ✅ Material document trail (date, user, qty, reference)
• ✅ Plant-level valuation (one price per material per plant)
• ✅ Vendor history per material (info records, source list)

2. When you actually NEED batch management

Batch management becomes necessary when you need to track stock at a finer granularity than plant + SL:

3. What batch enables that standard CAN'T do

4. How to activate — configuration steps

1. Decide batch level — OMCT

   Three options:

   • Client level — batch number unique across all plants and materials (rare)
   • Material level — batch unique per material across plants (common)
   • Plant level — batch unique per material per plant (most common)

   Recommendation: Plant level for most projects. Easier to manage.

2. Set Material Master flag — MM02 → Plant Data / Storage 1 view

   Tick XCHPF "Batch Management". This activates batch behavior for this specific material at this plant.

   If material is already used, system warns — you can activate going forward (new batches created), but existing stock won't be retroactively batched.

3. Choose batch number assignment — OMCT
   • Internal numbering — system auto-generates (e.g. 0000000001, 0000000002...)
   • External numbering — user enters batch number on GR (e.g. "VENDOR-LOT-202605")

   For pharma/food, external is often preferred (matches vendor's lot ID).

4. Define batch class — CL02

   Class type 023 for batches. Add characteristics that describe the batch.

5. Define characteristics — CT04

   Examples: ProductionDate, ExpiryDate, TensileStrength, Grade, OriginCountry, FurnaceNumber.

6. Define search strategy — OMCY

   Common strategies:

   • FEFO — First-Expired-First-Out (food, pharma)
   • FIFO — First-In-First-Out (general)
   • LIFO — Last-In-First-Out (steel where new is preferred)
7. Activate shelf life (if needed) — MM02

   Storage 1 view: MHDRZ (min remaining shelf life), MHDHB (total shelf life), IPRKZ (period D/W/M).

5. Batch classification with characteristics

The real power of batch management = classification. You don't just track that there's a batch — you track WHAT'S SPECIAL about each batch.

Example — PSEC Steel Rod batch classification

Class: STEEL_BATCH (Class type 023)

Characteristics:
  HEAT_NO         — Furnace heat number (e.g. H-25-05-001)
  TENSILE_MPA     — Tensile strength in MPa (e.g. 480, 510)
  CARBON_PCT      — Carbon percentage (e.g. 0.18, 0.22)
  GRADE           — A, B, C
  PRODUCTION_DATE — When made
  EXPIRY_DATE     — Date if shelf life applies (not for steel)

When batch is created at GR:
  Batch No. 0000000001
  HEAT_NO = H-25-05-001
  TENSILE_MPA = 485
  CARBON_PCT = 0.19
  GRADE = A
  PRODUCTION_DATE = 2025-05-20

Now when a customer order needs Grade A + Tensile > 480, batch determination automatically picks matching batches via classification search.

T-codes for classification

6. All T-codes for batch management

7. Real-world scenarios per industry

🏥 Pharmaceutical — Lot tracking for recall

Material: Antibiotic XYZ-500mg (FERT)
Batch level: Material (one batch number per material across plants)
Batch numbering: External (matches manufacturer's lot)
Characteristics: ManufactureDate, ExpiryDate, GMP_Test_Pass

Scenario: Patient reports adverse reaction → trace to batch number on packaging
→ MB56 shows: this batch supplied to 3 distributors, 47 pharmacies
→ Targeted recall, not all stock

🍞 Food & Beverage — FEFO shelf life

Material: Milk Powder 1kg (FERT)
Batch level: Plant
Batch numbering: Internal
Characteristics: ProductionDate, ExpiryDate, BestBefore
Shelf life: 365 days (MHDHB), min 30 days remaining (MHDRZ)
Search strategy: FEFO (oldest expiry first)

Scenario: Customer order ships → SAP picks batch expiring soonest
→ Reduces waste, increases freshness on shelf

🔩 Steel manufacturing (PSEC) — Heat number traceability

Material: Steel Rod 12mm (FERT)
Batch level: Plant
Batch numbering: External (heat number = batch)
Characteristics: HeatNo, TensileMPa, Carbon%, Grade

Scenario: Bridge contractor reports steel failure
→ Test failed rod → identify HeatNo via packaging
→ MB56 finds all customers who got this heat
→ Test their stock; targeted replacement
→ Furnace investigation if metallurgical issue

🧪 Chemicals — REACH compliance

Material: Industrial solvent (HAWA imported)
Batch level: Material
Characteristics: SupplierBatchID, OriginCountry, REACH_Cert_Available
Stock status: Quality hold until certificate verified

Scenario: EU customs requires REACH certificate per batch
→ Each batch tagged with source documentation
→ Compliance auditor pulls MSC3N, sees all data

8. When NOT to use batch management (over-engineering traps)

9. Try it in real SAP — step by step

1. Open OMCT in IDES — see the current batch level setting (usually plant level)
2. Open MM02 for an existing material (e.g. T-AS100 in IDES) → Plant Data / Storage 1 view → tick "Batch Management" → save
3. Do a Goods Receipt via MIGO 101 → notice the system now asks for Batch Number
4. Enter batch (or let system auto-generate) → save
5. Run MSC3N for that batch → see the batch master record created
6. Open CL20N → assign characteristic values
7. Do another GR → see new batch created
8. Run MB56 → see batch where-used list
9. Run SE16N → MCHB → see batch stock table directly

10. Interview Q&A

Related advanced topics