Results for “fnd_view_columns”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_VIEW_COLUMNS is a registration table in the Oracle Application Object Library (product FND) that stores the columns belonging to views defined through the Oracle E-Business Suite applications dictionary. Owned by the APPLSYS schema, the table records which database columns make up each registered view, along with their ordinal position within that view. It is an operational metadata table used internally by Oracle Application Object Library to manage and expose view definitions consistently across EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification of FND_VIEW_COLUMNS is satellite-leaning. This reflects the fact that the table hangs off a parent entity, FND_VIEWS, and captures descriptive, versioned attributes about that parent rather than acting as an independent hub of business keys. Each row enriches a view definition with column-level detail.

Key Information Stored

The table contains eleven documented columns. The most significant include the following.

• APPLICATION_ID — Identifies the EBS application that owns the view definition.
• VIEW_ID — The identifier of the parent view in FND_VIEWS to which the column belongs.
• COLUMN_SEQUENCE — The ordinal position of the column within the view, establishing column ordering.
• COLUMN_NAME — The database column name included in the registered view.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking who performed the most recent change and when.
• CREATION_DATE, CREATED_BY — Standard audit columns recording initial row creation.
• IREP_COMMENTS — Free-text comments associated with the registered column, used in reporting dictionary context.
• ZD_EDITION_NAME — Editioning support column used by the EBS 12.2 online patching (edition-based redefinition) architecture.

The surrogate primary key is FND_VIEW_COLUMNS_PK, defined on (APPLICATION_ID, VIEW_ID, COLUMN_SEQUENCE). Two business-key candidates are documented as unique indexes: FND_VIEW_COLUMNS_U1 on (COLUMN_NAME, APPLICATION_ID, VIEW_ID, ZD_EDITION_NAME), which enforces uniqueness of a named column per view, and FND_VIEW_COLUMNS_U2 on (APPLICATION_ID, VIEW_ID, COLUMN_SEQUENCE, ZD_EDITION_NAME), which enforces uniqueness of column position per view per edition.

Common Use Cases and Queries

FND_VIEW_COLUMNS is typically queried during metadata analysis, custom reporting dictionary development, and impact assessment prior to patching or view redefinition. A representative query to enumerate the columns of a view in sequence is:

• SELECT column_sequence, column_name FROM applsys.fnd_view_columns WHERE application_id = :app_id AND view_id = :view_id ORDER BY column_sequence;

Another common pattern joins to FND_VIEWS to resolve view names and confirm the parent definition, useful when building a catalog of registered views and their constituent columns. DBAs also query these rows when troubleshooting view registration or investigating discrepancies in reporting metadata between environments.

Related Objects

The most significant related object is its parent table FND_VIEWS, tied through the foreign key FND_VIEW_COLUMNS.APPLICATION_ID and VIEW_ID referencing FND_VIEWS. This relationship is the primary dependency and defines the satellite-to-parent association described in the modeling classification. Additional related FND objects include FND_APPLICATION (via APPLICATION_ID for application context) and the various reporting and dictionary registration tables that consume view definitions. Because the ETRM documentation for this object is limited, the practical dependency set centers on FND_VIEWS, and any dependent metadata should be traced upward through the view registration hierarchy rather than treating FND_VIEW_COLUMNS as a standalone entity.