Auditing loads?

Question

I've already looked at OWB's Runtime Audit Browser and I like it. But my auditing needs are different.
First let me explain, what I know and have already.
I'm executing OWB mappings with OEM jobs. To do this, I use the oem_exec_template.sql script provided with OWB. This script stores an audit_id in the variable l_audit_id. I need to put exactly this audit_id into the table(s) that where created/loaded by a mapping.
I could modify this oem_exec_template.sql script, so that after the load finished, I update all rows with this audit_id.
The problem is, that this is going to be too slow. I tried this with a small table with ~7 million rows and it delayed the overall execution time very much.
Is there a "correct and well performing" way to do this? Or I'm thinking way to complicated, maybe there is a nice solution.
Maybe you ask: why do I need this?
The tables are loaded once a day, and we must be able to tell exactly:
1) which rows were loaded
2) when where they loaded
3) any problem during this load (-> with the audit id, it is easy to find it in the OWB Audit Browser again)

Answer 1

01) I added an external table.
02) I linked all field from the ext_table to the target table.
03) In the target table I created an attribute AUDIT_ID and reconcile outbound.
04) The I added an expression.
05) In the expression's outgroup I added an attribute AUDIT_ID.
06) On (expression) AUDIT_ID, right-click -> expression
07) I entered M_MAP02.get_audit_id (since my mapping is M_MAP02)
08) I created an input field dummy.
09) I created a constant with the expression 1, which is linked to the expression.dummy input field.
10) I validated the mapping and it was okay.
11) I registered every LOCATION that was missing
Validation and deployment were successful.
Did I do everything right?
No! When I execute the mapping from the deployment manager, 0 rows get loaded :(
No. Now I get a "funny" error, that really starts getting to me:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-29400: data cartridge error KUP-00554: error encountered while parsing access parameters KUP-01006: error signalled during parse of access parameters KUP-00562: unknown escape sequence.
What is going wrong? I used the same flatfile definition that I used for the previous SQLLoader mappings. The file description must be correct, nothing changed.
I do however believe, that this error is still on my side, but I already hear my project leader telling me, that sticking with MS DTS packages would have been better, at least when it comes to usability of the product. None the less, OWB is the ETL tool for Oracle DBs, so there must be a way to take advantage of this tool...... (it is just boring, to do trial&error)