How To Fix EARC247 - Check in user exit ETOAR004; document is not to be archived

SAP Error Message - Details

• Message type: E = Error

• Message class: EARC - IS-U: Archiving

• Message number: 247

• Message text: Check in user exit ETOAR004; document is not to 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 EARC247 - Check in user exit ETOAR004; document is not to be archived ?

  The SAP error message EARC247 indicates that a document is not eligible for archiving due to certain conditions defined in the user exit ETOAR004. This user exit is part of the archiving process in SAP and is used to implement custom logic to determine whether a document can be archived or not.
  Cause:
  The error message EARC247 typically arises when:
  
  
  Business Rules: The document does not meet specific business rules or criteria defined in the user exit ETOAR004. This could include conditions such as:
  
  The document is still open or in use.
  The document has not reached the required retention period.
  There are dependencies or linked documents that prevent archiving.
  
  
  
  Configuration Issues: There may be configuration settings in the archiving object that restrict the archiving of certain documents.
  
  
  Custom Logic: If there is custom logic implemented in the user exit that explicitly prevents archiving for certain document types or statuses.
  
  
  Solution:
  To resolve the EARC247 error, you can take the following steps:
  
  
  Review User Exit ETOAR004:
  
  Check the implementation of the user exit ETOAR004 to understand the conditions that are preventing the document from being archived.
  If necessary, modify the logic to allow archiving under certain conditions or to ensure that the conditions are correctly defined.
  
  
  
  Check Document Status:
  
  Verify the status of the document in question. Ensure that it is not in a state that would prevent archiving (e.g., still open, pending approvals, etc.).
  
  
  
  Retention Period:
  
  Ensure that the document has met the required retention period as defined in the archiving object configuration.
  
  
  
  Dependencies:
  
  Check for any dependencies or linked documents that may be preventing the archiving process. Resolve any issues with these dependencies.
  
  
  
  Consult Documentation:
  
  Review SAP documentation related to archiving and the specific archiving object you are working with to ensure compliance with all requirements.
  
  
  
  Testing:
  
  After making any changes, test the archiving process with the document to confirm that the issue has been resolved.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide guidance on the EARC247 error.
  Archiving Objects: Familiarize yourself with the specific archiving object you are working with, as each object may have its own set of rules and configurations.
  User Exits: Understand how user exits work in SAP and how they can be used to customize standard processes.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.