SAP Production Version: setup with C223 and MRP4

The production version is the SAP object that says “to manufacture this material, you combine this bill of materials with this routing, over this period”. On an S/4HANA project, it is no longer optional: without it, MRP Live ignores the material. The topic is not complicated in itself, you just have to know the timing traps and know when to go through C223 or through the mass report.

What is a production version in SAP?

An SAP production version is a master object that combines a bill of materials (BOM) and a routing to define how a finished product will be manufactured over a given period. Created in transaction C223 (Manage Production Versions), it is the reference used by MRP to generate production orders.

The BOM x routing link

On a complex material, you sometimes have two or three alternative BOMs, and several routings identified by their group counter. Depending on the period or the plant, several combinations remain valid in parallel. The production version serves exactly that purpose: to lock the combination to use when MRP has to decide how to manufacture.

Why it becomes mandatory in S/4HANA

On ECC, the production version was often optional. Standard MRP could do without it by using the Selection Method field in the MRP4 master to choose the default BOM. That era is over.

Prerequisites before creating a production version

Before opening C223, three objects must exist and be consistent: the bill of materials, the routing, and their validity periods. If just one of the three is missing or not aligned, the consistency check will fail.

The bill of materials (BOM)

Transactions CS01 to create, CS02 to change, CS03 to display. The BOM lists all the components needed to manufacture one unit of finished product, with their quantities and their validity periods. On a complex material, you often have several alternative BOMs, for example an export version and a local version, or a recipe that changes when you switch to a new generation of raw material. When a component of this BOM is itself batch-managed, it is the batch determination that chooses the batch consumed during manufacturing.

The routing

Transactions CA01, CA02, CA03. The routing describes the sequence of operations (work center, duration, predecessors, resources). Like the BOM, it can have several alternatives identified by a group counter.

Aligning the validity periods

Method 1: mass creation via the CS_BOM_PRODVER_MIGRATION report

When you migrate an industrial plant from ECC to S/4HANA, you end up with hundreds of materials to equip with a production version. The standard report CS_BOM_PRODVER_MIGRATION is there for that. It scans the existing BOM/routing pairs and creates the corresponding production versions in a single pass.

1. 1
   Run the report

   Transaction SE38, program CS_BOM_PRODVER_MIGRATION, or via the direct transaction depending on the release.

2. 2
   Define the selection

   Enter the plant or plants concerned, and the range of material numbers to process. You can filter by MRP controller to scope to a perimeter.

3. 3
   Tick “Test mode”

   Always run the first pass as a simulation. The report produces a detailed log without creating any production version.

4. 4
   Check the log

   Materials processed, materials in error, reasons (BOM absent, inconsistent periods, etc.). Correct the faulty masters before the real pass.

5. 5
   Run again in real mode

   Untick Test mode, run again. The production versions are created with a standard name (often 0001, 0002…) and the consistency check runs automatically.

On an S/4HANA project in industry, I migrated a few hundred materials with this report in one afternoon. The difficulty is not the report, it is aligning the BOM and routing periods correctly before running it.

Pierre Balbinot, functional SAP consultant PP/PM

Method 2: manual creation via transaction C223

For a single material or a critical case, manual creation in C223 remains more instructive. All the fields are right in front of you, the consistency check is triggered manually, so when something goes wrong, you identify the cause immediately. It is also where you should start when you are learning the object.

1. 1
   Run transaction C223

   Enter the code C223 in the SAP command field (or via the menu Logistics > Production > Master Data > Production Versions).

2. 2
   Enter Material and Plant

   The finished material concerned and the production plant. Click the “Production Versions” button to list the existing production versions.

3. 3
   Create a new production version

   “New Entries” button or click in an empty line. Enter the production version code (4 characters, by convention 0001, 0002…) and a short description.

4. 4
   Fill in the details

   “Details” button: validity period, BOM alternative (often 1), BOM usage (often 1 = Production), routing group + group counter, lot size min/max.

5. 5
   Run the consistency check

   Dedicated button at the top of the screen. SAP checks the existence of the referenced objects and the alignment of the periods. Result: green light (OK), yellow (warning), red (error).

6. 6
   Save

   “Save” button. A production version with a red check can be saved but stays inactive. To be avoided.

The consistency check

The consistency check is the gatekeeper of the production version. As long as it is red, the production version is inactive: MRP Live ignores it, production orders cannot reference it. Always resolve the warnings and errors before leaving C223.

Setting up the production version in the MRP4 view

Once the production version is created, you still need to check that the finished material master takes it into account properly. This happens in the MRP4 view (transaction MM02, MRP4 tab).

The Selection Method field (deprecated in S/4HANA)

Enabling automatic sourcing for MRP Live

For a material to be fully driven by MRP Live in S/4HANA, three conditions must be met: at least one active production version over the current period; BOM and routing referenced in the production version also active over this period; consistency between the production version lot size and the lot-sizing rules of the MRP1 view.

FAQ: SAP production version

Keep reading

01

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

02

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

03

SAP Tutorials

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....

Pierre B. 12 min read

04

SAP Tutorials

SAP pMRP Explained: Predictive MRP in S/4HANA (and How It Differs from LTP)

SAP pMRP is neither one more MRP run nor a quick facelift of LTP. Predictive Material and Resource Planning is a simulation: nothing you do in it touches your operational...

Pierre B. 10 min read