| Audit - General remarks |  |
| The commands that cause a table transaction to be audited, are only the commands that affect the table data, that is, Insert, Update, and Delete commands. Several table level commands that affect all rows in a table are also audited, such as Create Table, Drop Table, and Clear Table. The audit configuration uses a positive approach, which means that you can only define the tables and fields that must be audited, but not the tables and fields that must not be audited. To compensate for this feature, you can load lists of all packages, modules, tables or fields through the Specific menu of the sessions concerned. Because you can use tables and fields in various profiles with conflicting settings, the following rules determine which setting take precedence over the conflicting setting: A higher level takes precedence over a lower level. Therefore, if you define in profile A that all tables in a module must be audited, but in profile B that only one table in this module must be audited, the result, if you convert these profiles to run time, is that all modules in the package concerned are audited. The setting Always takes precedence over Changed. Therefore, if profile A defines that a field must only be audited, when the profile is changed, and profile B defines that this field must always be audited, the field is always audited. The following tables illustrate this behavior.
Result of conflicting audit type settings
Package | Module | Table | Audit Type
--- | --- | --- | ---
tt | adv | * | Always
tt | adv | 200 | Changed
Result
tt | adv | * | Always
Result of conflicting audit type settings
Package | Module | Table | Audit Type
--- | --- | --- | ---
tt | adv | * | Changed
tt | adv | 200 | Always
Result
tt | adv | * | Changed
tt | adv | 200 | Always
If company groups are also added to a profile, the result of the convert to run time action on these profiles is determined by these company groups also, as illustrated in the following table.
Result of conflicting audit type settings
Package | Module | Table | Company | Audit Type
--- | --- | --- | --- | ---
tt | * | * | 001, 002 | Changed
tt | adv | * | 002, 003 | Always
tt | adv | 200 | 002, 004 | Changed
Result
tt | * | * | 001, 002 | Changed
tt | adv | * | 002, 003 | Always
tt | adv | 200 | 004 | Changed
The following table displays the same information, but now by company, and only for table ttadv200.
Possible combinations of audit type and field specification
Companies | Audit Type | Comment
--- | --- | ---
001 | Changed | 2
002, 003 | Always | 4
004 | Changed |
005 | - | For other companies, table ttadv200 is not audited.
You can configure audit settings for tables in another package combination. However, you cannot zoom to these tables. You must enter these tables manually. If you convert the audit configuration to run time, the result is stored in the following four files, which you can find in the `$BSE\lib` directory: `audit_spec` `audit_cols` `audit_hosts` `auditdef6.2` |