Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Configure Ebs Audit Trail

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7

HOW TO CONFIGURE E-BUSINESS SUITE AUDITTRAIL

Step 1 – Set AuditTrail Profile Option


The System Profile Option AuditTrail:Activate must be set to Yes. The default value for
AuditTrail:Activate is null (which equals No).

Be sure to log out of the applications to activate the profile option in your session.

2- Define Audit Installations

As System Administrator, select Security -> AuditTrail -> Install.

Select the registered Oracle user names at your site that you wish to audit.

Select the Audit Enabled check box to enable Audit Trail for an Oracle user name.

In this example our table PER_ABSENCE_ATTENDANCES belongs to HR, Hence search for HR and
tick the checkbox 'Audit Enabled'.
Also enable audit for APPS & APPLSYS

Step 3 – Create a New Audit Group


You can audit a table or Oracle ID by defining an audit group, which can consist of one
or more tables.
To create an Audit Group and assign specific tables and columns, perform the following:
1. Navigate to Security > Audit Trail > Groups to create audit groups and set
tables to be audited. Set audit group to Enabled Requested.
2. Identify the tables you want to audit or tables owned by an Oracle ID selected for
auditing in the previous step, "Define Audit Installations". See “Tables to Audit
with Audit Trail” for a list of recommended tables to consider auditing.
3. 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.

Important: All primary key columns in each table in an audit group are automatically
selected for auditing, whether or not you use the Audit Tables window to select which
columns you wish to audit.

Step 4 – Define Table Columns to be Audited

1. As System Administrator, select Security -> AuditTrail -> Tables.


2. Query the table name.
3. 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
4.
5. Save the columns.

Step 5 – Run AuditTrail Update Program


Your Audit Trail definitions (and auditing) do not go into effect until you run the
AuditTrail Update Tables Report.
If you change any of your definitions later, you must rerun this program.
Submit the “AuditTrail Update Tables” concurrent request from the standard
submission (Submit Reports) form.
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.
Note:
If while running AuditTrail Update Tables concurrent request it’s completed with the
following error occurs: Fatal error in fdasql, quitting... Fatal error in fdacv, quitting...,
Fatal error in fdaupc, quitting... (Doc ID 2018647.1)
Please execute the following steps:

  To fix the issue Check if you have enabled auditing for APPLSYS,APPS and the
application schema owner you want to audit, if not enable the auditing for the schema
you wish to audit.

1. Go into the responsibility: System Administrator


2. Navigate to MENUPATH >Security > Audit Trail > Groups (Audit Groups window).

3. Query the audit group SQLAP.AP_SYSTEM_PARAMETERS_ALL.

4. Set the group state of SQLAP.AP_SYSTEM_PARAMETERS_ALL from "Enable Requested" to


"Disable - Purge Table"

5. Save

6. Run the concurrent program "AuditTrail Update Tables"

7. Take backup of the following table "FND_AUDIT_COLUMNS" as the following script:


Create table FND_AUDIT_COLUMNS_BKP as select * from FND_AUDIT_COLUMNS where
table_id=(select table_id from FND_AUDIT_TABLES
where audit_group_id=(select audit_group_id from FND_AUDIT_GROUPS where
group_name='SQLAP.AP_SYSTEM_PARAMETERS_ALL'))

8. Delete columns from table:


delete from FND_AUDIT_COLUMNS where TABLE_ID = =(select table_id from
FND_AUDIT_TABLES
where audit_group_id=(select audit_group_id from FND_AUDIT_GROUPS where
group_name='SQLAP.AP_SYSTEM_PARAMETERS_ALL'));

9. Commit;
Step 6 – Setup Purge
The AuditTrail data should be purged on a periodic basis. There is no standard purge
program and the AuditTrail must be manually disabled to permit purging.
Use the following procedure to purge audit date –
1. As System Administrator, select Security -> AuditTrail -> Groups and select the
“Security Audit” group and then set the state of the group to be purged to a value of
“Disable – Purge Table”
2. Run the “Audit Trail Update Tables” Report
3. Purge the data from the shadow table
4. Select Security -> AuditTrail -> Groups
5. Select the “Security Audit” group and set the group state to “Enable”
6. Run the “Audit Trail Update Tables” Report

You might also like