Results for “fnd_views”

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

Overview

FND_VIEWS is a registration table in the Oracle E-Business Suite Application Object Library (FND) that catalogs database views defined within registered Oracle EBS applications. Owned by the APPLSYS schema, the table stores metadata about each view, including its owning application and descriptive text, so that Oracle Application Object Library and related framework components can resolve view definitions at runtime. It is a core component of the EBS metadata layer used by Oracle Forms, Oracle Reports, and building-block registrations.

From a Data Vault modeling perspective, the heuristic classification for FND_VIEWS is hub-leaning. This reflects the presence of stable business keys (application and view identifiers) that are referenced by multiple dependent tables, which is characteristic of a hub entity. The classification is offered as a modeling suggestion rather than an authoritative designation.

Key Information Stored

The table contains thirteen documented columns in the 12.2.2 schema. The most significant of these are:

• APPLICATION_ID — Identifies the registered EBS application that owns the view. This is a foreign key to FND_APPLICATION and part of both primary and unique keys.
• VIEW_ID — The internal surrogate identifier for the registered view. Combined with APPLICATION_ID, it forms the primary key FND_VIEWS_PK.
• VIEW_NAME — The database name of the registered view; combined with APPLICATION_ID it forms the unique business key FND_VIEWS_UK1.
• DESCRIPTION — A user- or developer-supplied textual description of the view's purpose.
• TEXT — The SQL text or definition associated with the registered view.
• IREP_COMMENTS and IREP_ANNOTATIONS — Repository comments and annotations, typically used by Oracle's internal repository/design-time tooling.
• ZD_EDITION_NAME — Editioning column supporting Oracle's Edition-Based Redefinition (EBR), required for online patching in EBS 12.2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-audit columns tracking row creation and modification.

The primary key is FND_VIEWS_PK (APPLICATION_ID, VIEW_ID); the business-key candidates are captured by FND_VIEWS_UK1 (APPLICATION_ID, VIEW_NAME) and, in 12.2 at the physical level, by FND_VIEWS_U1 and FND_VIEWS_U2, which include ZD_EDITION_NAME to accommodate editioned rows.

Common Use Cases and Queries

FND_VIEWS is most commonly queried to resolve view IDs to names, to audit which applications register which views, and to identify views for a specific application or pattern. A representative query joining to the owning application is shown below:

SELECT v.application_id,
       a.application_short_name,
       v.view_id,
       v.view_name,
       v.description,
       v.last_update_date
FROM   applsys.fnd_views v,
       applsys.fnd_application a
WHERE  v.application_id = a.application_id
AND    v.view_name LIKE 'FND_%'
ORDER BY v.view_name;

Developers also use it when tracing dependencies, for example finding views owned by a custom application, or joining to FND_VIEW_COLUMNS to enumerate the columns belonging to a given view. Because registration rows are created and maintained by Oracle's internal loaders, the table should be treated as read-only for query and reporting purposes.

Related Objects

• FND_APPLICATION — Referenced via FND_VIEWS.APPLICATION_ID; identifies the owning registered application.
• FND_VIEW_COLUMNS — Child table referencing FND_VIEWS on (APPLICATION_ID, VIEW_ID); stores the individual column definitions belonging to each registered view.
• FND_BUILDING_BLOCK_OBJECTS — References FND_VIEWS through OBJECT_APPLICATION_ID and OBJECT_ID, linking views into the broader building-block/object registry.
• FND_TABLES — The sibling registry for base tables; frequently compared alongside FND_VIEWS when analyzing the EBS data dictionary.
• FND_APPLICATION_TL — Provides translated application names for reporting alongside view metadata.