How To Fix FG653 - Total of documents read/archived: &/&

SAP Error Message - Details

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 653

• Message text: Total of documents read/archived: &/&

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 FG653 - Total of documents read/archived: &/& ?

  The SAP error message FG653, which states "Total of documents read/archived: &/&," typically occurs during the archiving process in SAP. This message indicates that there is a discrepancy between the number of documents that were expected to be archived and the actual number of documents processed.
  Cause:
  
  Data Selection Issues: The selection criteria used for archiving may not match the documents in the database, leading to fewer documents being archived than expected.
  Document Status: Some documents may not be eligible for archiving due to their status (e.g., they may still be in use or locked).
  Configuration Issues: There may be issues with the archiving object configuration or the archiving settings in the system.
  Authorization Issues: The user executing the archiving process may not have the necessary authorizations to access all the documents.
  Technical Errors: There could be technical issues such as database locks, inconsistencies, or other errors that prevent documents from being archived.
  
  Solution:
  
  Check Selection Criteria: Review the selection criteria used for the archiving run to ensure they are correct and match the documents you intend to archive.
  Review Document Status: Check the status of the documents that were not archived. Ensure that they are eligible for archiving and not locked or in use.
  Configuration Review: Verify the configuration settings for the archiving object in transaction SARA. Ensure that all necessary settings are correctly defined.
  Authorization Check: Ensure that the user executing the archiving process has the necessary authorizations to access and archive the documents.
  Log Analysis: Check the archiving logs for any errors or warnings that may provide more insight into why certain documents were not archived.
  Test Archiving: Perform a test archiving run with a smaller selection of documents to see if the issue persists. This can help isolate the problem.
  Consult SAP Notes: Look for relevant SAP Notes that may address known issues related to the FG653 message or the specific archiving object you are working with.
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Used for managing archiving objects.
  SARI: Used for displaying archived data.
  
  
  SAP Documentation: Refer to the official SAP documentation for archiving processes and best practices.
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.