How To Fix VK072 - No scales exist

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 072

• Message text: No scales exist

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 VK072 - No scales exist ?

  The SAP error message VK072 "No scales exist" typically occurs in the context of pricing and conditions in SAP, particularly when working with condition records for pricing in sales and distribution (SD) or materials management (MM). This error indicates that the system cannot find any valid scales for the condition type you are trying to use.
  Cause:
  
  Missing Scale Records: The most common cause is that there are no scale records defined for the condition type in the pricing procedure.
  Incorrect Condition Type: The condition type being used may not be set up correctly or may not be applicable for the transaction.
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that prevent the system from finding the appropriate scales.
  Condition Record Not Maintained: The condition record for the specific material, customer, or pricing scenario may not have been maintained.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the scales for the relevant condition type exist.
  Ensure that the scales are defined correctly for the specific condition type and that they are valid for the relevant combination of material, customer, and other key fields.
  
  
  
  Maintain Scales:
  
  If no scales exist, you will need to create them. Use transaction VK11 to create the necessary scale records for the condition type.
  Ensure that the scales are set up with the correct values and intervals.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document or purchase order. Ensure that the condition type is included in the pricing procedure and that it is configured correctly.
  
  
  
  Check Master Data:
  
  Verify that the master data (customer master, material master) is correctly maintained and that the relevant data is consistent with the condition records.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration or setup, refer to SAP documentation or consult with your SAP functional consultant for guidance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11: Create Condition Records
  VK12: Change Condition Records
  VK13: Display Condition Records
  V/06: Maintain Condition Types
  V/08: Maintain Pricing Procedures
  
  
  
  Condition Types: Familiarize yourself with the condition types relevant to your pricing scenario, as they dictate how pricing is calculated and what scales are applicable.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to the error message VK072.
  
  
  By following these steps, you should be able to resolve the VK072 error and ensure that the necessary scales are in place for your pricing conditions.