How To Fix RSEC652 - Deleted entries not copied

SAP Error Message - Details

• Message type: E = Error

• Message class: RSEC -

• Message number: 652

• Message text: Deleted entries not copied

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 RSEC652 - Deleted entries not copied ?

  The SAP error message RSEC652, which states "Deleted entries not copied," typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with data extraction, transformation, and loading (ETL) processes. This error indicates that there are entries in the source system that have been marked as deleted, and these entries are not being copied to the target system.
  Cause:
  
  Deleted Entries: The primary cause of this error is that the data extraction process is attempting to copy records that have been marked as deleted in the source system. In SAP BW, deleted entries are often not included in the data load to maintain data integrity and consistency.
  Data Source Configuration: The configuration of the data source may not be set up to handle deleted records properly.
  Delta Mechanism: If you are using a delta mechanism for data extraction, it may not be configured to capture deleted records.
  
  Solution:
  
  Check Data Source Settings: Review the settings of the data source in the source system. Ensure that it is configured to handle deleted records appropriately. You may need to adjust the settings to include deleted records if that is required for your reporting needs.
  Delta Load Configuration: If you are using delta loads, ensure that the delta mechanism is correctly set up to capture deletions. This may involve configuring the data source to track changes, including deletions.
  Data Load Process: If you are performing a full load, ensure that the data load process is correctly configured to handle deleted entries. You may need to adjust the extraction logic to include or exclude deleted records based on your requirements.
  Check for Data Integrity: Ensure that the data integrity is maintained in both the source and target systems. If necessary, perform data cleansing or reconciliation to address any discrepancies.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of SAP BW or BI you are using for any additional guidance on handling deleted entries.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Data Warehousing Best Practices: Familiarize yourself with best practices for data warehousing and ETL processes in SAP BW to prevent similar issues in the future.
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP Basis or BW team for further investigation and support.