How To Fix /SCMTMS/TCC_HL_MSG798 - Rate found for line &1 rate &2 for blank scale value &3

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_HL_MSG -

• Message number: 798

• Message text: Rate found for line &1 rate &2 for blank scale value &3

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 /SCMTMS/TCC_HL_MSG798 - Rate found for line &1 rate &2 for blank scale value &3 ?

  The SAP error message /SCMTMS/TCC_HL_MSG798 typically relates to issues in the Transportation Management System (TMS) within SAP. This specific error indicates that a rate was found for a transportation line item, but the scale value is blank, which can lead to confusion in rate determination.
  Cause:
  
  Missing Scale Value: The error suggests that the system is trying to determine a rate for a transportation charge but cannot find a valid scale value. Scale values are used to define how rates are applied based on certain criteria (like weight, volume, distance, etc.).
  Configuration Issues: There may be a configuration issue in the rate determination setup, where the scale values are not properly defined or linked to the rate.
  Data Inconsistencies: There could be inconsistencies in the master data or transactional data that lead to the absence of a scale value.
  
  Solution:
  
  
  Check Rate Configuration:
  
  Go to the rate determination configuration in SAP and ensure that the scale values are properly defined for the relevant rate types.
  Verify that the rate records are complete and that they include scale values.
  
  
  
  Review Master Data:
  
  Check the master data related to the transportation charges, such as the condition records for freight, to ensure that all necessary fields, including scale values, are populated correctly.
  
  
  
  Update Scale Values:
  
  If the scale values are missing, you may need to create or update the condition records to include the appropriate scale values.
  
  
  
  Test Rate Determination:
  
  After making changes, perform a test to see if the error persists. You can simulate the transportation charge calculation to verify that the rates are being determined correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help notes related to transportation management and rate determination for additional guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and data, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, VK11 for maintaining condition records, or VT01N for creating transportation orders.
  SAP Notes: Look for relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Community Forums: SAP Community and other forums can be helpful for finding similar issues faced by other users and their solutions.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.