Search Results audit_table

Overview

GMA_AUDIT_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, associated with the Process Manufacturing (GMA) product family. It supports the Oracle EBS audit-trail framework by assembling the metadata necessary to display and report on audit results for audited tables registered in the FND_AUDIT_GROUPS and FND_AUDIT_TABLES repository. The package is classified as OTHER, indicating it is an internal utility package rather than a published public API, and it is not referenced by any other documented package within the ETRM inventory.

The package operates against the standard EBS audit infrastructure. It resolves which physical audited ("shadow") tables exist for a given audit template, gathers the display columns and primary key columns required to render audit records in a meaningful form, and populates a reporting structure that downstream audit inquiry forms and reports consume. Because the package relies on dynamic SQL and REF CURSORs, its behavior is driven at runtime by the audit group, template, and where-clause criteria supplied by the calling component.

Key Procedures and Functions

• RETRIEVE_RESULT_TABLES — The central procedure of the package. It accepts an audit where-clause and a table where-clause and returns, through an IN OUT parameter of type AUDIT_REQUIRED_TABLES_TYPE, the set of audited tables that satisfy the criteria. Internally it declares two REF CURSOR variables (RETRIEVE_DATA) named AUDIT_TABLE and TABLE_DATA, plus VARCHAR2 buffers for the generated SQL statements. It builds a query joining FND_AUDIT_GROUPS, GMA_AUDIT_TMPLT_DTL, FND_AUDIT_TABLES, and FND_TABLES, filtered on the audit template's group and application identifiers and restricted to audit groups and audit tables in state E, G, or N. For each returned table, the procedure issues a secondary lookup against the TAB data dictionary view to confirm that a corresponding shadow table exists, testing the table name against the pattern formed by truncating the table name to 26 bytes and appending the suffix "_AC1". Confirmed tables are then loaded into the output collection with their table name, user-facing table name, and table identifier. The procedure therefore serves as the discovery and qualification stage of the audit reporting pipeline.
• POPULATE_TAB_REP_DATA — Companion procedure responsible for populating the audit report detail data used by the audit reporting screens. Its exact parameter list is not exposed in the available metadata, but its documented role is to write into the GMA_AUDIT_REP_DTL structure the row-level audit content required for display, drawing on the column specifications defined in GMA_AUDIT_DISP_COLS and the key definitions in FND_PRIMARY_KEYS and FND_PRIMARY_KEY_COLUMNS.

Tables Accessed

The package reads from the following documented objects:

• FND_AUDIT_GROUPS — Registry of audit groups; provides audit group and application identifiers used to scope the template join and to restrict processing to active states.
• GMA_AUDIT_TMPLT_DTL — The GMA audit template detail table that links an audit template to its audit group and application, defining which tables a template audits.
• FND_AUDIT_TABLES — The audited-table registry, resolving audit group to the physical tables included in the audit and their application identifiers and states.
• FND_COLUMNS — Column metadata used to resolve displayable columns for each audited table.
• FND_PRIMARY_KEYS and FND_PRIMARY_KEY_COLUMNS — Primary key definitions and their constituent columns, used to build the identifying key values for audit records.
• GMA_AUDIT_DISP_COLS — GMA-specific configuration of which columns are presented in audit output.
• GMA_AUDIT_REP_DTL — The report detail table populated by POPULATE_TAB_REP_DATA.
• TAB — The Oracle data dictionary view queried to confirm the existence of the "_AC1" shadow table for each candidate audited table.

Usage Notes

GMA_AUDIT_PKG is invoked indirectly by the audit inquiry and audit reporting user interfaces within Process Manufacturing, and by concurrent or custom programs that need to enumerate audited tables and materialize audit result data for presentation. Because RETRIEVE_RESULT_TABLES accepts caller-supplied where-clause fragments, it is typically called with predicates supplied by the form or report to narrow the audit population by template, group, or business entity. The package is not a documented public API and carries no cross-package references within the ETRM inventory, so customizations should treat it as an internal implementation detail. Any extension of audit reporting should prefer the supported audit configuration tables and the standard FND audit inquiry components rather than calling this package directly, and the header revision (115.2) indicates a stable, long-standing implementation carried forward into 12.1.1 and 12.2.2 without functional change.