Creating Audit Triggers and Running Trigger Scripts

This section discusses how to:

Create audit triggers.
Create and run trigger scripts.

Pages Used to Create Audit Triggers and Run Trigger Scripts

Page Name	Definition Name	Navigation	Usage
Audit Triggers	TRIGAUDPNL	PeopleTools, Utilities, Audit, Update Database Level Auditing, Audit Triggers	Create audit triggers and trigger statements.
Run Audtrgs (Run Audit Triggers)	RUN_AUDTRGS	PeopleTools, Utilities, Audit, Perform Database Level Audit, Run Audtrgs (Run Audit Triggers)	Run trigger scripts.

Audit Triggers Page

Use the Audit Triggers page (TRIGAUDPNL) to create audit triggers and trigger statements.

Navigation

PeopleTools, Utilities, Audit, Update Database Level Auditing, Audit Triggers

Image: Audit Triggers page

This example illustrates the fields and controls on the Audit Triggers page. You can find definitions for the fields and controls later on this page.

Record (Table) Name

Displays the base table you selected and intend to associate with an audit table.

Audit Record Name

Select an audit table you want to associate with the base table.

You must specify an audit table before you can create a trigger.

Trigger Name

Displays the name of the audit trigger.

The system automatically names the audit trigger using the following naming convention: [base record name]_TR.

Create Trigger Statement

Displays the trigger statement (code).

The code is automatically populated when you click Generate Code.

You can edit the script as needed.

Generate Code

Click this button to generate the SQL that creates the trigger.

Clicking this button also populates the Create Trigger Statement field with the trigger statement (code).

Audit Options

Add

Select this option if you want the audit table to track newly added records.

Change

Select this option if you want the audit table to track changed records.

Delete

Select this option if you want the audit table to track deleted records.

After you create your trigger statements, you can create and run the trigger script against the database to physically create the triggers. See the following section for more information.

Run Audit Triggers

Use the Run Audtrgs (Run Audit Triggers) page (RUN_AUDTRGS) to run trigger scripts.

Navigation

PeopleTools, Utilities, Audit, Perform Database Level Audit, Run Audtrgs (Run Audit Triggers)

Image: Run Audtrgs (Run Audit Triggers) page

This example illustrates the fields and controls on the Run Audtrgs (Run Audit Triggers) page . You can find definitions for the fields and controls later on this page.

Create All Triggers

Select this check box if you want all the triggers you defined in the Trigger Definition (PSTRIGGERDEFN) table included in the script.

The application engine writes a 'create trigger' statement to a file for every row in the Trigger Definition table.

Create Triggers On

Specify the table for which the trigger statement should be created.

Run

Click to run the trigger script.

This process writes a 'create trigger' statement to a file for the triggers you specified. The system writes the file to the location that is determined by the run location of the process. If it is run on the server, the file is created in the PS_SRVRDIR directory. If it is run on a Windows workstation, the file is created in the directory that the %TEMP% environment variable specifies. The file name is TRGCODEX.SQL, where X represents a digit that is determined by the number of files by the same name that already exist in the output directory.

Note: After you create the SQL script, use a SQL utility to run the script against the database. If you encounter an issue while running SQL due to OPRID, then OPRID (V_AUDIT_OPRID) generated from the script can be hardcoded with the username used for sign on.