SAP batch determination and management

You are configuring SAP batch determination and the engine does not kick in. You are picking batches in the wrong order even though the sort rule is correctly set up. Welcome to the club of consultants who spent two days on a point that gets solved in five minutes once you know the right transactions. Here are the 6 clean steps and the 4 pitfalls that cost full days on a project.

What is batch determination in plain terms?

SAP batch determination is the function that automatically selects the batches to consume or deliver based on criteria you define: expiration date, quality status, plant, technical batch characteristic (set up through the SAP classification system). It replaces the manual entry of a batch number with a rules engine. It is this engine that makes industrial FIFO possible at scale.

Definition of an SAP batch

A batch in SAP is a physical instance of a material, identified by a unique number and carrying its own characteristics: production date, vendor, serial number, quality inspection result. The batch lives in table MCH1 and its stock in MCHB. You create it via MSC1N or it is born automatically at goods receipt (MIGO movement 101).

When the engine kicks in

Batch determination is triggered in four contexts: when creating or releasing a production or process order, during an outbound delivery (SD), during a WM or EWM picking, and during a stock transfer between plants. In all these cases, the system does not select the batch on its own. It applies the search procedure you configured, and that procedure drives the chaining of the rules. The SAP Help Portal documentation details the usage contexts module by module.

The modules involved (PP, MM, SD, WM)

Batch determination is used by several SAP modules, each with its typical use case and its triggering transaction.

We stay on the PP configuration (production order) in what follows. That is where most consultants run into the topic for the first time. The principles (condition table, access sequence, search procedure) are identical for SD, MM and WM. Only the assignment transactions change.

Configuring batch determination in 6 steps

The Customizing fits into 6 objects to chain in order. The SPRO path:

Logistics → Central Functions → Batch Management → Batch Determination → Batch Search Procedure

Here are the 6 steps, in order.

1. 1

   Create the condition table

   The condition table defines the search key: which fields will SAP use to look for a strategy record? In PP, the classic combination is plant plus material plus order type. You create the table in the batch determination Customizing, under application PP (or MM, SD, WM depending on your case).

   

2. 2

   Define the access sequence

   The access sequence orders the condition tables by priority. SAP tests the tables from the most specific to the most general until it finds a record. If you have two tables (plant plus material, and plant only), you place the most specific one in first position.

   

3. 3

   Set up the sort rule

   The sort rule drives the sorting order of the eligible batches: FIFO on production date (characteristic HSDAT), sort on expiration date (characteristic VFDAT), LIFO or a custom criterion. You create it in CU70 by selecting the sort characteristics and their ascending or descending order. A step often forgotten at the assignment to the strategy type, see pitfall 3 further down.

   

4. 4

   Build the strategy type

   The strategy type links the access sequence to a batch selection logic and to a sort rule. It is the pivot object of the Customizing: it declares how SAP must search (access sequence), filter (characteristic class) and sort (sort rule) the batches.

   

5. 5

   Assemble the search procedure

   The search procedure groups one or more strategy types in an execution order. SAP runs the strategy types one by one until it finds enough batches to cover the requested quantity. It is the final container of the Customizing.

   

6. 6

   Assign via OPL8

   Last step, and the one that most often fails: you assign the search procedure to the order type via OPL8 (Order Type Dependent Parameters). Without this step, the engine never kicks in: all your Customizing is correct but inactive. Check it for each order type involved. For the Manufacturing detail, see SAP KBA 3649584.

   

Once the 6 steps are done, you maintain the condition records in COB1. This is the step that turns the Customizing (technical) into operational data (business).

Maintain the records in COB1, the step everyone forgets

On the PP projects I have seen, forgetting to maintain COB1 after go-live is recurring. The batch determination engine is silent about its own missing records: it raises no error, it just returns an empty batch list. The consultant who debugs spends the whole day searching in the configuration, while the problem is in the data.

Pierre Balbinot, SAP PP/PM consultant

