How To Fix /SCMTMS/CFIR160 - Attachment transferred to new document

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/CFIR -

• Message number: 160

• Message text: Attachment transferred to new document

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/CFIR160 - Attachment transferred to new document ?

  The SAP error message /SCMTMS/CFIR160 typically indicates that an attachment has been successfully transferred to a new document within the SAP Transportation Management System (TMS). This message is not necessarily an error but rather an informational message indicating that the system has processed the attachment as part of a document transfer.
  Cause:
  The message is triggered when an attachment (such as a document or file) is moved or copied from one document to another within the TMS. This can occur during various processes, such as:
  
  Creating a new transportation document based on an existing one.
  Transferring attachments during the creation of freight orders, shipment documents, or other related documents.
  
  Solution:
  Since this message is informational, there is typically no action required unless you are experiencing issues with the attachment transfer. However, if you are facing problems related to attachments, consider the following steps:
  
  
  Verify Attachment Status: Check if the attachment has been successfully transferred to the new document. You can do this by opening the new document and looking for the attachment.
  
  
  Check Document Links: Ensure that the original document and the new document are correctly linked and that the attachment is accessible from both.
  
  
  Review User Authorizations: Make sure that the user has the necessary permissions to view and manage attachments in both the original and new documents.
  
  
  Consult SAP Notes: If you suspect that there is a bug or issue with the attachment transfer process, check the SAP Support Portal for any relevant SAP Notes or updates that may address the issue.
  
  
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the attachment transfer process.
  
  
  Contact SAP Support: If the issue persists or if you believe there is a problem with the functionality, consider reaching out to SAP Support for further assistance.
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for Transportation Management for detailed information on document management and attachment handling.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar messages and can share their experiences or solutions.
  Training and Resources: Consider training sessions or resources on SAP TMS to better understand document handling and attachment processes.
  
  In summary, the /SCMTMS/CFIR160 message is generally not an error but an indication of a successful attachment transfer. If you encounter issues, follow the steps outlined above to troubleshoot and resolve any related problems.