How To Fix /SAPCND/DB_ACCESS062 - Evl-Scale record for varnumh &1 in table &2 missing

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/DB_ACCESS -

• Message number: 062

• Message text: Evl-Scale record for varnumh &1 in table &2 missing

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_ACCESS062 - Evl-Scale record for varnumh &1 in table &2 missing ?

  The SAP error message /SAPCND/DB_ACCESS062 Evl-Scale record for varnumh &1 in table &2 missing typically indicates that there is a missing evaluation scale record in the specified table. This error is often related to the condition management or pricing procedures in SAP, particularly in the context of condition records for pricing, discounts, or other related functionalities.
  
  Cause:
  
  Missing Data: The evaluation scale record for the specified variable number (varnumh) is not found in the specified table (&2). This could be due to data not being maintained or deleted inadvertently.
  
  Configuration Issues: There may be issues with the configuration of the condition types or scales in the pricing procedure.
  Transport Issues: If the system has recently undergone a transport of changes, the necessary condition records may not have been transported correctly.
  Data Inconsistency: There could be inconsistencies in the database that lead to missing records.
  
  
  Solution:
  
  Check Condition Records: Verify if the condition records for the specified variable