Scenario 16 — Batch Management (Steel Grade & Heat Number Tracking)

TIER 6 · MASTER DATA ★★★★☆ ⏱️ ~2.5 hours OMCD → MSC1N → MIGO (w/ batch) → MMBE
← Previous
Scenario 15: Outline Agreements
Next →
Scenario 17: Split Valuation
⚠️ Not yet live-tested
This page is built from researched standard-SAP content and has not yet been executed end-to-end in our IDES. The T-codes, fields, and accounts follow SAP standard but may need small adjustments on your S/4HANA 2023 system — we'll confirm and correct them when you run this scenario live. Hit a snag? See the Troubleshooting Center.

📊 Business Case

Batch Management lets you track stock of a single material in distinct, traceable lots — by heat number, grade, purity, manufacture date or expiry. Iron ore quality varies shipment to shipment (different sulfur/phosphorus content), so PakSteel must know exactly which batch went into which finished product. The moment a customer's rebar fails QC, you trace it back to the exact iron-ore batch. The same pattern protects pharma (shelf life), food (production date), and chemicals (purity).

🕐 When to use it

Whenever a material's units are not interchangeable — different shipments carry different quality, expiry, or origin and must be tracked, picked, and recalled by lot.

❓ Why it matters

Traceability, expiry control, and recalls. Track each lot by heat/grade so a failed product traces back to its source batch, expiring stock is picked first, and a recall touches only the affected batches — not your whole inventory.

👤 Who triggers it

Storekeepers assign a batch on every goods movement; QC links test results to a batch; planners use batch determination (FEFO/FIFO) to pick the right lot at goods issue.

🔁 The key distinction

A plain material is one anonymous pile of stock. A batch-managed material is the same code split into identifiable lots — every movement asks "which batch?", and stock is reported per batch (MCHB) on top of the total.

💰 Financial Impact — The Easy-Money Example

PakSteel holds 200 TO of iron ore across two heats. HEAT-2025-001 (high sulfur, suitable only for a 90-day window) and a fresher HEAT-2025-014. Without batches the storekeeper grabs whichever pile is nearest. Here is what batch tracking saves:

🚫 No batch tracking
Write-off ↑ ₨2.5M
The 90-day heat is forgotten at the back of the yard, expires past spec, and 10 TO @ ₨250,000 must be scrapped.
🔢 Batch + FEFO picking
Oldest batch issued first
Batch determination sorts on expiry/manufacture date and auto-picks HEAT-2025-001 before the fresh stock — it is consumed in spec.
📊 Result
₨2.5M write-off avoided
Plus: a customer complaint is traced to its source heat in minutes, so only that lot is recalled — not the entire warehouse.

The big idea: batch management converts an anonymous pile of stock into individually traceable lots. That traceability is what enables FIFO/FEFO picking (no expired write-offs) and surgical recalls (one batch, not the whole inventory).

💡 Lesson: the value of a batch isn't in the accounting entry — a GR still posts inventory the same way. The value is in knowing which units are which: you stop scrapping expired stock and you contain quality failures to a single lot instead of the whole material.

🇵🇰 The Business Story

Iron ore quality varies by batch — different sulfur/phosphorus content per shipment. PakSteel must track each batch (called "Heat Number" in steel industry) for traceability. If a customer rebar fails QC, they trace it back to which iron ore batch was used. Same applies in pharma (shelf life), food (production date), chemicals (purity).

🎯 What you'll learn

📦 Material needed — create first (just-in-time)

RM-IRON-01 (ROH, raw) — create steps. New to MM01? the why behind every field.

📦 MIGO top bar
MIGOAction Goods Receipt · Reference Purchase Order → mvt 101 → enter/assign the batch on the line. Full guide: MIGO Selection Bar.

🔧 Step-by-Step

⚙️ Config

16.1 — Set Batch Level · OMCD
  1. OMCD · Select Batch Level: Material (batch unique per material across all plants — most common)
  2. Activate Batch Status Mgmt (optional)
  3. Save (this is system-wide and can't easily change later — careful!)
16.2 — Activate Batch on Material · MM02
  1. MM02 · RM-IRON-01 · Purchasing view → "Batch Management" ✓
  2. Plant Storage Data view: optionally configure auto batch numbering, batch determination
  3. Save
16.3 — Optional: Batch Class & Characteristics (CT04 / CL02, class type 023)

Create characteristics like SULFUR_PCT, PHOSPHORUS_PCT, HEAT_NUMBER. Group into class type 023 (Batch). Assign class to material's classification view. Now batch master holds these values.

🔄 Transaction Flow

16.4 — Create Batch Master · MSC1N
  1. MSC1N · Material RM-IRON-01 · Batch: HEAT-2025-001 · Plant PK01
  2. Description, Manufacture Date, Vendor, Country of Origin
  3. Characteristics tab: enter Sulfur % = 0.05, Phosphorus % = 0.04, Heat # = HT001
  4. Save
16.5 — GR with batch · MIGO
  1. MIGO · GR · PO #
  2. Line item now has Batch field — mandatory. Enter HEAT-2025-001 (or new batch)
  3. If new batch, SAP prompts to create on the fly
  4. Post

Stock per batch: MMBE now shows quantity per batch + total.

16.6 — Batch Determination at GI — auto-pick FEFO/FIFO

Configure batch determination strategy (CU50 / MMB) — sort key = Expiry Date ASC → SAP auto-picks oldest batch first when issuing.

✅ Verification

🎓 Interview-Ready Answers

Q: What are the three batch levels and which is most common?

Set in OMCD: Plant (a batch number is unique only within one plant — the same number can mean different stock elsewhere), Material (a batch is unique per material across all plants), and Client (a batch number is unique across the whole client). Material level is the most common default. The choice is system-wide and hard to reverse, so it's decided up front.

Q: What is the difference between a batch and a batch characteristic?

The batch is the identifier for a physical lot (e.g. HEAT-2025-001) and SAP tracks stock per batch in table MCHB. Characteristics (sulfur %, manufacture date, expiry) are classification values attached to the batch via class type 023 — they describe the lot's properties and drive batch determination (e.g. sort by expiry for FEFO).

Q: How does FEFO picking actually work?

You configure a batch determination strategy with a sort rule on the expiry/manufacture-date characteristic ascending. At goods issue, SAP evaluates available batches against that strategy and proposes the oldest/first-to-expire batch first (FEFO) — so expiring stock is consumed before fresh stock, preventing write-offs.

Q: Does activating batch management change the accounting of a goods receipt?

No — the FI posting (Inventory Dr / GR-IR Cr at 101) is unchanged. Batch management adds a mandatory batch on every movement and splits the stock record per batch (MCHB) on top of the material total. Value is still at valuation-area level unless you combine it with split valuation.

← Previous
Scenario 15: Outline Agreements
Next →
Scenario 17: Split Valuation