Configuring Audit:
Step 1 – Set AuditTrail Profile Option:
The System Profile Option AuditTrail:Activate must be set to Yes. Be sure to log out of the applications to activate the profile option in your session.
Step 2 – Select the Audit Installations
??As System Administrator, select Security -> AuditTrail -> Install.
??Check all the schemas for which auditing should be enabled. For example, if you want to audit FND_USERS, you would check APPLSYS since the FND_USERS table is in the APPLSYS schema.
??Save your selections.
Step 3 – Create a New Audit Group
??As System Administrator, select Security -> AuditTrail -> Groups.
??Create a new audit group by setting the Application Name to the application that owns the table (e.g., Application Object Library for APPLSYS),
the Audit Group to a new name (e.g., My Audits), and Group State should be set to Enable Requested.
??Add the tables to be audited. Columns will be defined in the next step.
??Save the new audit group.
Step 4 – Define Table Columns to be Audited
For each table defined in the above step, define the columns to be audited using these steps –
??As System Administrator, select Security -> AuditTrail -> Tables.
??Query the table name.
??The primary key columns will always be saved. Add the columns that need to be audited. Do not ever add the following columns as user information is automatically added –
Creation Date Created By Last Update Login Last Update Date Last Updated By
??Save the columns.
Step 5 – Run AuditTrail Update Program
Run the AuditTrail Update Tables program to activate the auditing. This program will create a shadow table for each audited table and create triggers on each audited column in the original table. The shadow table will have the same name as the audited table appended with “_A”. Two views will be created for each column with the names “_AC#” and “_AV#” where # is a sequential number.
Few key points for Auditing
–Auditing in Apps can be done on Row by Row basis or Individual Column of a table
–If you change any of your definitions for auditing, you must rerun Audit Trail Update Tables
Define Audit Table and Columns
After defining the audit groups and audit installations you can choose the tables and columns for which you wish to enable auditing. You can use the audit tables to do this.
Run the Audit Trail Update Tables Report
You must run a concurrent request Audit Trail Update Tables Report so that your audit trail definitions and the required shadow tables are created. This report is also responsible for building database triggers for your audit installations.
Disabling Auditing
You can disable auditing at anytime by changing the audit group state through the Audit Groups window to either Disable - Interrupt Audit, Disable - Prepare for Archive or Disable - Purge Table. You must run the Audit Trail Update Tables Report after making the selection.
Step 1 – Set AuditTrail Profile Option:
The System Profile Option AuditTrail:Activate must be set to Yes. Be sure to log out of the applications to activate the profile option in your session.
Step 2 – Select the Audit Installations
??As System Administrator, select Security -> AuditTrail -> Install.
??Check all the schemas for which auditing should be enabled. For example, if you want to audit FND_USERS, you would check APPLSYS since the FND_USERS table is in the APPLSYS schema.
??Save your selections.
Step 3 – Create a New Audit Group
??As System Administrator, select Security -> AuditTrail -> Groups.
??Create a new audit group by setting the Application Name to the application that owns the table (e.g., Application Object Library for APPLSYS),
the Audit Group to a new name (e.g., My Audits), and Group State should be set to Enable Requested.
??Add the tables to be audited. Columns will be defined in the next step.
??Save the new audit group.
Step 4 – Define Table Columns to be Audited
For each table defined in the above step, define the columns to be audited using these steps –
??As System Administrator, select Security -> AuditTrail -> Tables.
??Query the table name.
??The primary key columns will always be saved. Add the columns that need to be audited. Do not ever add the following columns as user information is automatically added –
Creation Date Created By Last Update Login Last Update Date Last Updated By
??Save the columns.
Step 5 – Run AuditTrail Update Program
Run the AuditTrail Update Tables program to activate the auditing. This program will create a shadow table for each audited table and create triggers on each audited column in the original table. The shadow table will have the same name as the audited table appended with “_A”. Two views will be created for each column with the names “_AC#” and “_AV#” where # is a sequential number.
Few key points for Auditing
–Auditing in Apps can be done on Row by Row basis or Individual Column of a table
–If you change any of your definitions for auditing, you must rerun Audit Trail Update Tables
Define Audit Table and Columns
After defining the audit groups and audit installations you can choose the tables and columns for which you wish to enable auditing. You can use the audit tables to do this.
Run the Audit Trail Update Tables Report
You must run a concurrent request Audit Trail Update Tables Report so that your audit trail definitions and the required shadow tables are created. This report is also responsible for building database triggers for your audit installations.
Disabling Auditing
You can disable auditing at anytime by changing the audit group state through the Audit Groups window to either Disable - Interrupt Audit, Disable - Prepare for Archive or Disable - Purge Table. You must run the Audit Trail Update Tables Report after making the selection.
No comments:
Post a Comment