To enable Oracle E-Business Suite Audit Trail, review and perform the following steps as required:

1. Granted required privileges.

   Have your database administrator grant SELECT privileges on SYS.DBA_TABLES to the APPLSYS account. Normally, this step will already have been done as part of the installation or upgrade.

2. Register custom tables and primary keys.

   Your tables and their primary key information must already be registered and defined for successful auditing. If the table you want to audit is a custom table (not shipped as part of Oracle E-Business Suite), you should also perform the following two steps:

   1. Register your table and its primary key columns using Oracle Application Object Library's Tables window (Application Developer Responsibility).

   2. Run the Register Tables concurrent program from the Submit Requests window.

3. Turn on Audit Trail.

   Turn on Oracle E-Business Suite Applications Audit Trail by setting the system profile Audit Trail: Activate to True

4. Define Audit Installations (optional).

   You may optionally choose to audit by a registered Oracle ID. 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.

   Before you proceed, ensure that the desired Oracle username is registered. The installation process automatically registers Oracle E-Business Suite Oracle user names, but if you create a custom application, you should follow instructions in My Oracle Support Knowledge Document 1577707.1, Creating a Custom Application in Oracle E-Business Suite Release 12.2, for Oracle user names for custom applications.

   To audit by a registered Oracle ID, do the following:

   Navigate through Security > Audit Trail > Install and 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.

   For auditing to take effect, you must perform the next steps in this section.

5. Define Audit Groups.

   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.

      • Audit Groups block - Identify your audit group and enable or disable auditing for this group.

      • Application Name - Select the name of an application to associate with your audit group. The combination of application name and group name uniquely identifies your audit group. An audit group may be used to audit tables in additional applications.

      • Audit Group - Enter the name of the audit group.

      • Group State - Choose Enable Requested if you are defining a new audit group. When you run the Audit Trail Update Tables report, the concurrent program creates database triggers for the tables in your audit group. Once you have run the program, this field displays Enabled for audit groups where Audit Trail is active.

   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.

6. Active Audit Trail.

   Your Audit Trail definitions (and auditing) do not go into effect until you run the Audit Trail Update Tables Report. If you change any of your definitions later, you must rerun this program. Submit the Audit Trail Update Tables concurrent request from the standard submission (Submit Reports) form.