How To Fix /SCMTMS/TCC_MSG021 - Rate access for line &1 charge ty. &2 ended in errors; chk exception log

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_MSG -

• Message number: 021

• Message text: Rate access for line &1 charge ty. &2 ended in errors; chk exception log

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_MSG021 - Rate access for line &1 charge ty. &2 ended in errors; chk exception log ?

  The SAP error message /SCMTMS/TCC_MSG021 indicates that there was an issue with the rate access for a specific line item in the Transportation Management System (TMS). This error typically occurs when the system is unable to retrieve the necessary rate information for a charge type during the transportation planning process.
  Cause:
  
  Missing Rate Records: The most common cause is that there are no rate records available for the specified charge type and the conditions defined in the rate determination procedure.
  Incorrect Configuration: The configuration for rate determination might be incorrect or incomplete, leading to the system not being able to find the appropriate rates.
  Data Inconsistencies: There may be inconsistencies or missing data in the master data (e.g., transportation lanes, freight agreements) that are required for rate determination.
  Authorization Issues: The user may not have the necessary authorizations to access the rate records.
  
  Solution:
  
  Check Exception Log: As suggested in the error message, check the exception log for more detailed information about the error. This log can provide insights into what specifically went wrong during the rate determination process.
  Verify Rate Records: Ensure that the necessary rate records exist for the charge type in question. You can do this by navigating to the relevant transaction codes (e.g., /SCMTMS/FRG for freight agreements) and checking if the rates are correctly defined.
  Review Configuration: Review the configuration settings for rate determination in TMS. Ensure that all necessary settings are correctly configured, including the rate determination procedure and the conditions.
  Check Master Data: Verify that all relevant master data (e.g., transportation lanes, shipping points, and freight agreements) is correctly maintained and complete.
  User Authorizations: Ensure that the user has the necessary authorizations to access the rate records. This may involve checking roles and permissions in the SAP system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMTMS/FRG for freight agreements, /SCMTMS/TCC for rate determination configuration, and /SCMTMS/EXC_LOG for viewing exception logs.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on resolving this error.
  Documentation: Refer to the SAP Help Portal or the specific documentation for SAP Transportation Management for detailed information on rate determination and configuration.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.