How To Fix RECAAR079 - &1 objects were not archived

SAP Error Message - Details

• Message type: E = Error

• Message class: RECAAR - Data Archiving

• Message number: 079

• Message text: &1 objects were not 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 RECAAR079 - &1 objects were not archived ?

  The SAP error message RECAAR079 indicates that certain objects were not archived during the archiving process. This message typically arises in the context of the SAP Archive Development Kit (ADK) and can occur for various reasons. Below are some common causes, potential solutions, and related information for this error message.
  Causes:
  
  Selection Criteria Issues: The objects you are trying to archive may not meet the selection criteria defined in the archiving job.
  Dependencies: There may be dependencies or relationships with other objects that prevent archiving.
  Status of Objects: The objects may be in a status that does not allow them to be archived (e.g., they are still in use or locked).
  Archiving Object Configuration: The archiving object may not be properly configured, or there may be missing settings in the customizing.
  Authorization Issues: The user executing the archiving job may not have the necessary authorizations to archive certain objects.
  Technical Errors: There could be technical issues such as database locks, inconsistencies, or other system errors.
  
  Solutions:
  
  Check Selection Criteria: Review the selection criteria used in the archiving job to ensure that the objects you want to archive are included.
  Review Object Status: Check the status of the objects that were not archived. Ensure they are not locked or in use.
  Check Dependencies: Investigate if there are any dependencies that prevent the archiving of the objects. Resolve any issues related to these dependencies.
  Configuration Review: Verify the configuration of the archiving object in transaction SARA. Ensure all necessary settings are correctly defined.
  Authorization Check: Ensure that the user executing the archiving job has the necessary authorizations to perform the archiving.
  Log Analysis: Review the logs generated during the archiving process for any additional error messages or warnings that can provide more context.
  Test Archiving: If possible, test the archiving process in a development or quality environment to identify any issues before running it in production.
  
  Related Information:
  
  Transaction SARA: This is the main transaction for managing archiving in SAP. You can use it to configure archiving objects and monitor archiving jobs.
  Archiving Object Documentation: Refer to the documentation for the specific archiving object you are working with to understand its requirements and limitations.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address known issues related to the RECAAR079 error message.
  System Logs: Use transaction SLG1 to check application logs for any related messages that could provide further insights into the issue.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.