How To Fix /SAPCND/DB_ACCESS058 - Case 2: Check existency of condition records for supplementary records

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 058

• Message text: Case 2: Check existency of condition records for supplementary 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_ACCESS058 - Case 2: Check existency of condition records for supplementary records ?

  The SAP error message /SAPCND/DB_ACCESS058 typically indicates an issue related to condition records in the SAP system, particularly when dealing with supplementary records. This error can occur in various scenarios, such as pricing, discounts, or other condition-based functionalities.
  
  Cause:
  The specific case "Check existence of condition records for supplementary records" suggests that the system is unable to find the necessary condition records that are required for processing supplementary records. This can happen due to several reasons:
  
  Missing Condition Records: The required condition records for the specific pricing or discount conditions are not maintained in the system.
  Incorrect Configuration: The configuration settings for the condition types or access sequences may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the data, such as missing keys or incorrect entries in the condition tables.
  Authorization Issues: The user may not have the necessary authorizations to access the condition records.
  
  
  Solution:
  To resolve this error, you can follow these