Selecting a checkbox in this column creates an audit table for this source code.
When the audit trail history for a source code is enabled, a record is created any time that changes are made in the Transaction Groups window, such as:
· Edit (header or detail)
· Print Edit
· Summarize
· Post
· Delete
· Reverse JE/Batch
An audit trail is also recorded for any scripts that are run directly against a batch in the database.
The audit table creates a record that includes the following information:
· Key columns
· Column name change
o Audit Timestamp and Action (insert/update/delete)
· Before value
· After value
· User
· Job Name
· Job Time
For inserts, a record will be added for any column that has a value (DB default or entered). If it is NULL, then a row will not be created.
For updates, a record will be added for every column that is updated.
For deletes, one record will be added for any column that has a value. Basically, any column that is not null.
New tables created:
AUDIT_TRANS_BATCH_CTL
AUDIT_TRANS_HIST
AUDIT_SOURCE_MASTER
The audit trail history can be accessed and viewed by using SSRS or InfoMaker to create reports using the views listed below:
Name |
Description |
IZ_AUDIT_SOURCE_MASTER_V |
Contains audit trail information for changes made to the source_master |
IZ_AUDIT_TRANS_BATCH_CTL_V |
Contains audit trail information for changes made to the trans_batch_ctl |
IZ_AUDIT_TRANS_HIST_V |
Contains audit trail information for changes made to the trans_hist |
Because a record is created and stored for each field affected by a change, the size of the audit trail history files can quickly inflate, and at some point, could impact application performance. Users should carefully evaluate the advantages and disadvantages when deciding which Source Codes should be tracked.