How To Fix PRCG_CNDNRECORD_API064 - Condition record &1 not found for the condition supplement

SAP Error Message - Details

• Message type: E = Error

• Message class: PRCG_CNDNRECORD_API - Messages for the Condition Read API

• Message number: 064

• Message text: Condition record &1 not found for the condition supplement

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message PRCG_CNDNRECORD_API064 - Condition record &1 not found for the condition supplement ?

  The SAP error message PRCG_CNDNRECORD_API064 indicates that a condition record for a specific condition supplement could not be found. This error typically occurs in the context of pricing or conditions in SAP, particularly when working with condition records in the pricing procedure.
  Cause:
  
  Missing Condition Record: The most common cause is that the condition record for the specified condition supplement does not exist in the system.
  Incorrect Key: The key used to access the condition record may be incorrect or not properly defined.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables.
  Authorization Issues: The user may not have the necessary authorizations to view or access the condition records.
  Incorrect Configuration: The pricing procedure or condition types may not be configured correctly.
  
  Solution:
  
  
  Check Condition Records: 
  
  Use transaction code VK13 (Display Condition) to check if the condition record exists for the specified condition type and key.
  If it does not exist, you may need to create it using transaction code VK11 (Create Condition).
  
  
  
  Verify Key Values: 
  
  Ensure that the key values (like customer, material, etc.) used to access the condition record are correct and match the expected values.
  
  
  
  Review Configuration: 
  
  Check the configuration of the pricing procedure and condition types in transaction code SPRO. Ensure that the condition supplements are correctly defined and linked to the appropriate pricing procedure.
  
  
  
  Check Authorizations: 
  
  Ensure that the user has the necessary authorizations to access the condition records. This can be checked with the help of your SAP security team.
  
  
  
  Data Consistency Check: 
  
  Run consistency checks on the relevant tables to ensure there are no missing or inconsistent entries.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to the specific condition type and pricing procedure for any additional insights or known issues.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  VK11 - Create Condition Record
  VK12 - Change Condition Record
  VK13 - Display Condition Record
  SPRO - Customizing Implementation Guide
  
  
  Tables Involved: 
  
  KONV - Conditions (Transaction Data)
  KOND - Conditions (Master Data)
  
  
  SAP Notes: 
  
  Check SAP Notes for any known issues or patches related to this error message.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.