Search Results fnd_audit_groups




Overview
Explore in AI Chat

Overview

The FND_AUDIT_GROUPS table is a core repository within the Application Object Library (FND) of Oracle E-Business Suite (EBS) that defines logical collections of database objects for auditing purposes. It serves as the master definition table for audit groups, enabling administrators to centrally manage and apply audit policies to multiple tables and columns as a single unit. Its primary role is to streamline the configuration and maintenance of data auditing by associating specific application tables, via related objects, with a defined group identifier. This foundational structure is critical for implementing and tracking fine-grained data security and compliance logging across the EBS application modules.

Key Information Stored

The table stores the essential metadata that defines an audit group. Its structure is anchored by a composite primary key consisting of APPLICATION_ID and AUDIT_GROUP_ID. The APPLICATION_ID ties the group to a specific EBS application, such as General Ledger (SQLGL) or Payables (SQLAP), ensuring context within the modular architecture. The AUDIT_GROUP_ID is the unique identifier for the audit group within that application, a key field for developers and administrators when querying or configuring audit settings. While the provided ETRM metadata does not list all columns, typical supporting columns would include data such as the group's name, creation date, and enabled status, which collectively describe the audit group's properties and lifecycle.

Common Use Cases and Queries

A primary use case is investigating or reporting on the configured audit groups within the system. For instance, an auditor or developer needing to identify all audit groups defined for the General Ledger application might execute a query filtering on APPLICATION_ID. The most direct query pattern involves joining FND_AUDIT_GROUPS with its related child table, FND_AUDIT_TABLES, to list all tables assigned to a specific audit group. A sample SQL pattern is:

  • SELECT ag.application_id, ag.audit_group_id, at.table_name FROM apps.fnd_audit_groups ag, apps.fnd_audit_tables at WHERE ag.application_id = at.audit_group_app_id AND ag.audit_group_id = at.audit_group_id AND ag.audit_group_id = :group_id;

This is essential for validating audit scope, troubleshooting missing audit trails, or documenting security configurations during compliance reviews.

Related Objects

FND_AUDIT_GROUPS has a direct parent-child relationship with the FND_AUDIT_TABLES table, as defined by the documented foreign key. FND_AUDIT_TABLES references FND_AUDIT_GROUPS via the composite foreign key columns AUDIT_GROUP_APP_ID (mapping to APPLICATION_ID) and AUDIT_GROUP_ID. This relationship means that an audit group defined in FND_AUDIT_GROUPS can contain multiple table definitions from FND_AUDIT_TABLES. The audit framework likely involves other related objects such as FND_AUDIT_COLUMNS (for column-level auditing within tables) and FND_AUDIT_SCHEMAS, forming a hierarchy where FND_AUDIT_GROUPS acts as a central organizing entity. All these objects are part of the FND (Application Object Library) product family.