How To Fix /SCMTMS/TCC_MSG660 - No internal charges found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_MSG -

• Message number: 660

• Message text: No internal charges found

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_MSG660 - No internal charges found ?

  The SAP error message /SCMTMS/TCC_MSG660 No internal charges found typically occurs in the context of SAP Transportation Management (TM) when there are no internal charges defined for a transportation charge calculation. This can happen during the planning or execution of transportation processes when the system is trying to determine the costs associated with a transportation activity.
  Cause:
  
  Missing Charge Master Data: The internal charges (like freight costs, handling fees, etc.) may not be defined in the system.
  Incorrect Configuration: The configuration for charge calculation may not be set up correctly, leading to the system not being able to find applicable charges.
  Charge Type Not Assigned: The specific charge type that should be applied to the transportation process may not be assigned or available.
  Data Inconsistencies: There may be inconsistencies or missing data in the relevant master data (e.g., business partners, transportation lanes, etc.).
  
  Solution:
  
  
  Check Charge Master Data:
  
  Go to the charge master data in SAP TM and ensure that the necessary internal charges are defined.
  Verify that the charges are active and applicable to the relevant transportation scenarios.
  
  
  
  Review Configuration:
  
  Check the configuration settings for charge calculation in SAP TM. Ensure that the necessary settings for charge types and conditions are correctly configured.
  Make sure that the charge calculation schema is properly set up.
  
  
  
  Assign Charge Types:
  
  Ensure that the relevant charge types are assigned to the transportation lanes or other relevant master data.
  If necessary, create or modify charge types to ensure they are applicable to the transportation process.
  
  
  
  Data Consistency Check:
  
  Review the master data for any inconsistencies or missing information that could affect charge calculation.
  Ensure that all relevant business partners, transportation lanes, and other related data are correctly maintained.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test run to see if the error persists.
  Monitor the logs for any additional error messages that may provide further insight.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on charge calculation in SAP TM.
  Documentation: Refer to the SAP Help Portal for detailed documentation on charge calculation and configuration in SAP TM.
  Community Forums: Engage with SAP community forums or user groups for shared experiences and solutions from other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.