# SAP Pricing Error: Condition Record Missing for PR00 in a Sales Order > Source: https://netray.co/erp-help/sap-pricing-condition-record-missing-vk11-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer The error means the pricing procedure expected a price condition such as PR00, found no valid record for the key, and the condition was flagged mandatory. Use the pricing analysis in the order item to see which access failed, then create the record with VK11, or fix the pricing procedure determination if the wrong procedure was selected. ## Kind error ## System sap ## Erp SAP ECC / S/4HANA ## Module SD Pricing ## Query SAP pricing condition record missing PR00 sales order VK11 ## Alternate Queries - SAP no condition record found PR00 - SAP pricing error mandatory condition is missing - how to create condition record VK11 price - SAP pricing analysis in sales order item ## Applies To SAP ECC 6.0 and S/4HANA SD condition technique; condition tables vary by implementation, procedure names such as RVAA01 are standard examples ## Steps ### How to resolve a missing condition record **Items:** In VA01 or VA02 open the item, choose Conditions, and use Analysis (the pricing analysis function). It shows each condition type, its access sequence, and whether each access found a record. Note the key combination that failed, such as Sales Org, Distribution Channel, Customer and Material. Confirm the material and customer master data are what you expect. Check VK13 for the condition type, for example PR00, with the same key. A record may exist but be outside its validity dates or in another sales org or currency. Create the missing record with VK11. Enter condition type, choose the key combination, enter the keys, the amount, currency, unit and validity range, and save. In the order, choose Edit, New Pricing (or pricing type B) to redetermine the price, since the existing pricing result is not recalculated automatically. If the analysis shows the wrong pricing procedure, check determination in OVKK using sales area, document pricing procedure (set on the order type in VOV8) and customer pricing procedure (customer master, sales view). If the condition is mandatory in the procedure (V/08) but you intend it to be optional for this case, change the Mandatory indicator with a transport after approval. Test with a new order for the same customer and material and confirm the price appears. ## Sections ### How the condition technique selects a price **Body:** A pricing procedure (V/08) lists condition types in a fixed order, for example base price PR00, discounts K007 and surcharges. Each condition type points to an access sequence (V/07), which is an ordered list of accesses. Every access reads a condition table keyed by fields such as customer and material or price list and material. The system takes the first access that finds a valid record. Records live in header table KONH and item table KONP, with key fields in the A tables (A304 and others, depending on the key combination chosen). A record is valid only inside its validity range, with the right currency and unit. A record that exists for next month will not be found today, which is one of the most common surprises. ### Reading the pricing analysis **Body:** The analysis screen is the fastest diagnostic. Each condition type shows a list of accesses with a status. A green tick means a record was found, a mark means no record for that access, and a requirement failure means the access was skipped because a routine said it did not apply. The detail view shows the exact key values used, so you can compare them with the VK13 record character for character. Common mismatches are a customer pricing group different from the record, a material pricing group, a currency difference, a price list type, or a record created at a level the access sequence does not read. If the access sequence does not include the key combination you created, no record will be found, however correct the price looks in VK13. **Code:** VK11 Create condition record VK12 Change condition record VK13 Display condition record V/08 Pricing procedure (condition types, mandatory flag) V/07 Access sequence V/06 Condition types OVKK Pricing procedure determination VOV8 Document pricing procedure on sales document type ### Wrong procedure, scales and mass maintenance **Body:** When no record could be correct for the order, the pricing procedure was probably determined wrongly. OVKK combines sales area, document pricing procedure and customer pricing procedure. A new customer with an empty pricing procedure field, or a new sales order type without a document pricing procedure, gets a procedure that does not contain PR00 at all or contains a different set of accesses. For many records use VK31 for list based maintenance or upload through an LSMW or a standard BAPI based load. Check scale types and units: a price entered per 1 unit while the order is in per 100 units yields correct results only if conversions are maintained. Review released prices with the pricing analysis rather than assuming the load worked. ## Pitfalls - Creating a record with a key combination the access sequence does not read, so it is never found. - Setting validity from the first of next month and testing with today's pricing date. - Not redetermining price in the existing order, so the old error remains even after the record exists. - Making a condition mandatory in V/08 without testing special order types such as free of charge or intercompany. - Maintaining the price in the wrong currency or unit of measure. ## Ai Angle A grounded assistant like ERPray can compare the order's key values with the condition records it can read in KONH, KONP and the A tables, then state which access failed and which record would match: for example a record valid next month for the same customer and material. It shows the queries and only reads. Creating or changing prices stays a human action in VK11 with your normal approval. ## Faq ### What does the mandatory condition error mean? **Answer:** The pricing procedure flags a condition type, usually PR00, as mandatory. If no valid record is found for the order's keys and dates, the system raises an error and may set the item pricing status as incomplete. Create the record or correct the pricing procedure determination. ### Why does a record exist in VK13 but is not found? **Answer:** Typical reasons are validity dates, currency, unit of measure, a different sales organisation, or a key combination the access sequence does not use. Use pricing analysis to see the exact key used and compare it with the VK13 record. ### How do I recalculate price after creating the record? **Answer:** Open the order in VA02, go to the item conditions screen and choose Edit, New Pricing, or use pricing type B to redetermine prices fully. Without this step the order keeps the old pricing result even though the condition record now exists. ### Where is the pricing procedure determined? **Answer:** In OVKK, using the sales area, the document pricing procedure on the sales document type and the customer pricing procedure in the customer master sales view. If any of those fields are empty, a different procedure may be selected than the one you expected. ## Search terms SAP condition record missing, PR00 mandatory condition missing, VK11 create condition record, SAP pricing analysis, OVKK pricing procedure determination, SAP access sequence V/07, SAP pricing procedure V/08, KONH KONP condition tables, SAP new pricing sales order, SAP pricing error troubleshooting --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json