Results for “column_name”

50+ results




Overview
Explore in AI Chat

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

Overview

The view CSC_FND_ALL_COLUMNS_V is an APPS-owned database object in Oracle E-Business Suite, delivered under the CSC (Customer Care) product module. It is documented with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Its stated purpose is to return column properties held within the Oracle Application Object Library (FND) metadata tables, specifically the column definitions recorded in FND_COLUMNS.

The view exists to support the CSC module's internal metadata and reporting requirements, and more broadly it provides a normalized, read-only surface for querying column-level definitions across both physical tables and views. Rather than requiring a caller to know that table columns and view columns are stored in two separate FND tables with differing key semantics, CSC_FND_ALL_COLUMNS_V presents them through a single, uniform set of columns. This makes it useful for metadata reporting, technical documentation, dependency analysis, and integration utilities that need to introspect column structure.

Underlying Base Objects

The documented view text defines CSC_FND_ALL_COLUMNS_V as the UNION of two select statements over two FND synonyms:

  • FND_COLUMNS — as alias A, supplying table column definitions plus the literal type flag 'TABLE'.
  • FND_VIEW_COLUMNS — as alias B, supplying view column definitions plus the literal type flag 'VIEW'.

Because the view text uses UNION rather than UNION ALL, Oracle applies a distinct operation across the combined result set, so duplicate rows (same application, object, sequence, name, and description) are collapsed. The ETRM metadata records both base objects as SYNONYM references resolved within the APPS schema, consistent with standard Oracle EBS naming and the FND synonym architecture.

Key Columns

The view exposes six columns:

  • APPLICATION_ID — the numeric identifier of the application that owns the object, drawn from FND_APPLICATION. In FND_COLUMNS this is the owning application; in FND_VIEW_COLUMNS the column is aliased from the view's application identifier.
  • TABLE_ID — despite the name, this is a polymorphic key. For rows sourced from FND_COLUMNS it is the FND_TABLES TABLE_ID; for rows sourced from FND_VIEW_COLUMNS it carries the FND_VIEWS VIEW_ID. This unioned column is the most common source of confusion when joining the view to table or view catalogs.
  • COLUMN_SEQUENCE — the ordinal position of the column within the parent object, indicating physical or logical ordering.
  • COLUMN_NAME — the name of the column as defined in the data dictionary.
  • DESCRIPTION — the descriptive text for the column. For rows originating in FND_VIEW_COLUMNS the expression is a literal NULL, so view-sourced columns carry no description through this view.
  • TYPE — a literal discriminator populated as 'TABLE' or 'VIEW', identifying which underlying source produced the row.

Common Use Cases and Queries

The primary use case is metadata discovery: identifying which columns belong to a given table or view, and distinguishing table columns from view columns in a single pass. Because the view resolves APPLICATION_ID, callers can restrict results to a specific application, such as Customer Care.

Listing all columns for a given object, filtering on the discriminator:

SELECT application_id, table_id, column_sequence, column_name, description, type FROM apps.csc_fnd_all_columns_v WHERE type = 'TABLE' AND application_id = :app_id ORDER BY table_id, column_sequence;

Separating table and view columns with a classification:

SELECT type, COUNT(*) FROM apps.csc_fnd_all_columns_v GROUP BY type;

Finding a column by name across all tables and views:

SELECT application_id, table_id, column_name, type FROM apps.csc_fnd_all_columns_v WHERE column_name = 'CUSTOMER_ID';

Because TABLE_ID is unioned, joins to FND_TABLES or FND_VIEWS must be conditioned on the TYPE column to avoid mismatched associations. For detailed view column behavior, FND_VIEW_COLUMNS should be queried directly.