Audit - General remarks

The commands that cause a table transaction to be audited, are only the commands that affect the table data. That is, the 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. It means that you can only define the tables and fields that must be audited. You cannot define 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 concerned sessions.

Because you can use tables and fields in various profiles with conflicting settings. These rules determine which setting takes precedence over the conflicting setting:

  • A higher level takes precedence over a lower level. When you define a profile A that audits all tables in a module and a profile B that only audits one table in this module. The result is that if you convert these profiles to run time, that all modules in the package that are concerned are audited.
  • The setting Always takes precedence over Changed. For example, profile A defines that a field must only be audited when the profile is changed. Profile B defines that this field must always be audited. Then the field is always audited.

These two tables show the result of conflicting audit type settings:

Package Module Table Audit Type
tt adv * Always
tt adv 200 Changed
tt adv * Always
Package Module Table Audit Type
tt adv * Changed
tt adv 200 Always
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.

This table shows that 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
tt * * 001, 002 Changed
tt adv * 002, 003 Always
tt adv 200 004 Changed

Several combinations of audit type and field specification are possible. This table shows the same information, but now by company, and only for table ttadv200:

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. 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 these four files, which you can find in the $BSE\lib directory:

  • audit_spec
  • audit_cols
  • audit_hosts
  • auditdef6.2