FAT Audit Files

Field Audit Trail (FAT) creates an audit file to contain the captured data for each file being audited. The format of this audit file is composed of the audited fields and some extra tracking information. To capture and store data modifications, a database trigger is created for every monitored file. Audit files can grow large over time. Splitting audit files into smaller parts, known as partitions, solves this problem. You can remove partitions manually if the history data is no longer necessary. Since FAT can affect performance of M3 BE transactions negatively, you must be aware of what selections you have made. Only audit fields that you have a proven need to audit.