How To Fix IDFIES355 - Archived data was not saved.

SAP Error Message - Details

• Message type: E = Error

• Message class: IDFIES - Message Class for Spain

• Message number: 355

• Message text: Archived data was not saved.

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 IDFIES355 - Archived data was not saved. ?

  The SAP error message IDFIES355, which states "Archived data was not saved," typically occurs during the archiving process when the system encounters issues that prevent the successful saving of archived data. Here are some common causes, potential solutions, and related information regarding this error:
  Causes:
  
  Database Issues: There may be problems with the database connection or the database itself, such as insufficient space or corruption.
  Authorization Issues: The user executing the archiving process may not have the necessary authorizations to write to the archive.
  Configuration Errors: Incorrect configuration settings in the archiving object or archiving process can lead to this error.
  File System Issues: The file system where the archived data is supposed to be saved may be full or not accessible.
  Transport Issues: If the archiving process involves transporting data between systems, issues in the transport layer can cause failures.
  
  Solutions:
  
  Check Database Status: Ensure that the database is up and running, and check for any errors in the database logs. Make sure there is enough space available.
  Review Authorizations: Verify that the user has the necessary authorizations to perform archiving. This can be checked in transaction SU53 or by consulting with your security team.
  Configuration Review: Check the configuration settings for the archiving object in transaction SARA. Ensure that all settings are correct and that the archiving object is properly defined.
  File System Check: Verify that the file system where the archive files are being saved has sufficient space and is accessible. Check for any permission issues.
  Review Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into what went wrong during the archiving process.
  Retry the Process: After addressing any identified issues, retry the archiving process to see if the error persists.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Archiving Documentation: Review SAP documentation related to archiving processes for best practices and configuration guidelines.
  Support Community: Consider reaching out to the SAP Community or forums for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.