How To Fix CND_EXCHANGE072 - Record KNUMH = &1, VARNUMH = &2: det. data missing (structure BAPICONDIT)

SAP Error Message - Details

• Message type: E = Error

• Message class: CND_EXCHANGE - Error Messages in Data Exchange Conditions

• Message number: 072

• Message text: Record KNUMH = &1, VARNUMH = &2: det. data missing (structure BAPICONDIT)

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 CND_EXCHANGE072 - Record KNUMH = &1, VARNUMH = &2: det. data missing (structure BAPICONDIT) ?

  The SAP error message CND_EXCHANGE072 indicates that there is missing data in the condition record for a specific pricing condition. The message specifies that the record identified by KNUMH (the condition record number) and VARNUMH (the condition record variant number) is incomplete, particularly in the context of the structure BAPICONDIT.
  
  Cause:
  
  
  Missing Data: The error typically arises when the system expects certain data to be present in the condition record but finds it missing. This could be due to:
  
  Incomplete or incorrect configuration of pricing conditions.
  Missing entries in the condition tables.
  Issues during the creation or modification of condition records.
  
  
  
  Incorrect Condition Type: The condition type may not be properly set up or may not have the necessary data associated with it.
  
  
  Data Inconsistency: There may be inconsistencies in the data that prevent the system from retrieving the necessary information.
  
  
  
  Solution:
  
  
  Check Condition Records: 
  
  Use transaction code VK13 (Display Condition) to check the condition records for the specified