Search Results fnd_columns

Overview

The FND_COLUMNS table is a core metadata repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the central registry for storing descriptive information about every column in all registered application tables across the Oracle EBS environment. This registration is a fundamental aspect of the EBS architecture, enabling key platform features such as data auditing, security, and the declarative definition of database constraints. Its role is to provide a unified, application-aware catalog of the database schema, which is essential for the runtime and administrative frameworks in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to uniquely identify a column within the context of its owning application and table. The primary key (FND_COLUMNS_PK) is a composite of APPLICATION_ID, TABLE_ID, and COLUMN_ID. Important columns include APPLICATION_ID and TABLE_ID, which link to the FND_TABLES registry, and COLUMN_ID, a unique numeric identifier for the column within its table. The table stores both the physical database column name (COLUMN_NAME) and a user-facing name (USER_COLUMN_NAME), facilitating internationalization and end-user reporting. Additional metadata includes COLUMN_SEQUENCE for display order, WIDTH, and ENABLED_FLAG to control the column's active status within the application framework.

Common Use Cases and Queries

This table is primarily queried for metadata discovery, impact analysis, and generating audit reports. Common scenarios include identifying all columns within a specific registered table for documentation or determining which columns are enabled for auditing. A typical query retrieves column details for a known table:

• SELECT fc.user_column_name, fc.column_name, fc.column_sequence FROM fnd_columns fc, fnd_tables ft WHERE fc.table_id = ft.table_id AND fc.application_id = ft.application_id AND ft.table_name = 'PO_HEADERS_ALL';

Another critical use case is verifying the setup for Flexfields or auditing, often joining with related tables like FND_AUDIT_COLUMNS to list audited columns for a given entity.

Related Objects

FND_COLUMNS sits at the center of a network of metadata tables. Its primary relationship is with FND_TABLES, enforced by a foreign key. It is directly referenced by several key constraint and index definition tables: FND_PRIMARY_KEY_COLUMNS, FND_FOREIGN_KEY_COLUMNS, and FND_INDEX_COLUMNS. Most importantly, it is the parent table for FND_AUDIT_COLUMNS, which stores the specific auditing rules enabled for a registered column. Any operation that leverages EBS's declarative constraint or audit functionality will traverse through the FND_COLUMNS registry.