Why there are differences in error table definitions?

Question

Why there are differences in error table definitions?
We are using OWB repository 10.2.0.3.0 and OWB client 10.2.0.3.33. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
I created a error table using DBMS_ERRLOG.CREATE_ERROR_LOG in databse.
Here is the layout.
=========
ORA_ERR_NUMBER$
ORA_ERR_MESG$
ORA_ERR_ROWID$
ORA_ERR_OPTYP$
ORA_ERR_TAG$
PROJECT_ID
DESCRIPTION
PROJECT_TYPE
CREATION_DATE
===========
I imported the table metadata into OWB. As I used the table in mapping using table operator, I am not able to see ERR group in table object of mapping.
How do we bring manually created error table metadata into OWB? Is it feasible?
I specified data rule/shadow table for imported table using object editor. I deployed the table via CC.
Here is the layout from deployed ERROR table from DB
+++++++++++++
ORA_ERR_NUMBER$
ORA_ERR_MESG$
ORA_ERR_ROWID$
ORA_ERR_OPTYP$
ORA_ERR_TAG$
ERR$$$_AUDIT_RUN_ID
ERR$$$_AUDIT_DETAIL_ID
ERR$$$_ERROR_ID
ERR$$$_ERROR_REASON
ERR$$$_SEVERITY
ERR$$$_OPERATOR_NAME
ERR$$$_ERROR_OBJECT_NAME
PROJECT_ID
DESCRIPTION
PROJECT_TYPE
CREATION_DATE
++++++++++++
Why there are differences in error table definitions?
As I used the table in mapping using table operator, I am not able to see ORA_ERR_NUMBER$ , ORA_ERR_MESG$ , ORA_ERR_ROWID$ , ORA_ERR_OPTYP$ , ORA_ERR_TAG$ in ERR group in table object of mapping.
Are there any additional steps/process?
Any idea ?
Thanks in advance.
RI

Answer 1

There are columns for data rule errors (logical errors) and DML errors (physical errors), I think you probably have data rules on the table..?
To process DML errors you will have to add the error table into a map you may have to reverse engineer it). The error group behavior is only available for processing errors from tables with data rules. Ensure your table operator is synchronized with your design table.
http://blogs.oracle.com/warehousebuilder/newsItems/viewFullItem$184
Cheers
David