Results for “fnd_compiled_descr_flexes_pk”

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

Overview

FND_COMPILED_DESCRIPTIVE_FLEXS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the compiled, runtime-ready definition of descriptive flexfields. Descriptive flexfields allow customers to extend standard EBS forms and tables with additional attribute columns without modifying the base application schema. When a descriptive flexfield is compiled through the Flexfield Segments form or the concurrent program, Oracle generates metadata that the runtime engine consumes. This table holds that generated output, keyed by the flexfield's application, name, compiler version, segment sequence, and language.

Because the table is versioned by COMPILER_VERSION_NUM and LANGUAGE, it retains compiled definitions across compiler iterations and installed languages rather than a single mutable row per flexfield. This permits cached runtime lookups and supports multi-language deployments. Under the heuristic Data Vault classification derived from its foreign key structure, the object is described as satellite-leaning: it hangs off the FND_DESCRIPTIVE_FLEXS parent and carries descriptive, version-dependent attributes rather than acting as an independent hub or a pure relationship link.

Key Information Stored

The table is documented with nine columns. The primary key, FND_COMPILED_DESCR_FLEXES_PK, is a composite business key comprising APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, COMPILER_VERSION_NUM, SEQUENCE, and LANGUAGE. A secondary unique index, FND_COMPILED_DESCR_FLEXS_U1, extends the same column set with ZD_EDITION_NAME, reflecting the editioning infrastructure introduced in 12.2. The most significant columns include:

• APPLICATION_ID — identifies the owning application; part of the composite key and the foreign key to FND_DESCRIPTIVE_FLEXS.
• DESCRIPTIVE_FLEXFIELD_NAME — the internal flexfield name; the second component of the composite key and foreign key.
• COMPILER_VERSION_NUM — the version of the compiler that produced the row, allowing multiple compiled generations to coexist.
• SEQUENCE — orders the compiled definition blocks or segments within a version/language combination.
• LANGUAGE — the language code of the compiled definition, enabling translated prompt text.
• COMPILED_DEFINITION — the substantive payload: the compiled flexfield metadata consumed at runtime.
• ZD_EDITION_NAME — the edition name used by the 12.2 edition-based redefinition framework.
• CREATION_DATE and CREATED_BY — standard WHO audit columns recording row creation.

Note that no CLIENT_ID or ORG_ID column is present, confirming this is a setup/definition table rather than a transactional or multi-org table.

Common Use Cases and Queries

Administrators and technical consultants query this table to verify that a descriptive flexfield has been compiled and to inspect the active compiler version. A typical pattern retrieves the latest compiled definition for a given flexfield:

• SELECT fdf.descriptive_flexfield_name, fdf.compiler_version_num, fdf.language FROM fnd_compiled_descriptive_flexs fdf WHERE fdf.application_id = :app_id AND fdf.descriptive_flexfield_name = :name ORDER BY fdf.compiler_version_num DESC;
• Diagnostic queries compare rows here against FND_DESCRIPTIVE_FLEXS to detect a stale or missing compilation after a patch or DDL change.
• Reporting on language coverage: count distinct LANGUAGE values per flexfield to confirm translated definitions are present.
• Troubleshooting runtime prompt or validation errors by inspecting COMPILED_DEFINITION for the active version.

Related Objects

The principal relationship documented is a foreign key from APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME to FND_DESCRIPTIVE_FLEXS, the parent definition table. Other objects that reference or depend on this area include FND_DESCRIPTIVE_FLEXS_VL, FND_FLEX_VALIDATION_TABLES and the flexfield value-set tables used at runtime, FND_FLEX_VALUES and FND_FLEX_VALUES_TL, which resolve allowed values, and the Flexfield Segments and Value Sets forms that drive compilation. The FND_FLEX_API and FND_FLEX_EXT packages, together with the Generate Flexfields concurrent program, manage the lifecycle that populates this table.