How To Fix FG651 - Number of document headers read/archived: &/&

FG651 - Overview

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 651

• Message text: Number of document headers read/archived: &/&

What causes this issue?

&v1& document headers were read during the current program run for
archiving documents, of which &v2& meet all archiving criteria.
In the subsequent processing, &v2& documents are checked item by item
to see whether they can be archived.

System Response

Information

How to fix this error?

You can carry out a consistency check at the end of the archiving run:
The number of document headers read (&v1&) corresponds to the number of
documents selected in the statistics.
The number of documents which can be archived (&v2&) is only a subtotal
which does not appear in the log.
The number of documents archived in the statistics is the corresponding
value from message FG653 after the check has taken place at item level.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FG651 - Number of document headers read/archived: &/& ?

  The SAP error message FG651 typically relates to issues with document archiving in the SAP system. This message indicates that there is a problem with the number of document headers that have been read or archived, which can affect the retrieval and management of archived documents.
  
  Cause:
  
  Archiving Issues: The error may occur if there are inconsistencies in the archiving process, such as missing or corrupted data.
  Configuration Problems: Incorrect configuration settings in the archiving object or the archiving process can lead to this error.
  Database Issues: Problems with the database, such as locks or performance issues, can prevent the system from reading or archiving documents correctly.
  Authorization Issues: Lack of proper authorizations for the user trying to access or archive the documents can also trigger this error.
  
  
  Solution:
  
  Check Archiving Configuration: Review the configuration settings for the archiving object in transaction SARA. Ensure that all settings are correct and that the archiving process is properly defined.
  Run