Search Results fnd_default_context_fields_pk

Overview

FND_DEFAULT_CONTEXT_FIELDS is an Application Object Library (FND) reference table in the APPLSYS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the names of form fields that end users may designate as reference fields when defining descriptive flexfield context behavior. Descriptive flexfields allow an application to extend standard forms with additional, customer-defined attributes; this table identifies which of those attributes are eligible to serve as the reference or driving field for a given flexfield structure, thereby determining how context-sensitive segments are populated and validated at runtime.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. The heuristic derives this because the table carries descriptive attributes that qualify a parent flexfield definition rather than acting as an independent business entity or pure association. Modelers should treat it as a satellite of the descriptive flexfield construct, with the caution that this classification is a suggestion mined from relationships, not an authoritative design statement.

Key Information Stored

The table is defined with ten documented columns in the ETRM 12.2.2 physical schema, of which the following are most significant.

• APPLICATION_ID — Identifies the owning application; part of the primary key and the foreign-key link to the flexfield definition.
• DESCRIPTIVE_FLEXFIELD_NAME — The application-defined name of the descriptive flexfield to which the reference field applies; also part of the primary key.
• DEFAULT_CONTEXT_FIELD_NAME — The form field name that users may select as a reference field. This is the third component of the composite primary key and the primary business attribute of the row.
• DESCRIPTION — Free-text explanation of the reference field's purpose, typically surfaced to administrators during flexfield setup.
• ZD_EDITION_NAME — The edition identifier used by the EBS online patching (Editioning) mechanism in 12.2.x; it participates in the unique index and is absent from 12.1.1 instances.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard FND audit columns that track who created and last modified each row and when.

The surrogate primary key is FND_DEFAULT_CONTEXT_FIELDS_PK over (APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DEFAULT_CONTEXT_FIELD_NAME). The unique index FND_DEFAULT_CONTEXT_FIELDS_U1 adds ZD_EDITION_NAME to the same three columns, which is the practical business-key candidate for 12.2.x environments. No separate single-column surrogate identifier is documented.

Common Use Cases and Queries

Administrators and technical consultants query this table when troubleshooting descriptive flexfield context setup, when validating migrations of flexfield definitions between environments, and when building reports that document reference-field availability per flexfield. A typical query lists all reference fields for a named flexfield:

• SELECT default_context_field_name, description FROM fnd_default_context_fields WHERE descriptive_flexfield_name = :flex_name AND application_id = :app_id AND zd_edition_name = 'SET1';
• A referential-integrity check joins back to FND_DESCRIPTIVE_FLEXS to detect orphaned reference fields: SELECT d.descriptive_flexfield_name, d.default_context_field_name FROM fnd_default_context_fields d, fnd_descriptive_flexs f WHERE d.application_id = f.application_id(+) AND d.descriptive_flexfield_name = f.descriptive_flexfield_name(+) AND f.descriptive_flexfield_name IS NULL;
• Audit reporting uses last_update_date and last_updated_by to identify recent configuration changes prior to a release or patch.

Because the flexfield definitions themselves are cached by the FND runtime, direct DML against this table is not supported; changes should be made through the Descriptive Flexfields setup form or the supported flexfield APIs.

Related Objects

• FND_DESCRIPTIVE_FLEXS — Parent table referenced through (APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME); the definitive join partner.
• FND_FLEX_VALIDATION_EVENTS, FND_FLEX_VALUE_SETS, and FND_FLEX_VALUES — Configure validation and value storage for segments that reference context fields.
• FND_SEGMENT_ATTRIBUTES and FND_DESCR_FLEX_COL_USAGE — Define how flexfield segments map to underlying columns.
• FND_FORM_FUNCTIONS and FND_APPLICATION — Identify the form and application context in which the reference field is used.