How To Fix /SAPCND/DB_ACCESS060 - Case 4: Check existency of condition records for reference type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 060

• Message text: Case 4: Check existency of condition records for reference type &1

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_ACCESS060 - Case 4: Check existency of condition records for reference type &1 ?

  The SAP error message /SAPCND/DB_ACCESS060 with the description "Case 4: Check existence of condition records for reference type &1" typically indicates that the system is unable to find the necessary condition records for a specific reference type in the condition table. This can occur in various scenarios, such as pricing, discounts, or other condition-based functionalities in SAP.
  Cause:
  
  Missing Condition Records: The most common cause is that the required condition records for the specified reference type (e.g., pricing, discounts) do not exist in the database.
  Incorrect Configuration: There may be an issue with the configuration of the condition types or access sequences, leading to the system not being able to find the relevant records.
  Data Inconsistency: There could be inconsistencies in the data, such as missing master data (e.g., customer, material) that are required to determine the condition records.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the condition records.
  
  Solution:
  
  
  Check Condition Records: 
  
  Use transaction code VK13 (for pricing conditions) or VK11 (to create pricing conditions) to check if the condition records for the specified reference type exist.
  Ensure that the relevant condition records are created and active.
  
  
  
  Review Configuration:
  
  Check the configuration of the condition types and access sequences in the customizing settings (transaction code SPRO).
  Ensure that the access sequence is correctly set up to retrieve the condition records based on the required criteria.
  
  
  
  Verify Master Data:
  
  Ensure that all necessary master data (e.g., customer, material, sales organization) is correctly maintained and available in the system.
  Check if the master data is relevant for the condition records you are trying to access.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the condition records. This can be checked with the help of your SAP security team.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the program or transaction that is generating the error to identify where the failure occurs.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  VK13 - Display Condition Records
  VK11 - Create Condition Records
  SPRO - Customizing Implementation Guide
  
  
  Condition Types: Understand the specific condition type related to the error message and its configuration.
  Access Sequences: Review the access sequences associated with the condition types to ensure they are set up correctly.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.