Audit - General remarks (CE)

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 appropriate 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.