# SAP CO01 Error: No Production Version Found for Material > Source: https://netray.co/erp-help/sap-co01-production-version-missing-error-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SAP cannot pick a production version for the order quantity and date, so it cannot determine the BOM and routing. Fix it in C223 or on the MRP 4 view of the material: create a version for the plant, make its validity dates and lot size range cover the order, link a valid BOM alternative and routing, and remove the lock indicator. ## Kind error ## System sap ## Erp SAP ECC and S/4HANA ## Module PP / Production Versions ## Query SAP CO01 no production version found for material ## Alternate Queries - SAP no valid production version exists - production version lot size range error SAP - C223 production version how to create - SAP planned order conversion production version missing ## Applies To SAP ECC 6.0 and SAP S/4HANA, discrete and process manufacturing, CO01, CO40, CO41, planned order conversion (MD04) and MRP Live. ## Steps ### How to fix a missing or invalid production version **Items:** - Open C223 (Maintain Production Version) and enter the material and plant. Alternatively open MM02, go to the MRP 4 view and use the production versions button. - If no entry exists, create one with a version number, a text, and the validity dates that cover the order start date. - Set the Lot Size From and To so the order quantity falls within the range. Orders outside every range raise the error even if a version exists. - Fill in the BOM data (BOM usage, alternative BOM) and the routing data (task list type N, group and group counter), then confirm they exist in CS03 and CA03. - Use the Check function in C223 to test the version. Fix the messages for a missing BOM, routing, or an operation without a work center. - Make sure the Locked indicator is not set for the version and that the planning plant fields are correct for the production plant. - Check the Selection Method on MRP 4 of the material master, which controls how versions are chosen (by lot size, by date, or by the rules your plant configured). - Retry the order in CO01 or reconvert the planned order. If MRP created the error, rerun MD01N for the material afterwards. ## Sections ### How SAP picks a production version **Body:** A production version is the link between a material, a plant and the master data used to make it: the BOM alternative, the routing (task list), and optionally the issuing storage location and the line. When you create a planned order, a production order, or run a cost estimate, SAP looks at the versions of the material in the plant and picks the one that is valid on the required date and whose lot size range contains the order quantity. If more than one version fits, the selection method on the MRP 4 view decides which one is taken. If none fits, SAP raises the error that no valid production version could be found. Often there are versions, but all of them fail on dates, lot size, or lock. That is why simply having an entry in C223 does not mean the error will go away. ### The five usual root causes **Body:** First, the validity period has expired or has not started yet; versions often end on the last day of the previous year and nobody extended them. Second, the lot size range does not include the order quantity, typically after a rounding rule or a large customer order increases the quantity. Third, the Locked indicator is set, often automatically after a BOM or routing change made the version inconsistent. Fourth, the BOM or routing referenced by the version is gone, has a validity date that starts later, or has a status that excludes it from production use. Fifth, the version is held under a different planning plant or the MRP controller is working in a plant where the material has no version at all. Check each in turn before reconfiguring anything. **Code:** -- Review in SE16N Table MKAL (production versions: MATNR, WERKS, VERID, ADATU, BDATU, BSTMI, BSTMA, STLAL, PLNNR, ALNAL, MKSP) Table MARC (material plant data, SFEPR, SERNP) Table MAST (material to BOM link) Table MAPL (material to task list link) ### Mass maintenance and keeping versions healthy **Body:** Large installations can have thousands of materials and cannot fix versions one at a time. C202 is the mass transaction for creating production versions from existing BOM and routing data, and C223 handles single maintenance. For roll-forward of validity dates, use a controlled mass update with a test run and a spot check on MKAL before and after. Never edit MKAL directly in the database. A good habit is a regular exception report: materials with MRP type not ND and procurement type E (in-house) in MARC that have no valid row in MKAL for the next planning horizon. Run it before the planning run, not after. A missing version often shows as a material that MD01N failed to plan, so reading the failed list in the planning log is part of the same discipline. ### Variants: process orders, repetitive manufacturing and costing **Body:** In process industries, the production version points to a master recipe instead of a routing, and the check validates phases and resources. In repetitive manufacturing, the version also drives the line assignment. Costing uses the same logic: a missing version in CK11N or a standard cost run gives the same kind of error, so fixing the version fixes both. If you are on S/4HANA and the material appears to have a version but the error continues, check the transaction used for the material master. Some fields such as the selection method are only maintained in MM02 on MRP 4. Also check whether an alternative production planning plant or a supply area is in play, since those can send the order to another set of versions. ## Pitfalls - Creating a version with validity dates that do not cover the order start date, so the error continues. - Setting lot size ranges that do not overlap, leaving gaps where no quantity is valid. - Leaving a version locked after a BOM or routing change, so SAP silently skips it. - Fixing the version in one plant and forgetting the planning plant or a second plant that uses the same BOM. - Editing production version data directly in the database table instead of using C223 or C202. ## Ai Angle An assistant grounded in your SAP data (ERPray, read-only by default) can answer which materials have no valid production version for next month, by comparing MARC and MKAL and showing the query. It lists the gaps by plant and reason: expired dates, lot size holes, locked flags, or missing BOM or routing. It does not create versions; planners still maintain them in C223 or C202 with the usual authorisations. ## Faq ### Where do I maintain production versions? **Answer:** Use transaction C223 for single materials, or open the material in MM02 and go to the MRP 4 view where a button leads to production versions. For mass creation from existing BOM and routing data, use C202. The data is stored in table MKAL. ### Why is the error shown even though a production version exists? **Answer:** A version only counts if it is valid on the required date, its lot size range contains the order quantity, it is not locked, and its BOM and routing exist. Check dates, lot size from and to, the lock indicator, and use the Check function in C223 to see the exact inconsistency. ### Can MRP create orders without a production version? **Answer:** It depends on plant configuration. Many plants require a version to explode the BOM and select the routing. Where it is not required, SAP falls back on the BOM and routing selected by usage and alternative. Check with your PP configuration owner before relying on the fallback, because costing may still need the version. ### How do I find all materials missing a production version? **Answer:** Compare in-house produced materials in MARC (procurement type E, MRP type not ND) with valid rows in MKAL for the same plant and date range. Use SE16N for a quick look or a custom query for a recurring report, and run it before the MRP run. ## Search terms SAP production version, C223 production version, no production version found, MKAL production version, CO01 production version error, C202 mass production version, SAP planned order conversion error, MRP 4 view production version, SAP lot size range production version, SAP production version check --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json