How To Fix EARC713 - Number of checked TOU exceptions: &1. &2 of which can be archived

SAP Error Message - Details

• Message type: E = Error

• Message class: EARC - IS-U: Archiving

• Message number: 713

• Message text: Number of checked TOU exceptions: &1. &2 of which can be 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 EARC713 - Number of checked TOU exceptions: &1. &2 of which can be archived ?

  The SAP error message EARC713 indicates an issue related to the archiving of Time-Dependent Objects (TOU) in the SAP system. This message typically arises during the archiving process when the system checks for exceptions that prevent certain data from being archived.
  Cause:
  The error message EARC713 is triggered when the archiving process identifies a number of exceptions related to the Time-Dependent Objects (TOU). The message format indicates:
  
  &1: The total number of checked TOU exceptions.
  &2: The number of exceptions that can actually be archived.
  
  This means that while the system has checked a certain number of TOU exceptions, only a subset of them is eligible for archiving, possibly due to various constraints or dependencies.
  Possible Causes for Exceptions:
  
  Data Dependencies: Some TOU records may have dependencies on other records that prevent them from being archived.
  Incomplete Data: Records may be incomplete or not meet the criteria for archiving.
  Configuration Issues: The archiving configuration may not be set up correctly, leading to exceptions.
  Authorization Issues: Lack of proper authorizations may prevent certain records from being archived.
  
  Solution:
  To resolve the EARC713 error, you can take the following steps:
  
  Review the Exceptions: Check the detailed log or report that accompanies the error message to understand the specific exceptions that are preventing archiving.
  Analyze Dependencies: Investigate any dependencies that may exist for the TOU records. Ensure that all related records are either archived or no longer needed.
  Correct Data Issues: If there are incomplete or incorrect records, take the necessary steps to correct or complete the data.
  Adjust Archiving Configuration: Review the archiving configuration settings in the SAP system to ensure they are correctly set up for the TOU.
  Check Authorizations: Ensure that the user executing the archiving process has the necessary authorizations to archive the records.
  Consult Documentation: Refer to SAP documentation or notes related to archiving TOU for any specific guidelines or troubleshooting steps.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on archiving TOU.
  Archiving Guidelines: Familiarize yourself with the general guidelines for archiving in SAP, including prerequisites and best practices.
  Transaction Codes: Use transaction codes like SARA (Archive Administration) to manage archiving processes and monitor the status of archiving jobs.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.