How To Fix EARC606 - &1 documents checked. &2 archivable, &3 not archivable

SAP Error Message - Details

• Message type: E = Error

• Message class: EARC - IS-U: Archiving

• Message number: 606

• Message text: &1 documents checked. &2 archivable, &3 not archivable

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 EARC606 - &1 documents checked. &2 archivable, &3 not archivable ?

  The SAP error message EARC606 indicates that during the archiving process, a certain number of documents were checked, and the system has classified them into two categories: those that are archivable and those that are not. The message format typically looks like this:
  EARC606 &1 documents checked. &2 archivable, &3 not archivable.
  Cause
  The error message is primarily informational and indicates the results of an archiving check. The causes for documents being classified as "not archivable" can include:
  
  Document Status: The document may be in a status that does not allow it to be archived (e.g., it is still open or in use).
  Retention Period: The document may not have reached the end of its retention period as defined in the archiving object settings.
  Dependencies: There may be dependencies on other documents or data that prevent archiving.
  Configuration Issues: The archiving object may not be properly configured, or the necessary prerequisites for archiving may not be met.
  
  Solution
  To resolve the issue, you can take the following steps:
  
  
  Review Document Status: Check the status of the documents that are not archivable. If they are still in use or open, you may need to close or finalize them before archiving.
  
  
  Check Retention Period: Verify the retention period settings for the archiving object. Ensure that the documents have met the criteria for archiving.
  
  
  Analyze Dependencies: Investigate if there are any dependencies or linked documents that are preventing archiving. Resolve any issues related to these dependencies.
  
  
  Configuration Review: Ensure that the archiving object is correctly configured in the system. This includes checking the settings in transaction SARA (Archive Administration).
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific archiving object you are working with for any additional requirements or considerations.
  
  
  Run Archiving Jobs: If necessary, run the archiving jobs again after addressing the issues identified.
  
  
  Related Information
  
  Transaction SARA: This is the main transaction for managing archiving in SAP. You can use it to check the status of archiving objects and their configuration.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to archiving for your version of SAP.
  Archiving Object Documentation: Each archiving object has specific documentation that outlines the requirements and processes for archiving. Make sure to review this documentation for the object you are working with.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or functional team for further assistance, as they may have more insights into the specific configuration and data in your system.