- OracleApps Epicenter - http://www.oracleappshub.com -
Are you seeking auditing ability in EBS…use ‘AuditTrail’
Posted By Sanjit Anand On May 15, 2008 @ 1:48 pm In AOL,EBS Suite,Oracle Application,Tool | 1 Comment
What is an AuditTrail?
An AuditTrail is one of functionality for retaining a history of changes to data. What ,who and when can be identified on a particular table or column if the functionality is enabled.
When you enter or update data in your forms, you change the database tables underlying those forms. An audit trail tracks which row in the database was updated at what time, and which user was logged in using the associated form(s).
If you are seeking auditing ability to track changes on a particular table of Oracle this post might helpful to you.
Enabling the Functionality of AuditTrail
You can turn AuditTrail on or off (Yes or No). Normally the default setting is No (Off). When you enter or update data in your forms, you change the database tables underlying the forms you see and use. AuditTrail tracks which rows in a database table(s) were updated at what time and which user was logged in using the form(s). Also..
The internal name for this profile option is AUDITTRAIL:ACTIVATE.
Setting Up AuditTrail(>11i )
You can choose to store and retrieve a history of all changes users make on a given table. Auditing is accomplished using audit groups, which functionally group tables to be audited. For a table to be audited, it must be included in an enabled audit group.
The steps for setting up AuditTrail include:
Yuu need to verify Select Privileges on SYS.DBA_TABLES
Have your database administrator grant SELECT privileges on SYS.DBA_TABLES to the APPLSYS account. Normally, this step would Normally taken care during the installation of Oracle.
Define Audit Groups
This is very very important.These are groups of tables and columns, where you do not necessarily need to include all the columns in a given table. You enable auditing for audit groups rather than for individual tables. You would typically group together those tables that belong to the same business process (for example, purchase order tables see at the end).
A given table can belong to more than one audit group. If so, the table is audited according to the highest "state" of enabling for any of its groups, where Enabled is the highest, followed by Disable Dump Data, Disable No Growth, and Disable Purge Table, in that order.
Navigation: Security -> AuditTrail -> Groups
Define Audit Installations
You choose the registered Oracle IDs at your site that you want to audit. This allows you to audit across multiple application installations. When a table is added to an audit group, auditing will automatically be enabled for all installations of the table for which audit is enabled.
Navigation: Security -> AuditTrail -> Install
Run the Audit Trail Update Tables Report to Enable Auditing
Your AuditTrail definitions (and auditing) do not take effect until you run the Audit Trail Update Tables Report. If you change any of your definitions later, you must rerun this program. You run the Audit Trail Update Tables Report from the standard submission (Submit Reports) form.
Audit Trail Update Tables Report
This program creates database triggers on the tables in your audit groups for your installations. It also creates shadow tables, one for each audited table, to contain the audit information. If you have changed your audit definitions or disabled auditing for an audit group, the program drops or modifies the auditing triggers and shadow tables appropriately.
The program also builds special views you can use to retrieve your audit data for reporting.
You can check SQL*Plus to see if the Shadow Tables have been created or not. Shadow Table name is the same 26 Characters of the Table being audited followed by a suffix of "_A" ,suffix of "_AI" for Insert Triggers, "_AU" for Update triggers , "_AD" for Delete Triggers,suffix of "_AIP" for Insert Procedures "_AUP" for Update Procedures and "_ADP" for Delete Procedures.
These are limitation of AuditTrail:
Sometime back we found while enabling this on these tables.
What are the primary Auditing Tables?
Client Dilema : HOW TO ENABLE AUDITING AT "FORMS" AND "USER" LEVEL TOGETHER
Customer has set the profile "Sign-on: Audit Level" to FORMS to collect information about the forms sessions at a particular time .
By default the value for this profile was USER. Since he has set the value to Forms can he collect the User related information
Yes you can ...
If the profile "Sign-on: Audit Level" is set to FORMS then it will collect Form sessions information in addition to user session information.
So you will get information related to User session as well as forms session. There is no harm in setting this profile value to FORMS.
Article printed from OracleApps Epicenter: http://www.oracleappshub.com
URL to article: http://www.oracleappshub.com/oracle-application/are-seeking-auditing-ability-in-ebsuse-audittrail/
Disclaimer The opinions expressed here represent solely my own represent personal conjecture based upon experience, practice and observation and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients. Copyright © 2007-2010 OracleApps Epicenter. All rights reserved.