How To Fix FG652 - SAP archive &: No.of documents read/archived previously: &/&

SAP Error Message - Details

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 652

• Message text: SAP archive &: No.of documents read/archived previously: &/&

What causes this issue?

&v2& documents were read on the data base during the archiving run, of
which &v3& fulfil all the criteria for being archived. These &v3&
documents were written to an external file.

System Response

Information

How to fix this error?

The total of the documents archived can be found again in the log for
the archiving run and in the archive administration.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FG652 - SAP archive &: No.of documents read/archived previously: &/& ?

  The SAP error message FG652 typically relates to issues encountered during the archiving process of documents in the SAP system. This message indicates that there is a problem with the archiving process, specifically that the system is unable to read or archive documents as expected.
  Cause:
  
  Archiving Object Configuration: The archiving object may not be properly configured, leading to issues in reading or archiving documents.
  Document Status: The documents you are trying to archive may not be in a status that allows them to be archived (e.g., they may still be in use or locked).
  Database Issues: There may be issues with the database that prevent the archiving process from completing successfully.
  Authorization Issues: The user executing the archiving process may not have the necessary authorizations to read or archive the documents.
  Archiving Sessions: There may be existing archiving sessions that are still processing or have not been completed, causing conflicts.
  
  Solution:
  
  Check Configuration: Review the configuration of the archiving object in transaction SARA. Ensure that all settings are correct and that the object is properly defined.
  Document Status Check: Verify the status of the documents you are trying to archive. Ensure that they are eligible for archiving and not locked or in use.
  Database Health: Check the health of the database. Look for any locks, performance issues, or errors that may be affecting the archiving process.
  User Authorizations: Ensure that the user has the necessary authorizations to perform archiving. Check roles and permissions in transaction SU01.
  Review Archiving Sessions: Use transaction SARA to check for any active archiving sessions. If there are sessions that are stuck or incomplete, you may need to resolve those before proceeding.
  Logs and Traces: Check the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context on the issue.
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SLG1: Application Log
  SE38: ABAP Program Execution (to run specific archiving programs)
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to archiving for your version of SAP.
  Documentation: Review SAP documentation on archiving processes for your specific module or application area to ensure compliance with best practices.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.