How To Fix TN713 - File &1 sent, decompressed, and then deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: TN - Support Package Manager (SPAM) Messages

• Message number: 713

• Message text: File &1 sent, decompressed, and then deleted

What causes this issue?

The selected file was passed to the application server and decompressed.
The compressed file was then deleted from the application server.
You can now use transaction SAINT or SPAM to import the package
contained in this file.

System Response

The selected file was decompressed to the EPS inbox. The compressed file
was deleted from the application server at the end of the operation,
since it is activated in the <LS>Delete file after decompression </>
option. (To display the settings for transaction SAINT or SPAM, choose
<LS>Extras -> Settings</> on the initial screen.)

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TN713 - File &1 sent, decompressed, and then deleted ?

  The SAP error message TN713 indicates that a file was sent, decompressed, and then deleted. This message typically occurs in the context of file transfer processes, particularly when using the SAPconnect (SAPoffice) or SAP's communication infrastructure for sending files.
  Cause:
  
  File Transfer Process: The error message TN713 is informational rather than an error. It indicates that the system has successfully sent a file, decompressed it, and then deleted the original file from the temporary storage location.
  Configuration Issues: If the file is not being processed as expected, it could be due to misconfiguration in the file transfer settings or the communication method being used.
  File Handling: The message may also appear if there are issues with how files are being handled post-transfer, such as permissions or file path issues.
  
  Solution:
  
  Check Configuration: Ensure that the configuration for file transfer in SAP is set up correctly. This includes checking the settings for the communication method, file paths, and any relevant parameters.
  Review Logs: Look at the application logs (transaction SLG1) for any additional messages or errors that may provide more context about the file transfer process.
  File Permissions: Verify that the user or service account has the necessary permissions to access the file locations involved in the transfer.
  Monitor File Transfers: If this message is part of a larger issue, monitor the file transfer processes to ensure that files are being sent and received as expected.
  Consult Documentation: Refer to SAP documentation or support notes related to file transfer processes for any specific guidance or troubleshooting steps.
  
  Related Information:
  
  SAPconnect: This is the SAP component responsible for handling communication between SAP systems and external systems, including file transfers.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SOST (to view the status of sent messages) and SCOT (to configure SAPconnect).
  SAP Notes: Check for any SAP Notes that may address specific issues related to file transfers or the TN713 message.
  
  If the message is causing operational issues or if you need further assistance, consider reaching out to SAP support for more tailored help based on your specific system configuration and requirements.