How To Fix /SCMTMS/TCC_HL_MSG799 - Rate not found for line &1 rate &2 for matching scale item

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_HL_MSG -

• Message number: 799

• Message text: Rate not found for line &1 rate &2 for matching scale item

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_MSG799 - Rate not found for line &1 rate &2 for matching scale item ?

  The SAP error message /SCMTMS/TCC_HL_MSG799 Rate not found for line &1 rate &2 for matching scale item typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find a valid rate for a specific transportation line item based on the defined rate scales.
  Cause:
  
  Missing Rate Configuration: The most common cause is that the rate configuration for the specified transportation line item is not set up correctly or is missing entirely.
  Incorrect Rate Scale: The rate scale defined for the transportation line item may not match any existing rates in the system.
  Data Inconsistencies: There may be inconsistencies in the data, such as incorrect or incomplete entries in the rate tables.
  Invalid Parameters: The parameters used to determine the rate (like weight, distance, etc.) may not align with the defined scales.
  
  Solution:
  
  
  Check Rate Configuration:
  
  Navigate to the rate management section in SAP TM and verify that the rates for the relevant transportation lanes and conditions are correctly defined.
  Ensure that the rate scales are properly set up and that they match the criteria of the transportation line item.
  
  
  
  Review Rate Scales:
  
  Check the rate scale items to ensure that they are correctly defined and that there are no gaps or missing entries that would prevent the system from finding a match.
  
  
  
  Validate Data:
  
  Review the data for the transportation line item to ensure that all necessary fields (like weight, volume, etc.) are populated correctly and that they correspond to the defined rate scales.
  
  
  
  Test with Different Parameters:
  
  If possible, try adjusting the parameters of the transportation line item to see if a different configuration yields a valid rate.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on setting up rates and scales in SAP TM.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/RA (Rate Management) to access and manage rate configurations.
  Customizing Settings: Ensure that the customizing settings for transportation management are correctly configured to support the rate determination process.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance on this error message.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.