How To Fix /SAPCND/DB_ACCESS073 - Case 6: General check of condition records

/SAPCND/DB_ACCESS073 - Overview

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 073

• Message text: Case 6: General check of 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_ACCESS073 - Case 6: General check of condition records ?

  The SAP error message /SAPCND/DB_ACCESS073 typically indicates an issue related to the access or retrieval of condition records in the SAP system. This error can occur during various operations, such as pricing, where the system checks for condition records that are necessary for determining prices, discounts, or other conditions.
  
  Cause:
  The error message /SAPCND/DB_ACCESS073 Case 6: General check of condition records can be caused by several factors, including:
  
  Missing Condition Records: The condition records that the system is trying to access may not exist in the database.
  Authorization Issues: The user may not have the necessary authorizations to access the condition records.
  Database Issues: There may be issues with the database itself, such as corruption or connectivity problems.
  
  Configuration Issues: Incorrect configuration in the pricing procedure or condition types may lead to this error.
  Transport Issues: If condition records were transported from one system to another, they may not have been transported correctly.
  
  
  Solution:
  To resolve the error, you