Do you have any question about this error?
Message type: E = Error
Message class: /SAPCND/DB_ACCESS -
Message number: 068
Message text: Case 5: Check overlapping condition records
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.
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.
/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) orVK12
(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 records, you will need to adjust the validity periods of the condition records. This may involve:
- Changing the start or end dates of one or more records to ensure that they do not overlap.
- Deleting unnecessary or duplicate records.
Check for Custom Logic:
- If your organization has custom pricing logic or enhancements, ensure that these do not inadvertently create overlapping records.
Test Changes:
- After making adjustments, test the pricing procedure to ensure that the error no longer occurs and that the correct condition records are being applied.
Consult Documentation:
- Review SAP documentation or notes related to condition records and pricing to ensure compliance with best practices.
Related Information:
Transaction Codes:
VK13
- Display Condition RecordsVK12
- Change Condition RecordsVK11
- Create Condition RecordsCondition Types:
SAP Notes:
Support:
By following these steps, you should be able to resolve the /SAPCND/DB_ACCESS068
error related to overlapping condition records in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
/SAPCND/DB_ACCESS067
Reference type needs to be provided for case &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPCND/DB_ACCESS066
Condition table needs to be provided for case &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPCND/DB_ACCESS069
Names of scale tables could not be determined for appl &1 and usage &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/SAPCND/DB_ACCESS070
Lin tables names could not be det. for appl &1 usage &2 scalebasetype &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.