Unable to abort from a mapping

Question

Hi All,
We need to abort processing within our mapping upon meeting a certain condition. We have tried WB_ABORT and functions with RAISE_APPLICATION_ERROR. But the mapping runs to completion with errors and inserts all other rows into the target table. The mapping doesn't abort, but the audit records do show the error message raised in the above function.
The abort is necessary at the row where the error occurs, so the mapping can be re-run from that point after fixing the problem.
The mappings use sorter and expression operators and a splitter and run in row-based mode with bulk-processing set to false.
Any input is highly appreciated.
Thanks,
Aravind

Answer 1

Nikolai,
Thanks for the tip. Regarding the same problem.. Max. no. of errors is set to 1. The errors are not database related.
For Eg: Assume there are 10 rows in the source table. If the 5th row doesn't meet a particular condition, we want the mapping to abort at this stage. So we use a splitter to identify this row and call a function to raise an error. We see the error in the audit log, but rows 6 to 10 get processed as well and end up in the target table.
We tried this in a simple mapping. The mapping aborts at row 5.
source-> splitter -> target/error function.
Mapping completion status - Completed with errors.
Next we tried using this logic in our mapping, it doesn't abort.
source-> filter -> expression/functions-->sorter-->expression/function --> splitter --> target/error function.
Mapping completion status - Completed with warnings.
Why didn't it error out here?
Thanks,
Chethan