SAP Netweaver Business Intelligence BI / BW

Symptom

The delete phase of an archiving request terminates with message RSDA 228 “Simulation of selective deletion returns different number of data records”.

Other terms

Archiving, package RSDA, transaction RSDAP, transaction
RSA1, data archiving process (DAP), RSDA 228, RSDA228
Reason and Prerequisites

The problem is caused by a program error.
This problem occurs only if all the following prerequisites apply:
You use a data archiving process to archive data from an InfoCube.At the beginning of the copy phase of the archiving request, the InfoCube contains at least one request that is not yet visible for reporting (for example, a request for which roll up has not yet been carried out if aggregates or an SAP NetWeaver BI Accelerator (BWA) index exists).The request that is not yet visible for reporting in the InfoCube contains at least one data record that fulfills the selection condition of the archiving request.The request is loaded into the InfoCube before the archiving request receives the status “30″ (Data Area of the Request is Locked Against Changes).The terminated archiving request has the request status “50″ (Verification Phase Ended Successfully).

Solution

If the prerequisites of this note do not apply, the situation described in Note 1233601 may also be the cause of the problem.
Preventative solution:
Start an archiving request for copying data to the archive or a near-line storage only
If you are sure that the InfoCube in requests that are not yet visible for reporting do not contain any data records that fulfill the selection condition of the archiving request, orIf all requests in the InfoCube are visible for reporting.

Reactive solution:
If the archiving request still terminates with message RSDA 228, first check whether the situation described under “Reason and Prerequisites” applies. If it does, proceed as follows:
Decide whether the data in the request that is not yet visible is still required in the InfoCube.If it is not (for example, if the request was loaded by accident), to correct the problem, it is sufficient to delete the relevant request from the InfoCube and then repeat the delete phase of the archiving request.If the data is still required in the InfoCube, first invalidate the terminated archiving request.Then ensure that the relevant requests are visible for reporting by carrying out roll up in the aggregate, for example.Create a new archiving request with the same selection conditions and execute it.