How To Fix /SCMTMS/TC_RATES118 - At dimension &1, scale item key changed from &2 to &3; this is disallowed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TC_RATES -

• Message number: 118

• Message text: At dimension &1, scale item key changed from &2 to &3; this is disallowed

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/TC_RATES118 - At dimension &1, scale item key changed from &2 to &3; this is disallowed ?

  The SAP error message /SCMTMS/TC_RATES118 typically occurs in the context of Transportation Management (TM) when there is an inconsistency in the scale item keys during the processing of transportation rates. This error indicates that at a specific dimension (e.g., weight, volume), the scale item key has changed from one value to another, which is not allowed.
  Cause:
  The error is caused by an attempt to modify or process transportation rates where the scale item key for a specific dimension has been altered. This can happen due to:
  
  Data Inconsistency: There may be inconsistencies in the rate tables or master data where the scale item keys are defined.
  Incorrect Configuration: The configuration of the transportation rates may not align with the expected values, leading to discrepancies.
  Manual Changes: Manual changes to the rate records or scale items that violate the integrity of the data.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Rate Records: Review the transportation rate records to ensure that the scale item keys are consistent and correctly defined. Look for any discrepancies in the scale items for the affected dimension.
  
  
  Review Configuration: Verify the configuration settings in the Transportation Management module. Ensure that the scale items and their keys are set up correctly according to the business requirements.
  
  
  Data Consistency Check: Run consistency checks on the relevant master data and rate tables to identify any inconsistencies. You may need to use transaction codes or reports specific to TM to perform these checks.
  
  
  Recreate Rate Records: If necessary, consider recreating the affected rate records to ensure that the scale item keys are correctly assigned from the beginning.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to transportation rates and scale items for any specific guidelines or known issues.
  
  
  Contact SAP Support: If the issue persists and you cannot identify the root cause, consider reaching out to SAP support for assistance. Provide them with detailed information about the error and the context in which it occurs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/TC_RATES for managing transportation rates.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional guidance on handling transportation rates.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.