# Production version in SAP S/4HANA: how to create it and why it is required > Source: https://netray.co/erp-help/production-version-in-sap-s4hana-create-c223-mass-maintenance > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A production version links a material, a plant and a validity period to one BOM and one routing or recipe. In S/4HANA you create it in C223 (or the Manage Production Versions app) and the system then uses it to pick the BOM and task list for planned and production orders. Without a valid one, order creation and MRP conversion fail. ## Kind how-to ## System sap ## Erp SAP S/4HANA ## Module Production Planning / Production Versions ## Query production version in sap s4hana ## Alternate Queries - how to create production version in sap s4hana - c223 production version - mass maintenance of production versions sap ## Applies To SAP S/4HANA (on-premise and private cloud editions); concept also applies to ECC. Menu text varies slightly by release. ## Steps ### Create a production version in C223 **Items:** - Run transaction C223 (Logistics > Production > Master Data > Production Versions > Edit). Enter the material and plant and press Enter. - Create a new line: give the version a four character key such as 0001 and a short text. - Set Valid From and Valid To dates and, if you use lot size ranges, the Lot Size From and To so the version applies only to those quantities. - Enter the routing: task list type (N for routing, R for rate routing, S for reference rate routing, or a recipe type), group and group counter. - Enter the BOM: alternative BOM and BOM usage, or let the system derive them from the material and plant. - Press Check. The system validates that the BOM and the routing exist, are valid in the date range and that components and operations are consistent. - Save. Open the material master (MM03), MRP 4 view, and confirm the Selection Method and, if needed, that the version shows under the work scheduling view. ## Sections ### Why S/4HANA insists on production versions **Body:** In older ECC systems a production order could find its BOM and routing from the material master through automatic selection, using the BOM usage and plant. That path still exists in some configurations, but SAP's direction in S/4HANA is that the production version is the master data object that ties a manufacturing definition to a material. Planned orders, production orders, process orders, MRP conversion and costing all read it. If no version is found for the order quantity and date, you get the familiar message that no production version exists or that none is valid. The production version is stored in table MKAL, keyed by material, plant and version. It carries the BOM and routing keys, validity dates and lot size range, and the version is locked or unlocked through a status flag. Because it carries dates and quantity bands, you can run two versions for the same product, for example a legacy line and a new line, and let the lot size or date decide which one MRP uses. **Code:** - -- Quick check of versions for a material (SE16N on MKAL or ABAP SQL) - SELECT matnr, werks, verid, bdatu, adatu, plnty, plnnr, plnal, stlal, stlan - FROM mkal WHERE matnr = '000000000012345678' AND werks = '1010'. ### Mass maintenance of production versions **Body:** When you onboard hundreds of materials, one by one entry in C223 is too slow. SAP provides a mass processing function for production versions (transaction C202 in many releases, also reachable from the Production Versions menu) where you select materials by plant or MRP controller and either create versions from a template or change fields in bulk, such as extending the valid-to date or switching the routing group. Run it first in test mode if the option exists, and check the log. The other route is a migration object through the Migration Cockpit, or a controlled upload using a standard BAPI or a recorded batch input. Whatever you choose, load BOMs and routings first, because the version check fails if the referenced objects are missing or not valid on the validity dates. After a mass change, rerun the check function on a sample and read MKAL to confirm. ### How production versions interact with MRP and costing **Body:** MRP converts planned orders using the version selected for the lot size and date. Materials that are externally procured do not need one. Materials flagged as made in house, including those with special procurement keys that produce in house, do. If MRP creates planned orders with no BOM explosion, the usual cause is a missing, locked or expired version. For costing, the cost estimate with quantity structure (CK11N) takes its BOM and routing from the version determined for the costing lot size, so a wrong or missing version produces a wrong standard cost. Keep the versions reviewed in the same cycle as your standard cost run. ## Pitfalls - Validity dates that expire silently: a version with a Valid To in the past causes order creation to fail the day after, with no change to the material. - Lot size ranges that leave gaps: a version valid for 1 to 100 and another from 200 up leaves quantities 101 to 199 with no version. - Locked versions: a version locked in the status field is ignored by planning and by order creation. - Mass changing without checking: a bulk update can point many materials at a routing group whose validity does not cover the dates. - Assuming automatic BOM selection still works: configuration may allow it, but design for production versions to avoid surprises on upgrade. ## Ai Angle An assistant grounded in your SAP data, such as ERPray reading MKAL, MAST and PLPO read-only, can list every in-house material that has no valid production version for the next planning horizon, or whose version expires within 60 days, and show the query it ran. Because it runs read-only, a planner reviews the list and a person still makes the change in C223. On-prem deployment keeps that material data inside your network. ## Faq ### What is the transaction code to create a production version in SAP? **Answer:** Use C223 for single maintenance. In S/4HANA you can also use the Fiori app Manage Production Versions. Mass processing is available from the production version mass processing function (C202 in many releases). Authorization objects for the plant and for production planning master data apply. ### Is a production version mandatory in S/4HANA? **Answer:** In practice yes for in-house produced materials, because planned order conversion, production order creation and costing look for one. SAP's direction is to make it the standard way to select BOM and routing. Treat it as required and test your own configuration. ### Which table stores production versions? **Answer:** Table MKAL holds production versions, keyed by material, plant and version. It stores the validity dates, lot size range, BOM and routing references and the lock status. Use SE16N for display only and never change it directly. ### Why does the check in C223 fail? **Answer:** Typical causes are a BOM or routing that does not exist or is not valid on the version's dates, an unreleased routing status, a plant mismatch between BOM and routing, or a lot size range outside the routing's lot size limits. The check message names the object to fix. ## Search terms production version in sap s4hana, c223 production version, create production version sap, mkal table, mass maintenance production version, c202 production versions, sap production version bom routing, manage production versions fiori --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json