SAP C223: How to Create a Production Version in SAP PP

โšก Smart Summary

Production versions in SAP PP pair one alternative bill of material with one routing, so planning and order creation know exactly which components and which operations to use for a given lot size and validity period.

  • ๐Ÿ”˜ Definition: A production version is the named link between an alternative BOM and a routing for one material and plant.
  • โ˜‘๏ธ Transaction: C223 maintains production versions, and the same data appears on the MRP 4 view of the material master.
  • โœ… Prerequisites: The material master, the BOM and the routing must all exist before the version can be created.
  • ๐Ÿงช Selection rules: Validity dates and the lot-size range decide which version planning picks for a given order.
  • ๐Ÿ› ๏ธ Consistency check: A green status confirms the BOM and routing really are valid for that period and quantity.
  • ๐Ÿ“ˆ S/4HANA change: Production versions were optional in ECC and are mandatory master data in SAP S/4HANA.

Create Production Version in SAP PP Using Transaction C223

What is a Production Version in SAP PP?

The production version is the link between a product BOM (bill of material) and the process routing. It determines which alternative BOM is used together with which routing to produce a material or plan a material.

There may be different production versions based on the lot sizes and validity dates. For example, there may be different versions if you want to produce 1 to 100 liters of paint rather than 100 to 1,000 liters, because a different composition of the BOM may be required in each case.

A production version comprises the following data:

  1. The assignment of routings to the production version.
  2. The assignment of the alternative BOM to the production version.

Production versions are used in material requirements planning (MRP), production order creation and product costing, to select the most suitable routing and the corresponding bill of material.

Why is a Production Version Required?

A material with only one BOM and one routing still runs without a version in older releases. The moment a plant has a choice, however, something has to record which combination is legitimate, and that is the job of the production version.

  • Several ways to make the same material. Two production lines, or a manual and an automatic line, each need their own BOM and routing pairing.
  • Quantity-dependent recipes. A small batch and a bulk batch often use different components, so each gets its own version with its own lot-size range.
  • Time-dependent changes. A reformulated product can be introduced on a fixed date by giving the new version a later validity start.
  • Unambiguous planning. Without a version, MRP has to guess which alternative BOM and which routing group to explode.
  • Mandatory in SAP S/4HANA. What was optional in SAP ERP is required master data in S/4HANA for discrete, process and repetitive manufacturing, so existing materials must be given versions during migration.

Key Fields in the Production Version

The C223 detail screen is short but every field changes how the version is selected. The table below explains what each entry controls before you fill the screen in.

Field What it controls
Plant and Material The material and location the version belongs to. A version is always plant specific
Production version and text The identifier, usually 0001, 0002 and so on, plus a description a planner can recognize
Valid from / Valid to The period during which planning may select this version
Lot size from / to The order quantity range the version covers. An order outside the range will not use it
Alternative BOM and BOM usage Which BOM alternative to explode. Usage 1 is the production BOM
Task list type N for a routing, 2 for a master recipe in process manufacturing
Task list group and group counter The routing group generated by CA01, and the counter that picks one alternative inside it

Steps to Create Production Version in SAP

Before starting, confirm that the material master exists in the plant, that the BOM has been created in CS01 and that the routing has been created in CA01. In order to create a production version, perform the following steps.

Step 1) From the SAP Easy Access screen, open transaction C223.

  1. Enter the Plant code.
  2. Enter the parent material for which the production version needs to be created.
  3. Enter the Material code.
  4. Input the production version code and text.
  5. Input the validity dates of the production version.
  6. Input the lot size range where it would be valid.
  7. Input the Alternative BOM and BOM usage as “1” for a production BOM.
  8. Enter the Routing Group and Group Counter.
  9. Enter the type of task list, which is N for a routing.

The detail screen collects all of these entries in a single pop-up window.

C223 production version detail screen with BOM and routing assignment

After filling in all the fields, click Green check mark button used to confirm the entry or press Enter to go to the next screen.

Step 2) In this screen:

  1. Select the line of the newly created production version.
  2. Press “consistency check” to check whether the BOM and routing are valid.

A new version starts with the status “not yet checked”, shown as a yellow triangle, until the check is run.

Production version mass processing list with the consistency check button

Step 3) In this screen, you can see the messages regarding the validity of the BOM and routing for the material.

  1. Check whether the task list routing exists in the validity period (01.01.2015 to 31.12.9999) and lot sizes (0 to 99999999) of the production version.
  2. Check whether the BOM exists in the validity period (01.01.2015 to 31.12.9999) and lot sizes (0 to 9999999999999) of the production version.

Each line reports one check, so a red entry names exactly which object failed.

Consistency check messages for BOM and routing validity

Click Back button in the SAP toolbar or press F3 on the keyboard to return to the previous screen.

Step 4) In this screen, you can see that the test status is indicated by a green color.

  1. You can see the consistency check status in green.

Production version list showing a green consistency check status

Click Save button in the SAP toolbar to save the new version. The system will show the message “Production version saved” in the lower left corner.

Production Version in the Material Master

C223 is not the only route to the same data. The identical production versions can be reached from the material master, which is often faster when you are already working on one material.

  1. Run transaction MM02 for the material and plant.
  2. Open the MRP 4 view, or the Work Scheduling view.
  3. Click the ProdVersions button to open the same detail screen used above.

The choice is one of scale rather than function. C223 is built for mass processing, so it lists every version for a material or plant at once and allows a collective consistency check, while MM02 handles a single material at a time. In SAP S/4HANA, the Manage Production Version app covers the same task, and the Process Production Version app proposes new versions automatically when a matching BOM and routing appear.

Troubleshooting Production Version Errors

  • There might be a case where the BOM and routing are not valid within the production version validity time frame. Ensure that the validity period of the production version falls within the validity period of both the BOM and the routing.
  • If the lot-size range of the version is wider than the range on the routing header, the consistency check reports an error. Narrow the version or widen the routing lot size.
  • An order quantity outside the version lot-size range simply will not select the version, which usually looks like a missing version rather than an error message.
  • If the routing group or group counter is wrong, the check still passes on the BOM line but fails on the task list line, so read both messages rather than only the first.
  • The consistency check is informational and does not block order creation, so a version can be used while still yellow. Running it anyway is what surfaces lot-size and validity mismatches early.

FAQs

Rule-based and machine learning services detect missing or duplicate master data, propose values from similar materials, and flag versions whose validity has lapsed. SAP already proposes production versions automatically once a matching BOM and routing exist.

Copilot can draft the ABAP, LSMW or BAPI wrapper used for a mass load and generate the spreadsheet template behind it. The field values still come from the plant, and every generated load should run in a test client first.

There is no practical limit. Each version needs a unique identifier for the material and plant, and overlapping validity periods are allowed as long as the lot-size ranges keep the selection unambiguous.

Planning filters by plant, validity date and order quantity, then takes the first version that fits and is not locked. Quota arrangements can override that order when production has to be split across lines.

Yes, and locking is the safer option. A locked version stays visible for historical orders and costing runs but is no longer selected by planning, whereas deletion removes a record that older documents may still reference.

The screen is the same, but the task list type becomes 2 for a master recipe instead of N for a routing. Process industries therefore use production versions to pair a recipe with the correct alternative BOM.

Yes. Costing with a quantity structure explodes the BOM and routing named by the selected version, so two versions with different components or times produce two different standard costs for the same material.

MKAL holds the production version header for each material and plant, and MKAL_MDV stores the related repetitive manufacturing details. Reporting and mass-load programs read these tables rather than the C223 screen.

Summarize this post with: