How To Fix CONNECT_PRC_SAPCND022 - VARNUMH for the condition record does not exist in EVL scale table

SAP Error Message - Details

• Message type: E = Error

• Message class: CONNECT_PRC_SAPCND -

• Message number: 022

• Message text: VARNUMH for the condition record does not exist in EVL scale table

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 CONNECT_PRC_SAPCND022 - VARNUMH for the condition record does not exist in EVL scale table ?

  The SAP error message CONNECT_PRC_SAPCND022 VARNUMH typically indicates that a condition record does not exist in the specified scale table (in this case, the EVL scale table). This error often arises in the context of pricing conditions, where the system is unable to find the necessary condition records to process a pricing request.
  Cause:
  
  Missing Condition Records: The most common cause is that the condition records for the specified pricing condition type do not exist in the EVL scale table.
  Incorrect Configuration: There may be an issue with the configuration of the pricing procedure or condition types.
  Data Inconsistency: There could be inconsistencies in the master data or transactional data that prevent the system from finding the relevant condition records.
  Incorrect Access Sequence: The access sequence defined for the condition type may not be set up correctly, leading to the inability to find the condition records.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) and check if the condition records for the relevant condition type exist.
  If they do not exist, create the necessary condition records.
  
  
  
  Review Access Sequence:
  
  Check the access sequence assigned to the condition type in the pricing procedure. Ensure that it is correctly configured to access the relevant scale table.
  You can do this by navigating to the transaction code V/07 (Access Sequences) and reviewing the access sequence settings.
  
  
  
  Verify Pricing Procedure:
  
  Ensure that the pricing procedure assigned to the sales document or purchase order is correctly configured and includes the necessary condition types.
  You can check this in the transaction code V/08 (Pricing Procedures).
  
  
  
  Check Master Data:
  
  Ensure that the relevant master data (such as customer master, material master, etc.) is correctly maintained and that there are no missing or incorrect entries that could affect pricing.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing logic to identify where the failure occurs. This may require assistance from a technical consultant.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for any additional insights or updates.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11 / VK12: Create/Change Condition Records
  V/07: Access Sequences
  V/08: Pricing Procedures
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  SAP Community: Engage with the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.