How To Fix /SAPCND/MAINTENANCE060 - No scale entries available in table &1

/SAPCND/MAINTENANCE060 - Overview

• Message type: E = Error

• Message class: /SAPCND/MAINTENANCE -

• Message number: 060

• Message text: No scale entries available in table &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.

/SAPCND/MAINTENANCE060 - Details

• The SAP error message /SAPCND/MAINTENANCE060 No scale entries available in table &1 typically indicates that there are no scale entries available in the specified condition table. This can occur in various scenarios, particularly when working with condition records in pricing, discounts, or other condition-based functionalities.
  
  Cause:
  
  
  Missing Scale Entries: The most common cause is that the condition table specified does not have any scale entries defined. This could be due to:
  
  The condition records were never created.
  The condition records were deleted or not properly maintained.
  The condition records are not valid for the current context (e.g., the validity period has expired).
  
  
  
  Incorrect Configuration: There may be an issue with the configuration of the condition type or the scale type, leading to the absence of expected entries.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the scale entries.
  
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change