Search Results fnd_default_context_fields_u1

Overview

APPLSYS.FND_DEFAULT_CONTEXT_FIELDS is an Oracle E-Business Suite reference table that stores the names of form fields which users may select as reference fields when defining descriptive flexfields. Each row associates a descriptive flexfield with an application, a registered reference field name, and a description of that field. Oracle Application Object Library (FND) populates and consumes this data to drive the list of values (LOV) presented to implementers and installers during descriptive flexfield definition, ensuring that only fields explicitly registered by the application developer are made available as context references.

The object resides in the APPLSYS schema and is classified as FND design data (FND.FND_DEFAULT_CONTEXT_FIELDS), with a status of VALID across EBS 12.1.1 and 12.2.2. Its physical storage is in the APPS_TS_SEED tablespace, reflecting its role as seeded reference metadata rather than transactional data. From a dimensional modeling perspective, the mined relationship structure suggests a satellite-leaning classification: the table carries descriptive attributes (the reference field name and its description) that qualify a parent descriptive flexfield definition rather than acting as an independent hub or an associative link between two strong entities.

Key Information Stored

The table comprises ten documented columns. The composite business key is enforced by the unique index FND_DEFAULT_CONTEXT_FIELDS_U1, which spans APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DEFAULT_CONTEXT_FIELD_NAME. In the 12.2.2 physical schema, this unique index additionally includes ZD_EDITION_NAME, the editioning column introduced by the 12.2 online patching architecture; the corresponding primary key is FND_DEFAULT_CONTEXT_FIELDS_PK over the same three business columns. The most significant columns are:

• APPLICATION_ID — Numeric identifier of the application that owns the descriptive flexfield; part of the composite business key and the foreign key to APPLSYS.FND_DESCRIPTIVE_FLEXS.
• DESCRIPTIVE_FLEXFIELD_NAME — The internal name of the descriptive flexfield for which the reference field is registered; part of the business key.
• DEFAULT_CONTEXT_FIELD_NAME — The name of the form field offered as a reference field; part of the business key and typically the value users select in the LOV.
• DESCRIPTION — Free-text description of the reference field, displayed to aid selection.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata for each row.
• ZD_EDITION_NAME — Editioning column used by the 12.2 online patching infrastructure.

Common Use Cases and Queries

Implementation and support teams query this table to determine which reference fields are available for a given descriptive flexfield, to audit seeded versus custom registrations, and to troubleshoot why a particular field does not appear in the flexfield definition LOV. A typical lookup joins the table to FND_DESCRIPTIVE_FLEXS to resolve application and flexfield names, for example:

• Listing registered fields for a flexfield: SELECT DEFAULT_CONTEXT_FIELD_NAME, DESCRIPTION FROM APPLSYS.FND_DEFAULT_CONTEXT_FIELDS WHERE APPLICATION_ID = :app_id AND DESCRIPTIVE_FLEXFIELD_NAME = :df_name;
• Resolving flexfield titles: join APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME to APPLSYS.FND_DESCRIPTIVE_FLEXS.
• Reporting new custom reference fields: filter on CREATION_DATE or LAST_UPDATED_BY to identify rows added after a baseline date.
• Validating seed data integrity: count rows per APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME to detect missing or duplicate registrations.

Related Objects

The object participates in a narrow dependency footprint. The most significant related objects are:

• APPLSYS.FND_DESCRIPTIVE_FLEXS — Parent definition table; FND_DEFAULT_CONTEXT_FIELDS.APPLICATION_ID references it, and joins typically also match DESCRIPTIVE_FLEXFIELD_NAME.
• APPS.FND_DEFAULT_CONTEXT — The APPS synonym or view through which this table is referenced, and the primary runtime access point for the data.
• FND_DEFAULT_CONTEXT_FIELDS_PK / FND_DEFAULT_CONTEXT_FIELDS_U1 — The primary key constraint and unique index that enforce and support the composite business key.
• APPLSYS.FND_APPLICATION — Reference table for resolving APPLICATION_ID to application names in reporting queries.
• FND_DESCRIPTIVE_FLEXFIELD APIs — The flexfield definition routines that consume this table to populate the reference field LOV during setup.