audit_cols

The audit_cols file specifies the table columns that are to be audited. You can specify whether a column a) must be logged only when the column’s value has changed or b) must be logged when any other column of the table has changed.

The audit_cols file contains entries of this format:

<Table Name>:<Company Number>:<A/C>[:<Column name list>]

Each entry specifies one or more columns that are to be audited.

The following sections list the meaning of each field.

Table name

This specifies the table names to which this entry applies. These formats are possible:

  • *: Means all tables in all packages.
  • Package: Means all tables in this package, for example, tf, td, and so on
  • Package and module code: All tables in the module, for example, tccom or ttadv
  • Package, module, and table number: For example, ttadv999 or tccom010

Company number

This specifies the company numbers to which this entry applies. These formats are possible:

  • *: All companies.
  • 100: Company 100 only.
  • 100,000: Company 100 and 000.

A/C

This specifies when the column must be logged:

  • A (Always): The column is logged when any audited column in the table has changed.
  • C (when Changed): The column is logged only if the column’s value has changed.

Column name list

This list is a comma-separated list of the column names to which this entry applies. If the <column name list> is omitted, this entry applies to all columns of the table. Otherwise, this entry applies to a column only if the column’s name is in the <column name list>.

Only if the <table name> specifies a full table name, including package, module and table number, a <column name list> can be supplied.

To determine whether a column of a table in a company is audited, the column is matched against every entry. An entry matches if and only if:

  • The table name of the column matches with <table name>.
  • The company matches with <company number>.
  • The name of the column is in <column name list> or <column name list> is omitted.
Note: Multiple matching entries can exist for a column. In case of conflicts, for example, if one entry specifies A for a particular column and another entry specifies C, then A takes precedence over C. In other words, if some entry specifies that a column will be logged always, then no other entry can change this specification to “when changed”.