How To Fix VYSC814 - Pricing error: scale value exists, but no (freight) rates

SAP Error Message - Details

• Message type: E = Error

• Message class: VYSC - Output for Scale Processing

• Message number: 814

• Message text: Pricing error: scale value exists, but no (freight) rates

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 VYSC814 - Pricing error: scale value exists, but no (freight) rates ?

  The SAP error message VYSC814 indicates that there is a pricing issue related to scale values in the pricing procedure. Specifically, it means that while there are scale values defined for a pricing condition, there are no corresponding freight rates available for those scale values. This can occur in scenarios where freight charges are calculated based on certain conditions, but the necessary data is missing.
  Cause:
  
  Missing Freight Rates: The most common cause is that the freight rates for the relevant condition type are not maintained in the system.
  Incorrect Condition Records: There may be condition records that are not properly set up or are incomplete.
  Scale Values Defined: Scale values exist in the pricing procedure, but they do not have associated rates defined.
  Condition Type Configuration: The configuration for the condition type may not be set up correctly to allow for the calculation of freight based on the defined scale values.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the relevant condition records for freight are maintained.
  Ensure that the scale values and corresponding rates are correctly defined.
  
  
  
  Maintain Freight Rates:
  
  If the freight rates are missing, you will need to create or update the condition records for the relevant condition type (e.g., freight condition types like FRA1, FRA2, etc.).
  Ensure that the scale values are correctly linked to the rates.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document type to ensure that it includes the necessary condition types for freight.
  Use transaction code V/08 to review and adjust the pricing procedure if necessary.
  
  
  
  Test Pricing:
  
  After making the necessary adjustments, test the pricing in a sales order or delivery to ensure that the error is resolved.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration or how to maintain condition records, refer to SAP documentation or consult with your SAP functional consultant.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11 / VK12: Create/Change Condition Records
  V/08: Maintain Pricing Procedures
  V/06: Maintain Condition Types
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to pricing errors.
  User Exits and Enhancements: If custom logic is involved in pricing, ensure that any user exits or enhancements are functioning correctly.
  
  By following these steps, you should be able to resolve the VYSC814 error and ensure that the pricing calculations work as intended.