How To Fix /SCMTMS/TCD005 - Charges not found for forwarding order &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCD -

• Message number: 005

• Message text: Charges not found for forwarding order &1

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/TCD005 - Charges not found for forwarding order &1 ?

  The SAP error message /SCMTMS/TCD005 Charges not found for forwarding order &1 typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find any charge conditions or pricing information associated with a specific forwarding order. This can happen for several reasons, and here are some potential causes, solutions, and related information:
  Causes:
  
  Missing Charge Conditions: The charge conditions for the forwarding order may not have been defined or maintained in the system.
  Incorrect Configuration: The configuration settings for charge calculation may not be set up correctly in the system.
  Data Inconsistencies: There may be inconsistencies or missing data in the master data (e.g., customer, vendor, or material master) that are required for charge determination.
  Forwarding Order Status: The status of the forwarding order may not allow for charge determination (e.g., if it is in a status that does not permit pricing).
  Pricing Procedure: The pricing procedure assigned to the forwarding order may not be correctly configured or may not include the necessary conditions.
  
  Solutions:
  
  Check Charge Conditions: Verify that the charge conditions are properly defined in the system. You can do this by navigating to the relevant configuration settings in SAP TM.
  Review Configuration: Ensure that the configuration for charge calculation is correctly set up. This includes checking the pricing procedure and the condition types used.
  Validate Master Data: Check the master data related to the forwarding order (e.g., customer, vendor, and material) to ensure that all necessary information is complete and accurate.
  Forwarding Order Status: Confirm that the forwarding order is in a status that allows for charge determination. If necessary, change the status to one that permits pricing.
  Test Pricing Procedure: If you suspect an issue with the pricing procedure, you can test it in a controlled environment to ensure it is functioning as expected.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as /SCMTMS/FO to access forwarding orders or /SCMTMS/CHARGE to manage charge conditions.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Documentation: Refer to the SAP Help Portal for detailed documentation on charge calculation and forwarding order management in SAP TM.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP TM expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.