How To Fix /SCMTMS/TSPS024 - TCM cost could not be determined for &1 with carrier &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TSPS -

• Message number: 024

• Message text: TCM cost could not be determined for &1 with carrier &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/TSPS024 - TCM cost could not be determined for &1 with carrier &2 ?

  The SAP error message /SCMTMS/TSPS024 indicates that the Transportation Management System (TMS) could not determine the Transportation Cost Management (TCM) cost for a specific transportation request or shipment with a given carrier. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Missing Costing Information: The system may not have the necessary costing information for the specified carrier. This could include missing or incomplete data in the condition records for freight costs.
  
  
  Carrier Configuration Issues: The carrier may not be properly configured in the system, or the relevant transportation lanes may not be set up correctly.
  
  
  Inconsistent Master Data: There may be inconsistencies in the master data related to the transportation request, such as incorrect or missing data in the shipment, transportation lanes, or freight agreements.
  
  
  Invalid or Inactive Carrier: The carrier specified may be inactive or not valid for the specific transportation request.
  
  
  Missing or Incorrect Pricing Procedures: The pricing procedures for the transportation costs may not be correctly defined or assigned.
  
  
  Solutions:
  
  
  Check Condition Records: Verify that the condition records for the freight costs are maintained correctly for the specified carrier. Ensure that the necessary pricing conditions are set up in the system.
  
  
  Review Carrier Configuration: Ensure that the carrier is properly configured in the system. Check the transportation lanes and ensure that they are active and correctly defined.
  
  
  Validate Master Data: Review the master data related to the transportation request, including shipment details, transportation lanes, and freight agreements. Correct any inconsistencies or missing information.
  
  
  Check Carrier Status: Ensure that the carrier is active and valid for the transportation request. If the carrier is inactive, consider reactivating it or selecting a different carrier.
  
  
  Examine Pricing Procedures: Review the pricing procedures assigned to the transportation request. Ensure that they are correctly defined and applicable to the scenario.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on configuring transportation costs and resolving related issues.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/TS for transportation scheduling or /SCMTMS/PRC for pricing to investigate further.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By systematically checking these areas, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.