Results for “fnd_audit_tables”

Key Information Stored

The documented physical schema contains 11 columns. The most significant, together with their roles, are:

• AUDIT_GROUP_ID — Identifier of the audit group to which the table belongs; part of the primary key.
• AUDIT_GROUP_APP_ID — Application identifier qualifying the audit group; part of the primary key and the FK to FND_AUDIT_GROUPS.
• TABLE_APP_ID — Application identifier for the audited table; part of the primary key and the FK to FND_TABLES.
• TABLE_ID — Identifier of the audited table within its application; part of the primary key and the FK to FND_TABLES.
• STATE — Status flag indicating whether the table/group audit association is active or inactive.
• ZD_EDITION_NAME — Editioning column used by the 12.2 online patching architecture to scope rows to an edition.
• CREATION_DATE, CREATED_BY — Standard WHO creation audit columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO update audit columns recording the last change to the row.

The surrogate primary key is FND_AUDIT_TABLES_PK, defined over (AUDIT_GROUP_ID, AUDIT_GROUP_APP_ID, TABLE_APP_ID, TABLE_ID). The documented unique index FND_AUDIT_TABLES_U1 extends these four columns with ZD_EDITION_NAME, representing the business-key candidate (including the edition dimension).

Common Use Cases and Queries

The primary use case is auditing enablement reporting and troubleshooting: identifying which tables are audited under a given group, and whether each association is active.

• List all audited tables in a named audit group, joining to FND_AUDIT_GROUPS for the group name.
• Determine whether a specific application table is currently under audit by filtering on TABLE_APP_ID and TABLE_ID.
• Reconcile physical audit shadow tables against this configuration to detect orphaned or missing audit structures.
• Report inactive (STATE) associations that may indicate disabled auditing.

A representative join pattern is:

SELECT g.AUDIT_GROUP_NAME, t.TABLE_NAME
FROM APPLSYS.FND_AUDIT_TABLES at,
     APPLSYS.FND_AUDIT_GROUPS g,
     APPLSYS.FND_TABLES t
WHERE at.AUDIT_GROUP_ID = g.AUDIT_GROUP_ID
  AND at.AUDIT_GROUP_APP_ID = g.AUDIT_GROUP_APP_ID
  AND at.TABLE_APP_ID = t.APPLICATION_ID
  AND at.TABLE_ID = t.TABLE_ID
  AND at.STATE = 'A';

In 12.2 environments, queries should constrain or account for ZD_EDITION_NAME when editioning is active.

Related Objects

The table participates in two documented foreign-key relationships, with FND_AUDIT_GROUPS and FND_TABLES being the most significant related objects. Additional context objects include the audit column and audit shadow definitions maintained by the AuditTrail/AuditManager utilities, and the FND_TABLES_VIEW reporting view over FND_TABLES.

• FND_AUDIT_GROUPS — parent of AUDIT_GROUP_ID and AUDIT_GROUP_APP_ID; defines the audit group.
• FND_TABLES — parent of TABLE_APP_ID and TABLE_ID; defines the audited application table.
• FND_AUDIT_COLUMNS — column-level audit definitions that parallel the table-level association established here.
• FND_TABLES_VIEW / FND_APPLICATION — supporting views and application lookups for resolving names.

Auditing configuration in EBS is normally maintained through the Oracle Audit Management/Application Object Library concurrent processes and associated audit-trail APIs rather than direct DML against FND_AUDIT_TABLES.