Search Results xtr_audit_columns_u1




Overview
Explore in AI Chat

Overview

XTR.XTR_AUDIT_COLUMNS is a seed data configuration table owned by the XTR (External Transaction) schema in Oracle E-Business Suite. It defines, on a per-event and per-table-column basis, which columns of the XTR audit trail are subject to audit capture. The table resides in the APPS_TS_SEED tablespace, confirming its role as a reference or setup table rather than a transactional table. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and it carries the standard Oracle internal-use restriction: Oracle Corporation does not support direct access to this data except through standard Oracle Applications programs. The table includes the ZD_EDITION_NAME column, which is consistent with the editioning infrastructure used in the 12.2.x online patching architecture.

From a heuristic Data Vault modeling perspective, XTR_AUDIT_COLUMNS exhibits the characteristics of a reference or lookup satellite, since it stores descriptive attribute values keyed by a composite natural key. However, the metadata classifies the object as standalone, meaning no foreign-key relationships to other tables were mined. This classification is advisory and reflects the limited relational metadata available rather than a definitive architectural statement.

Key Information Stored

The table contains seven documented columns. The most significant are:

  • EVENT (VARCHAR2, 50) — Identifies the audit event to which the column configuration applies. This column forms part of both the primary key and the unique index.
  • TABLE_COLUMN (VARCHAR2, 50) — Names the specific table column being audited. Together with EVENT, this forms the documented primary key XTR_AUDIT_COLUMNS_PK.
  • AUDIT_YN (VARCHAR2) — A flag indicating whether the column is to be audited. Valid values are Y (audit) and N (do not audit). This is the operative control value of the table.
  • COLUMN_TYPE (VARCHAR2, 15) — Classifies the column type, supporting downstream processing logic.
  • P_KEY_YN (VARCHAR2) — Indicates whether the table column participates as a primary key within the audit context.
  • COLUMN_TITLE (VARCHAR2, 50) — Supplies a display title for the audited column, useful in reporting and user interfaces.
  • ZD_EDITION_NAME (VARCHAR2, 30) — Editioning support column, present in 12.2.x environments to support online patching.

The documented unique index XTR_AUDIT_COLUMNS_U1 is defined on (EVENT, TABLE_COLUMN, ZD_EDITION_NAME). Because this index includes the edition name, it represents the edition-aware business key and is the object referenced by the search term "xtr_audit_columns_u1". The three-column unique key is broader than the two-column primary key (EVENT, TABLE_COLUMN), reflecting the editioning model where the same logical row may exist across editions.

Common Use Cases and Queries

Administrators and developers query this table to determine which columns are actively audited for a given XTR event, to troubleshoot missing audit records, or to validate seed data after a patch or upgrade. A typical query retrieves the audit configuration for a specific event:

  • SELECT EVENT, TABLE_COLUMN, COLUMN_TITLE, AUDIT_YN, P_KEY_YN, COLUMN_TYPE FROM XTR.XTR_AUDIT_COLUMNS WHERE EVENT = :event ORDER BY TABLE_COLUMN;
  • To list all audited columns: SELECT EVENT, TABLE_COLUMN FROM XTR.XTR_AUDIT_COLUMNS WHERE AUDIT_YN = 'Y';
  • To verify edition-specific configuration in 12.2.x: SELECT * FROM XTR.XTR_AUDIT_COLUMNS WHERE ZD_EDITION_NAME = :edition;

Report writers may join the COLUMN_TITLE values to audit trail extracts to produce human-readable audit reports. Because the object is a seed table, changes should generally be made through supported Oracle setup flows rather than direct DML.

Related Objects

The documented metadata states that XTR_AUDIT_COLUMNS does not reference any database object and is referenced only by XTR_AUDIT_COLUMNS#, the editioning view associated with the underlying table in 12.2.x. No foreign-key relationships were mined, consistent with the standalone classification. In practice, the table is functionally related to the audit trail tables within the XTR schema that store captured event data, and to the XTR event definitions that supply the EVENT values used as part of the primary key. Administrators should consult the XTR audit trail schema documentation for the specific audit data tables consumed at runtime, as those relationships are enforced by application logic rather than database constraints.