COB1 creates and maintains the condition records of the batch determination engine. Without a record in COB1, your Customizing is valid but the engine finds no applicable strategy and returns an empty batch list. This is the number one silent pitfall.

COB1 vs MBC1: do not mix them up

COB1 is the transaction for creating and maintaining the condition records (Customizing and master data side). MBC1 is the transaction for running the batch search on the user side, which consumes the records configured in COB1. In plain terms: COB1 writes the rules, MBC1 applies them. On S/4HANA, MBC1 is largely replaced by the Fiori apps Manage Batches and Maintain Batch Search Strategies, but COB1 remains the reference transaction for the configuration.

ECC vs S/4HANA: what really changes

The batch determination logic is strictly identical between ECC and S/4HANA. What moves is the surrounding master data and the UI.

So you can reassure the project managers during a migration: batch determination is not part of the work packages to rebuild. You transport your Customizing as is, you check the batch level (which may move on the MM side) and you run a regression test. For the post-migration classes and batch levels, SAP KBA 3078948 provides the up-to-date matrix.

4 pitfalls we run into in production

Pitfall 1: Batch Management activated after stock movements

You activate the Batch Management flag in MM02 on a material that already has stock in MCHB. By default, SAP will not let you do it (error message). But if you force it one way or another … The result: MIGO blocks every movement with an error message on batch level consistency. The fix: activate Batch Management before any movement, or archive the existing stock before switching the flag. The creation of the Production Version, which often serves as a prerequisite, follows the same timing logic.

Pitfall 2: OPL8 forgotten on a custom order type

You copy a standard order type PP01 into ZP01 for a specific business need. You carry over the whole dependent Customizing, except the assignment of the search procedure in OPL8. The batch determination engine never kicks in on ZP01 and raises no error. You search through the Customizing for hours while the cause is a missing line in OPL8.

Pitfall 3: Sort rule defined but not assigned to the strategy type

You create a clean FIFO sort rule in CU70, you save, you test. SAP picks the batches in a seemingly random order. Cause: the sort rule exists but is not linked to the strategy type involved. The engine therefore selects the batches without sorting. The fix: open the strategy type, sort sequence tab, explicitly link the sort rule.

Pitfall 4: Class type 022 vs 023 chosen wrong

You work with a material batch level (S/4 default) but you classified the material via class type 022 (plant level). The characteristics do not propagate, the engine ignores your filters and returns all the available batches. The fix: align the class type with the actual batch level (023 for material/client, 022 for plant).

FAQ: SAP Batch Determination

Batch determination is a silent engine. It raises no error when a record is missing. It does not tell you that your sort rule is not linked. When a consultant tells me “my batch determination does not work”, I always start with COB1 and OPL8. The technical Customizing comes after.

If you want to go further on the PP module end-to-end, we are preparing a complete SAP PP training that will be released on our short training catalog in the coming months. For the prerequisites linked to the creation of the Production Version, see our SAP Production Version tutorial. And on the logistics side, the same cascade logic applies for the storage bin type search in SAP WM, where SAP filters the candidate bins across 3 levels before retaining the final storage bin.

Keep reading

01

SAP Tutorials

Beginner's guide to batch management in SAP MM

I have seen consultants tick the "Batch management" box on thousands of materials in a MASS run, without realizing the batch level was still set at client level. A few...

Pierre B. 12 min read

02

SAP Tutorials

SAP Serial Number: OIS2 setup and material vs equipment

A SAP serial number is the unique identifier attached to one specific physical unit of a given material. It is the tool for unit-level traceability, the foundation for individualized after-sales...

Pierre B. 15 min read

03

SAP Tutorials

SAP PRT: Production Resources and Tools

On an industrial site, the tools shared between production lines are often invisible in SAP. Jigs, probes and technical drawings move from one order to the next, but nobody knows...

Pierre B. 13 min read

04

SAP Tutorials

SAP Classification System: characteristics and classes

You are looking for every high-criticality 24V piece of equipment in SAP. Every batch with a viscosity between 200 and 250. Every premium customer in a specific geographic area. If...

Pierre B. 10 min read