Record filtered in advance as error records with the same key exist RSM2
Need your guidance to get rid of the following issue that I am facing. Appreciate your early help and response on this. Scenario is:
We have a DSO (level 1, write optimized) and transferring transaction data to another standard DSO via DTP. For some of the transaction data we do not have master data set up(which is be going to set up in near future, not an issue right now) and that is why couple of records ending up as error requests in error stack upon every transaction data load in a day.
Earlier whenever I used to run the Error DTP after a week time interval, all the error requests present in error stack were used to convert into a single common consolidated error request. Now, what is happening is that, upon execution of Error DTP pertaining to this standard DSO, load is ending up with a red status.
For first occurrence of record with particular semantic key in error request, error description is that no master data maintained for the related data, BUT, for all the following occurrences of records with same semantic key, in same error request, error description is:
u201CRecord filtered in advance as error records with the same key exist RSM2 722u201D
The data record was filtered out because data records with the same key have already been filtered out in the current step for other reasons and the current update is non-commutative (for example, MOVE). This means that data records cannot be exchanged on the basis of the semantic key.
The data record is filtered out; further processing is performed in accordance with the settings chosen for error handling.
Check these data records and data records with the same key for errors and then update them.
Could you please suggest a solution to get rid of the above mentioned error? Awaiting your reply.