Summary

In general, it can be assumed that any action performed by a user such as inserting, editing, updating or deleting records in the PayGlobal entity framework will write an audit log record.

This makes audit logs invaluable for troubleshooting problems that may occur, as you can track who made a change, and when.

Tracking such changes can be done in a number of different ways. These include:

• Using the Audit Analysis tool
• Running the Audit Report (PGPRAUDT001)
• Viewing system generated audit logs.

However not every change is written to an audit log. Certain tables are never audited, because of the way they are declared in PayGlobal's database structure. Many of these tables are 'transaction' tables. Therefore, many processes will not show up in the AuditLog table because of the restrictions on these tables.

Tables not included in Audit Logs

The following list of tables are not included in Audit Logs:

Processes not included

The following process commands do not add records to the Audit Log table:

Tables with Audit Log flag

In some areas, certain tables are created with a flag that disables auditing. These tables are:

• Processing UDA breakdowns:

  No auditing on EmplUDABreakdown, CostCentre, Employee, Job and Position.

• Clock processing:

  No auditing on employee, none of the transaction tables are audited

• P35 Processing (UK):

  No auditing on Employee or P14

• Pay-Close:

  No auditing on CostCentre, EmplLeaveCredit, Employee, EmployeeBenefitsInKind, EmployeeNote, EmployeeYTDNIC, Job and Loan

• End-Of-Year Pay-close:

  No auditing on Employee

• Synchronisation:

  User-setting ('AuditImport') determines whether imports are logged or not.

• Updating UserProfile if wrong password at login:

  No auditing on UserProfile

• Updating bank-branch descriptions:

  No auditing on BankBranch and BankGroup

See also

Audit Analysis

Audit Report (PGPRAUDT001)

Maintain Log Files