How To Fix ADS2KIPARCH016 - No records for deletion found in & table

SAP Error Message - Details

• Message type: E = Error

• Message class: ADS2KIPARCH - SPEC2000 Initial Provisioning: Data archiving messages

• Message number: 016

• Message text: No records for deletion found in & table

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 ADS2KIPARCH016 - No records for deletion found in & table ?

  The SAP error message ADS2KIPARCH016 indicates that there are no records available for deletion in the specified table. This error typically occurs during the archiving process when the system attempts to delete records that are supposed to be archived but finds none that meet the criteria.
  Cause:
  
  No Records Available: The most straightforward cause is that there are simply no records in the specified table that meet the criteria for deletion.
  Archiving Object Configuration: The archiving object may not be correctly configured, leading to no records being eligible for deletion.
  Selection Criteria: The selection criteria used for identifying records for deletion may be too restrictive or incorrect.
  Previous Deletion: Records may have already been deleted in a previous archiving run, leaving no records for the current operation.
  
  Solution:
  
  Check Records: Verify if there are indeed records in the specified table that should be eligible for deletion. You can do this by running a query or using transaction codes like SE16 or SE11 to view the table contents.
  Review Archiving Object: Ensure that the archiving object is correctly configured. Check the settings in transaction SARA for the specific archiving object to ensure that it is set up properly.
  Adjust Selection Criteria: If the selection criteria are too restrictive, consider adjusting them to include more records. Review the parameters used in the archiving process.
  Check Previous Runs: Investigate if previous archiving runs have already deleted the records. You can check the archiving logs in transaction SARA to see if the records were processed earlier.
  Consult Documentation: Refer to SAP documentation or notes related to the specific archiving object for any known issues or additional configuration steps that may be required.
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: For managing archiving objects.
  SE16/SE11: For viewing table contents.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Archiving Logs: Review the logs generated during the archiving process for more detailed information about what was processed and any potential issues encountered.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation or to reach out to SAP support for assistance.