Lesson 2 of 6
Batch levels and the batch master
10 min
Listen to this lesson
Before any material is batch-managed, the system needs one global decision: at which level is a batch number unique? Then each material needs to be switched on for batch management, and each batch gets a batch master record that holds its data. This lesson covers those three things and the trap of switching on batch management for a material that already has stock.
Batch levels
| Batch level | Uniqueness | Data held in | Note |
|---|---|---|---|
| Plant | Unique per material and plant | MCHA | The same number in two plants can mean two different batches |
| Material | Unique per material across all plants | MCH1 (plus plant data in MCHA) | SAP's recommended level for new implementations |
| Client | Unique across the whole client for a material | MCH1 | A batch number never repeats for any material |
Batch levels, set system-wide in Customizing (transaction OMCT, together with batch status management).
The level is a system-wide setting, so it is decided once and changed rarely. Converting from plant level to a higher level is possible with SAP's conversion program (RM07CHDX), which first checks for batch numbers that would become ambiguous; converting back down from material or client level to plant level is not supported in the standard. Contoso's system runs at material level, which suits a company that moves rotors between Detroit and Chicago: batch 0000001042 of CMC-RTR-200 means the same Lakeside lot in both plants. Check your own setting in OMCT before designing anything.
Switching a material on
A material becomes batch-managed with the batch management indicator in the product master. Depending on the batch level, there is a global indicator and a plant-specific one that decides whether the material is batch-managed in each plant. The indicator cannot simply be set while stock or open documents exist for the material, because existing quantities have no batch. Plan the switch like a small cutover.
- 1. FreezeAgree a date with procurement and production; no open purchase orders, production orders or deliveries for CMC-RTR-200 that cannot be closed
- 2. EmptyPost remaining rotor stock out to a temporary material or count and issue it, as agreed with finance
- 3. Switch onSet the batch management indicator for CMC-RTR-200 in plants 1710 and 1720
- 4. RefillPost the stock back in with batches, one batch per known supplier lot, or one "legacy" batch if lots are unknown
- 5. VerifyStock overview by batch; open documents recreated; MRP and backflush settings rechecked
The batch master record
| Batch data | Example for CMC-RTR-200 batch 0000001042 | Why it matters |
|---|---|---|
| Batch number | 0000001042, assigned internally at goods receipt | The key that travels with every movement |
| Supplier batch | LKS-26-311, Lakeside's lot number | Links Contoso's batch to the supplier's trace |
| Date of manufacture and SLED | Manufactured 2027-03-02; no expiry for rotors | Shelf-life control where relevant |
| Batch status | Unrestricted or restricted | Restricted batches are blocked from normal use (with batch status management active) |
| Classification | Characteristics such as bearing type and test result | Batch determination and quality decisions |
What a batch master record holds (values illustrative).
Batch master records can be created manually, for example in the Manage Batches app (or MSC1N in SAP GUI), but most are created automatically: at the first goods receipt, when a production order is created, at a quality usage decision, or with a transfer posting that splits a batch. Number assignment is usually internal, from a number range; external entry is possible only if the settings allow it. Contoso uses internal numbers and stores the supplier's lot in the supplier batch field, so Contoso's batch numbers stay unique and Lakeside's lot is still searchable.
With batch status management active, each batch is either unrestricted or restricted. A restricted batch stays in stock but is excluded from normal use, for example from batch determination for production. Quality uses this to hold a lot while a test result is open, and the quality usage decision can set the status. For Contoso's rotors, a batch whose Lakeside certificate is missing is received as restricted and released by quality when the certificate arrives. Test both directions: a restricted batch must not be issued, and releasing it must make it available without any other change.
What goes wrong in testing
| Pitfall | Consequence | Prevention |
|---|---|---|
| Indicator switched in CMQ with stock present | Errors, or stock without batch history | Rehearse the empty-switch-refill steps with finance |
| Supplier batch not captured | Contoso batch exists but cannot be linked to Lakeside's lot | Make supplier batch mandatory in the receiving test script |
| Batch level assumed, not checked | Plant-level numbers treated as unique across plants | Read OMCT in each test system first |
| Restricted status not tested | Blocked batches still consumed | Test a goods issue from a restricted batch |
Typical batch master test failures.
What would you do?
In CMQ, Kenji's team sets the batch management indicator for CMC-RTR-200 while 1,200 rotors are in stock, and the change is refused. Omar suggests "just using a different material number for batched rotors." What is the better approach?
- Batch level (plant, material, client) is system-wide; SAP recommends material level.
- Switching a material on requires a plan when stock or open documents exist.
- The batch master holds number, supplier batch, dates, status and classification.
- Batches are mostly created automatically at goods receipt or order creation.
Check your understanding · not graded
Lesson check
1. At which batch level does the same number mean the same batch in every plant for a material?
2. Which conversion of the batch level is NOT supported in the standard?
3. Why does switching on batch management need planning when stock exists?
4. Where does Contoso keep Lakeside's own lot number?