How To Fix FTR_GENERAL021 - Document & attached successfully

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 021

• Message text: Document & attached successfully

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 FTR_GENERAL021 - Document & attached successfully ?

  The SAP error message FTR_GENERAL021 typically indicates that there is an issue with the document attachment process in the SAP system. The message "Document & attached successfully" suggests that the system is acknowledging the attachment of a document, but there may be underlying issues that need to be addressed.
  Possible Causes:
  
  Document Type Configuration: The document type may not be configured correctly in the system, leading to issues when trying to attach documents.
  Authorization Issues: The user may not have the necessary authorizations to attach documents to the specified transaction or object.
  File Size Limitations: The document being attached may exceed the maximum file size allowed by the system.
  Technical Issues: There may be technical issues with the SAP system, such as database problems or issues with the document management system.
  Incorrect Object Reference: The object to which the document is being attached may not be valid or may not exist.
  
  Solutions:
  
  Check Document Type Configuration: Ensure that the document type is correctly configured in the SAP system. This can be done by checking the settings in the relevant customizing transaction (e.g., OAC2 for document types).
  Verify User Authorizations: Check the user roles and authorizations to ensure that the user has the necessary permissions to attach documents. This can be done through transaction SU01 or SU53.
  Review File Size: Ensure that the document being attached does not exceed the maximum file size limit set in the system. If it does, consider compressing the file or reducing its size.
  Check System Logs: Review the system logs (transaction SLG1) for any related error messages that may provide more context about the issue.
  Test with Different Documents: Try attaching a different document to see if the issue persists. This can help determine if the problem is with a specific document or a broader system issue.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for more details on document management and attachment processes.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to identify the cause of the FTR_GENERAL021 error and implement a suitable solution.