How To Fix COND_API213 - This record cuts off another record in the database

SAP Error Message - Details

• Message type: E = Error

• Message class: COND_API - Messages for the Condition API

• Message number: 213

• Message text: This record cuts off another record in the database

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 COND_API213 - This record cuts off another record in the database ?

  The SAP error message COND_API213 indicates that there is a conflict in the condition records in the database. Specifically, it means that the condition record you are trying to create or modify overlaps with an existing record, which can lead to inconsistencies in pricing or other condition-related data.
  Cause:
  The error typically arises due to one of the following reasons:
  
  Overlapping Validity Periods: The validity periods of the condition records you are trying to create or modify overlap with those of existing records.
  Duplicate Keys: The combination of key fields (like condition type, customer, material, etc.) already exists in the database with a different validity period or other attributes.
  Incorrect Data Entry: There may be a mistake in the data being entered, leading to conflicts with existing records.
  
  Solution:
  To resolve the COND_API213 error, you can take the following steps:
  
  
  Check Existing Records:
  
  Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to review existing condition records for the same condition type and key fields.
  Look for overlapping validity periods or duplicate entries.
  
  
  
  Adjust Validity Periods:
  
  If you find overlapping records, you may need to adjust the validity periods of the existing records or the new record you are trying to create.
  Ensure that the new record's validity does not conflict with existing records.
  
  
  
  Delete or Archive Old Records:
  
  If certain records are no longer needed, consider deleting or archiving them to eliminate the conflict.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to condition records for specific guidelines on managing overlaps and conflicts.
  
  
  
  Use Transaction Codes:
  
  Use transaction codes like VK11 (Create Condition) to create new records after ensuring there are no conflicts.
  
  
  
  Check for Custom Logic:
  
  If your organization has custom logic implemented in the pricing procedure, ensure that it is not causing the conflict.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13, and VK31 (for mass changes).
  Condition Types: Understand the condition types being used and their configurations in the pricing procedure.
  SAP Notes: Check for any SAP Notes related to COND_API213 for additional insights or patches that may address the issue.
  User Authorization: Ensure that you have the necessary authorizations to view and modify condition records.
  
  By following these steps, you should be able to identify the cause of the COND_API213 error and implement a solution to resolve it.