C223 — Maintain Production Versions
C223 is used to create and maintain production versions linking material, BOM and routing/recipe for a plant and validity range. It is most useful when MRP and order creation must choose an approved combination of quantity structure and production method. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers C223 — Maintain Production Versions. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 633 words
Esta página aún no está disponible en español.
Purpose
create and maintain production versions linking material, BOM and routing/recipe for a plant and validity range. C223 is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
C223 is typically used when MRP and order creation must choose an approved combination of quantity structure and production method. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Open the material/plant and review existing versions.
- Define validity and lot-size range without overlap ambiguity.
- Assign the correct BOM and routing/recipe.
- Run consistency checks.
- Test MRP/order creation to confirm the expected version is selected.
Key data objects
These are the most useful anchors when working in C223. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- material/plant — verify the exact value, validity/date context and relationship to the affected process.
- production version — verify the exact value, validity/date context and relationship to the affected process.
- validity — verify the exact value, validity/date context and relationship to the affected process.
- lot-size range — verify the exact value, validity/date context and relationship to the affected process.
- BOM and routing/recipe assignment — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
Production versions are especially important in S/4HANA because they are the strategic source-selection object for many production processes. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Overlapping versions with unclear selection. Return to the exact object status and chronology before applying a workaround.
- Assigning a BOM/routing that is not valid on the same date. Return to the exact object status and chronology before applying a workaround.
- Creating a version to fix order creation without correcting the underlying master data. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the PP M2D team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/c223ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.