How To Fix /SCMTMS/UI_MESSAGES658 - Carrier invoice &1 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/UI_MESSAGES -

• Message number: 658

• Message text: Carrier invoice &1 not 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/UI_MESSAGES658 - Carrier invoice &1 not found ?

  The SAP error message /SCMTMS/UI_MESSAGES658 Carrier invoice &1 not found typically occurs in the context of SAP Transportation Management (TM) when the system is unable to locate a specific carrier invoice that is referenced in a transaction or process. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  
  Invoice Not Created: The carrier invoice may not have been created in the system. This could happen if the invoicing process was not completed or if there was an error during the creation of the invoice.
  
  
  Incorrect Invoice Number: The invoice number referenced in the transaction may be incorrect or mistyped, leading the system to search for a non-existent invoice.
  
  
  Data Deletion: The invoice might have been deleted or archived, making it unavailable for retrieval.
  
  
  Authorization Issues: The user may not have the necessary permissions to view or access the carrier invoice.
  
  
  System Configuration Issues: There may be configuration issues in the SAP TM module that prevent the proper linking or retrieval of invoices.
  
  
  Solutions:
  
  
  Verify Invoice Creation: Check if the carrier invoice has been created in the system. You can do this by navigating to the relevant transaction or report that lists carrier invoices.
  
  
  Check Invoice Number: Ensure that the invoice number you are using is correct. Double-check for any typographical errors.
  
  
  Review Deletion/Archiving: If the invoice was deleted or archived, consult with your SAP administrator or support team to see if it can be restored or if there are any backup records.
  
  
  Check User Authorizations: Ensure that the user encountering the error has the necessary authorizations to access the carrier invoice. This may require coordination with your SAP security team.
  
  
  Consult Configuration Settings: If the issue persists, review the configuration settings in the SAP TM module to ensure that everything is set up correctly for invoice processing.
  
  
  SAP Notes and Support: Check for any relevant SAP Notes that may address this specific error. You can search the SAP Support Portal for updates or patches that may resolve the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/INVOICE for managing invoices.
  Documentation: Review SAP documentation related to Transportation Management and invoicing processes for additional insights.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team or consult with an SAP expert for further assistance.