How To Fix /SAPCND/DB_ACCESS068 - Case 5: Check overlapping condition records

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 068

• Message text: Case 5: Check overlapping condition records

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 /SAPCND/DB_ACCESS068 - Case 5: Check overlapping condition records ?

  The SAP error message /SAPCND/DB_ACCESS068 typically indicates an issue related to overlapping condition records in the SAP system. This error is often encountered in the context of condition management, particularly when dealing with pricing, discounts, or other condition-based functionalities.
  
  Cause:
  The error occurs when there are overlapping condition records in the database. This means that two or more condition records exist for the same key (e.g., the same material, customer, or pricing date) that have overlapping validity periods. This can lead to ambiguity in determining which condition record should be applied during pricing calculations.
  
  Solution:
  To resolve this error, you need to identify and correct the overlapping condition records. Here are the steps you can take:
  
  
  Identify Overlapping Records:
  
  Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to review the condition records for the relevant condition type.
  Check the validity periods of the condition records to identify any overlaps.
  
  
  
  Adjust Validity Periods:
  
  If you find overlapping