How To Fix /SCMTMS/SFIR140 - Carrier invoice &1: no charges in freight order &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SFIR -

• Message number: 140

• Message text: Carrier invoice &1: no charges in freight order &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/SFIR140 - Carrier invoice &1: no charges in freight order &2 ?

  The SAP error message /SCMTMS/SFIR140 Carrier invoice &1: no charges in freight order &2 typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the carrier invoice processing. This error indicates that the system is unable to find any charges associated with the specified freight order when trying to process the carrier invoice.
  Cause:
  
  Missing Charges: The freight order referenced in the error does not have any associated charges. This could happen if the freight order was created without any cost elements or if the charges were not properly calculated or assigned.
  Incorrect Configuration: There may be configuration issues in the transportation management settings that prevent charges from being generated or linked to the freight order.
  Data Inconsistencies: There could be inconsistencies in the data, such as missing or incorrect entries in the freight order or related documents.
  Incomplete Processing: The freight order may not have been fully processed or completed, leading to a lack of charge information.
  
  Solution:
  
  Check Freight Order: Review the freight order referenced in the error message to ensure that it has the necessary charge information. You can do this by navigating to the freight order in SAP TM and checking the charge details.
  Review Charge Calculation: Ensure that the charge calculation has been performed correctly. If charges are supposed to be generated based on certain conditions, verify that those conditions are met.
  Configuration Review: Check the configuration settings in SAP TM related to charge calculation and freight order processing. Ensure that all necessary settings are correctly configured.
  Data Consistency Check: Perform a data consistency check to identify any discrepancies in the freight order or related documents. Correct any inconsistencies found.
  Reprocess the Freight Order: If the freight order was not fully processed, consider reprocessing it to ensure that all necessary steps have been completed.
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on handling carrier invoices and freight orders.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like /SCMTMS/FREIGHTORDER to access freight orders and review their details.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.