Search Results xtr_audit_columns_pk

Overview

XTR_AUDIT_COLUMNS is a Treasury (XTR) module configuration table in Oracle E-Business Suite, originally created by Oracle on 27-MAY-96 and retained as a valid object in both release 12.1.1 and 12.2.2. The table functions as a metadata registry that governs which columns of which Treasury-related tables are subjected to auditing, and how those columns are presented to the audit and reporting layer. Rather than storing transactional treasury data itself, XTR_AUDIT_COLUMNS stores the definitions that control audit behavior for other objects in the XTR schema.

The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table participates in no documented parent/child foreign-key relationships and behaves as an independent reference or configuration entity. Under a Data Vault modeling suggestion, it is best treated as a standalone reference table rather than a hub, link, or satellite, since it holds descriptive configuration rows keyed by composite business attributes rather than by a surrogate warehouse key with dependent descriptive history.

Key Information Stored

The table contains seven documented columns. The primary key is defined by the constraint XTR_AUDIT_COLUMNS_PK over the composite of EVENT and TABLE_COLUMN. A second unique index, XTR_AUDIT_COLUMNS_U1, spans EVENT, TABLE_COLUMN, and ZD_EDITION_NAME, making these three columns the principal business-key candidates and confirming that edition context participates in uniqueness.

• EVENT — the audit event or business action against which column-level audit rules are registered; part of both the primary key and the unique business key.
• TABLE_COLUMN — identifies the specific table column being audited or titled; the second component of the primary key.
• ZD_EDITION_NAME — the edition designator supporting Oracle's edition-based redefinition (EBR) model in 12.2.x, completing the unique business key.
• AUDIT_YN — a flag indicating whether the identified column is audited for the associated event.
• COLUMN_TYPE — classifies the column (for example, by data role or presentation grouping) so audit output can be formatted appropriately.
• P_KEY_YN — indicates whether the referenced table column forms part of a primary key, useful when constructing audit trails that must resolve entity identity.
• COLUMN_TITLE — the display label used when the audited column is rendered in audit inquiry screens or reports.

There is no documented warehouse-style surrogate key; identity is expressed entirely through the composite business key (EVENT, TABLE_COLUMN) plus the edition discriminator.

Common Use Cases and Queries

Typical uses include auditing configuration review, troubleshooting why a treasury field does or does not appear in audit history, and generating documentation of audit coverage. A representative query lists audited columns for a given event:

• SELECT event, table_column, column_title, column_type FROM xtr_audit_columns WHERE audit_yn = 'Y' AND event = :event ORDER BY table_column;
• SELECT table_column, column_title FROM xtr_audit_columns WHERE p_key_yn = 'Y' AND event = :event; — resolves key columns for building audit trails.
• SELECT DISTINCT event FROM xtr_audit_columns ORDER BY event; — inventories the audit events configured in the instance.

Reporting use cases center on audit-coverage matrices and data-governance reviews. In 12.2.x, queries should generally filter on the active ZD_EDITION_NAME to avoid returning rows from superseded editions.

Related Objects

Because the mined relationship classification is standalone, no documented foreign keys tie XTR_AUDIT_COLUMNS to other tables. Related objects therefore derive from functional context within the XTR Treasury schema rather than from enforced constraints:

• Audit history and audit trail tables in the XTR schema that consume EVENT and TABLE_COLUMN values from this registry.
• Treasury transaction and setup tables whose columns are referenced by TABLE_COLUMN, providing the target of the audit definitions.
• XTR concurrent programs and audit inquiry forms that read COLUMN_TITLE and COLUMN_TYPE for presentation.
• EBR edition metadata (ZD_EDITION_NAME) shared across the XTR schema in 12.2.x.
• The XTR_AUDIT_COLUMNS_PK and XTR_AUDIT_COLUMNS_U1 indexes, which enforce identity and uniqueness for the registry itself.

Administrators should treat this table as configuration data and change it only through supported Oracle setup procedures or after backup, since manual edits affect audit behavior across Treasury objects.