How To Fix RSDA228 - Simulation of selective deletion returns different number of data records

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 228

• Message text: Simulation of selective deletion returns different number of data records

What causes this issue?

When simulating the selective deletion, the number of data records that
were archived was found to differ from the number of data records that
were deleted with the current deletion condition:
A total of &v1& data records was archived, but the current deletion
condition deleted &v2& data records from the InfoProvider &v3& .

System Response

The selective deletion was not executed.

How to fix this error?

If there is more than one open archivation request for the data
archiving process &v4& , you can try to delete all open archivation
requests together or change the order of the deletion phases for the
individual requests.
For further information on causes, error analysis and troubleshooting,
see SAP Note 1233601.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDA228 - Simulation of selective deletion returns different number of data records ?

  The SAP error message RSDA228 indicates that there is a discrepancy in the number of data records when simulating a selective deletion in a DataStore Object (DSO) or InfoProvider. This error typically arises during the process of data management in SAP BW (Business Warehouse) when the system attempts to simulate the deletion of certain records based on specified criteria.
  Cause:
  The error can occur due to several reasons, including:
  
  Inconsistent Data: The data in the DSO may have changed since the last time the simulation was run, leading to a mismatch in the expected number of records.
  Selection Criteria: The selection criteria used for the simulation may not match the actual data, resulting in a different number of records being identified for deletion.
  Data Locks: Other processes or users may be locking the data, causing inconsistencies during the simulation.
  Data Aggregation: If the data is aggregated or if there are multiple records that meet the criteria, the simulation may yield a different count than expected.
  Technical Issues: There may be underlying technical issues or bugs in the SAP BW system that affect the simulation process.
  
  Solution:
  To resolve the RSDA228 error, you can take the following steps:
  
  Check Selection Criteria: Review the selection criteria used for the simulation to ensure they accurately reflect the records you intend to delete.
  Data Consistency: Verify the consistency of the data in the DSO. You may need to run consistency checks or data repair processes if inconsistencies are found.
  Refresh Data: If the data has changed, refresh the data in the DSO and re-run the simulation to see if the issue persists.
  Check for Locks: Investigate if there are any locks on the data that could be causing the discrepancy. You can use transaction codes like SM12 to check for locks.
  Review Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Test in a Development Environment: If possible, replicate the issue in a development or test environment to further analyze the problem without affecting production data.
  Consult SAP Notes: Look for relevant SAP Notes or updates that may address known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), SLG1 (Application Log), and SM12 (Lock Entries).
  SAP BW Documentation: Review SAP BW documentation for best practices on data management and selective deletion processes.
  SAP Community: Engage with the SAP Community or forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.