Search Results flexfield_usage_code




Overview
Explore in AI Chat

Overview

FND_COLUMNS is a core Application Object Library (FND) metadata table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores one row for every column defined across all registered application tables, forming the column-level component of the Oracle EBS data dictionary. As a VALID, registered object, it supports the runtime infrastructure that drives Flexfields, descriptive and key flexfield segment definitions, concurrent program parameters, and the AD (Applications DBA) utility layer that builds and validates database objects.

Each row links a column to its owning table through the composite key APPLICATION_ID and TABLE_ID (foreign keyed to FND_TABLES), and identifies the column itself through COLUMN_ID. This three-part combination is both the primary key (FND_COLUMNS_PK) and the natural business key.

Under a heuristic Data Vault classification, this object behaves as a hub-leaning entity: it holds the unique identity of each column in the enterprise dictionary and is referenced by numerous downstream satellite-style tables (audit columns, index columns, primary key columns, foreign key columns). A Data Vault model would therefore treat it as a hub, with those downstream tables acting as links or satellites.

Key Information Stored

The most significant columns capture the column identity, its owning table, and its Flexfield attributes:

Business-key candidates in 12.2.2 include FND_COLUMNS_U1, U2, U3, and U4, which add ZD_EDITION_NAME to enforce uniqueness under Edition-Based Redefinition.

Common Use Cases and Queries

Administrators and developers query FND_COLUMNS to inspect table structures, confirm Flexfield registrations, or trace which columns drive validation logic.

SELECT c.column_name, c.user_column_name, c.column_type, c.flexfield_usage_code
FROM   fnd_columns c
WHERE  c.table_id = :table_id
AND    c.application_id = :application_id
ORDER  BY c.column_sequence;

A common join resolves the owning table name through FND_TABLES:

SELECT t.table_name, c.column_name, c.column_type
FROM   fnd_columns c, fnd_tables t
WHERE  c.application_id = t.application_id
AND    c.table_id       = t.table_id
AND    c.flexfield_usage_code IS NOT NULL;

Typical scenarios include auditing which Flexfields are attached to a table, verifying value-set bindings, generating custom data-dictionary reports, and diagnosing EBS schema mismatches after patching.

Related Objects

The following objects reference or depend on FND_COLUMNS via documented foreign keys:

These relationships confirm FND_COLUMNS as the central dictionary hub for column definitions across the EBS schema.