Search Results fnd_audit_disp_cols




Overview
Explore in AI Chat

Overview

FND_AUDIT_DISP_COLS is a configuration table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). The table stores the display columns used by the Audit Query Navigator, the user interface component that allows administrators and auditors to selectively view the audited column values captured for a given audited table and application combination. Rather than exposing every column of an audited table by default, the Audit Query Navigator consults this table to determine which columns are displayed, how they are selected, and how the underlying query is composed.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This is a modeling suggestion indicating that no foreign-key-derived parent relationships were mined from the ETRM structure; the table functions as an independent configuration registry keyed by a composite business identifier. Its primary key, FND_AUDIT_DISP_COLS_PK1, is defined on the column pair (TABLE_ID, APPLICATION_ID), which uniquely identifies one row per audited table within a given application context.

Key Information Stored

The documented physical schema contains six columns. The most significant are:

  • APPLICATION_ID — Identifies the EBS application that owns the audited table. Part of both the primary key and the unique index.
  • TABLE_ID — Identifies the specific audited table within the application. Part of both the primary key and the unique index.
  • COL_DISP_IND — A display indicator that controls whether the associated column is presented in the Audit Query Navigator output.
  • SELECT_CLAUSE — The SQL select-list fragment used to build the navigator's dynamic query for the audited table.
  • FROM_CLAUSE — The SQL from-list fragment supplying the source table(s) for the dynamic query.
  • WHERE_CLAUSE — The SQL predicate fragment used to filter the audited records returned by the navigator.

The surrogate-style composite key is (TABLE_ID, APPLICATION_ID). The unique index FND_AUDIT_DISP_COLS_U1 covers the same two columns in reverse order (APPLICATION_ID, TABLE_ID), serving as the business-key candidate and reinforcing the one-row-per-table-per-application rule. Notably, SELECT_CLAUSE, FROM_CLAUSE, and WHERE_CLAUSE store SQL text rather than live objects, so this table is a driver of runtime SQL generation rather than a data repository in the traditional sense.

Common Use Cases and Queries

Typical scenarios include diagnosing why an audited column does not appear in the Audit Query Navigator, auditing the configuration of the navigator across applications, and reviewing customizations applied to the generated query fragments. A common diagnostic query enumerates the configuration for a specific application and table:

  • SELECT application_id, table_id, col_disp_ind, select_clause, from_clause, where_clause FROM applsys.fnd_audit_disp_cols WHERE application_id = :app_id AND table_id = :table_id;

Because the clauses are text, reporting queries frequently join back to FND_TABLES and FND_APPLICATION to resolve human-readable table and application names. Change-tracking scripts compare rows against a baseline to detect unauthorized modifications to SELECT_CLAUSE, FROM_CLAUSE, or WHERE_CLAUSE, since these directly affect what data appears in audit investigations. Disabled display entries are easily located with WHERE col_disp_ind = 'N' to identify columns hidden from the navigator.

Related Objects

The following objects are most relevant when working with this table:

  • FND_TABLES — joined via TABLE_ID and APPLICATION_ID to resolve the audited table's name and properties.
  • FND_APPLICATION — joined via APPLICATION_ID to resolve the owning application name and short name.
  • FND_AUDIT_TABLES — the parent audit-registry table identifying which tables participate in auditing.
  • FND_AUDIT_COLUMNS — the companion configuration that defines which columns are audited, complemented by the display entries in this table.
  • FND_AUDIT_QUERY_NAV / Audit Query Navigator UI components — consume COL_DISP_IND and the clause fragments to render results.
  • FND_AUDIT_TRAIL (and related shadow/audit tables) — the underlying audited data the navigator queries using the stored clauses.

Because the metadata identifies this object as standalone, no direct foreign-key constraints are documented; associations to the above objects are maintained through the TABLE_ID and APPLICATION_ID values rather than enforced referential integrity.