OneData 10.7 | Managing Master Data with webMethods OneData | Administering webMethods OneData | Working with Metadata | Audit Columns and Triggers
 
Audit Columns and Triggers
Audit columns and triggers are automatically added to objects the first time they are imported into OneData. When database changes are made in source system, like re-creating the table for changing column order after the object has been brought into OneData, these columns or triggers may be dropped. Therefore, after these actions are performed, it is important to verify that the audit columns and triggers exist as described in the table below.
Every table and view represented as a OneData object must have audit columns and triggers. For tables, OneData automatically creates both audit columns and triggers when the table is created or imported into OneData. For logical objects, such as views, OneData does not define triggers or columns. Therefore, you must manually create audit columns in the source before importing the view into OneData.
The following audit columns must exist in all tables and views in both the staging area and the production data.
Column Name
Datatype
Nullable
Default Value
Definition
CREAT_DT
date
No
Sysdate
Date/time of record creation
LST_UPD_DT
date
No
Sysdate
Date/time of last update
CREAT_USR_ID
varchar2(50)
No
User
User who created the record.
LST_UPD_USR_ID
varchar2(50)
No
User
User who last updated the record.
LST_DEL_DT
date
Yes
Date/time record was logically deleted.
S2P_TRN_DT
date
Yes
Date/time of record transfer to Release Area
FLD_DELETE
number(1)
No
0
Logical delete indicator