How To Fix /SCMTMS/TCCS195 - Resolution base &1 not valid for charge type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCCS -

• Message number: 195

• Message text: Resolution base &1 not valid for charge type &2

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/TCCS195 - Resolution base &1 not valid for charge type &2 ?

  The SAP error message /SCMTMS/TCCS195 Resolution base &1 not valid for charge type &2 typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the configuration of charge types and their associated resolution bases.
  Cause:
  
  
  Invalid Configuration: The error indicates that the resolution base specified (represented by &1) is not valid for the charge type (represented by &2) you are trying to use. This could be due to:
  
  The resolution base not being defined for the specific charge type in the system.
  A mismatch between the expected resolution base and the one configured in the system.
  
  
  
  Data Inconsistency: There may be inconsistencies in the master data or configuration settings related to charge types and resolution bases.
  
  
  Missing Customization: If the system has been customized, it’s possible that the necessary settings for the charge type and resolution base have not been properly set up.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for charge types in SAP TM. Ensure that the resolution base you are trying to use is correctly defined for the charge type in question.
  You can check this in the customizing settings under SPRO -> Transportation Management -> Basic Transportation Functions -> Charge Calculation -> Define Charge Types.
  
  
  
  Review Master Data:
  
  Ensure that the master data related to the charge type and resolution base is correctly maintained. This includes checking the relevant settings in the master data for the transportation charges.
  
  
  
  Adjust Settings:
  
  If the resolution base is not valid for the charge type, you may need to either change the resolution base to a valid one or modify the charge type configuration to include the desired resolution base.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for detailed information on how to configure charge types and resolution bases correctly.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs and that the charge calculations are functioning as expected.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on configuration.
  Community Forums: SAP Community and other forums can be helpful for finding similar issues faced by other users and their solutions.
  Transaction Codes: Familiarize yourself with transaction codes related to charge calculation and configuration in SAP TM, such as /SCMTMS/CHARGE for charge management.
  
  If the issue persists after checking the configuration and master data, it may be beneficial to consult with an SAP expert or your technical support team for further investigation.