Hi,
I have already solved my problem. The solution was to create an implementation of badi /POSDW/CONDITION_PRE where I put my check code.
In the OT_MESSAGE table I fill the MESSAGE_RANGE fields BUSINESSDAYDATE, TRANSINDEXBEGIN and TRANSINDEXEND to identify what transactions are wrong.
Furthermore, I fill the OT_ACTIONRESULT table with an entrie which has the BUSINESSDAYDATE, TRANSIDEX and ACTIONRESULT = '3' (Error). If you fill this table, you will avoid that wrong transactions pass through your Agregation Badi.
Best regards.