Results for “fnd_compiled_id_flexs”

50+ results




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

Overview

FND_COMPILED_ID_FLEXS is a core Applications Object Library (FND) table in Oracle E-Business Suite, owned by the APPLSYS schema. Its purpose is to store the compiled definitions of Key Flexfields (KFFs). In Oracle EBS, a Key Flexfield is a configurable field whose structure is defined by one or more segments separated by a delimiter, widely used for accounting flexfields, item categories, system items, and similar constructs. Because compiling a flexfield is an expensive operation, Oracle persists the compiled representation in this table so the runtime flexfield engine can validate and display segments efficiently. The table is populated and maintained during flexfield compilation, a routine commonly triggered from the Key Flexfield Segments form or the Flexfields Compiler concurrent program.

From a Data Vault modeling perspective (a heuristic mined from the foreign-key structure), this table is classified as satellite-leaning. It hangs off a parent flexfield definition table and carries descriptive compiled attributes, which is behavior consistent with a satellite entity rather than a hub or link.

Key Information Stored

The table documents nine physical columns. The most significant are:

  • APPLICATION_ID — The application owning the flexfield; part of both the primary key and the foreign key to FND_ID_FLEXS.
  • ID_FLEX_CODE — The internal code identifying the Key Flexfield (for example, GL# or MCAT); paired with APPLICATION_ID to identify the flexfield.
  • COMPILER_VERSION_NUM — The version number produced at compilation time, allowing multiple compiled versions to coexist.
  • SEQUENCE — Ordering sequence for the compiled rows that make up the flexfield definition.
  • COMPILED_DEFINITION — The actual compiled flexfield definition; the payload column holding the compiled structure.
  • LANGUAGE — The language context of the compiled definition, since segment prompts and descriptions are language-dependent.
  • ZD_EDITION_NAME — The editioning column used for the EBS online patching / edition-based redefinition model.
  • CREATION_DATE and CREATED_BY — Standard Who audit columns.

The documented primary key is FND_COMPILED_ID_FLEXS_PK, comprising APPLICATION_ID, ID_FLEX_CODE, COMPILER_VERSION_NUM, SEQUENCE, and LANGUAGE. A business-key candidate is exposed via the unique index FND_COMPILED_ID_FLEXS_U1, which adds ZD_EDITION_NAME to that same column set. Note that the surrogate PK columns are attributes of the natural flexfield identity rather than a generated sequence; the business key and primary key differ only by the editioning column.

Common Use Cases and Queries

This table is most often queried to troubleshoot flexfield compilation problems, confirm which compiled version is active, or determine whether a flexfield has been compiled at all. A typical diagnostic query joins the table to FND_ID_FLEXS to retrieve the application and flexfield name:

  • Check compilation status: SELECT application_id, id_flex_code, compiler_version_num, language, creation_date FROM applsys.fnd_compiled_id_flexs ORDER BY creation_date DESC;
  • Locate the latest compiled definition for a flexfield: filter by APPLICATION_ID and ID_FLEX_CODE, order by COMPILER_VERSION_NUM descending, and inspect the highest row.
  • Detect stale or duplicate versions: group by APPLICATION_ID, ID_FLEX_CODE, COMPILER_VERSION_NUM, and LANGUAGE to identify multiple compiled versions.
  • Audit who compiled and when: use CREATED_BY and CREATION_DATE for change-history reporting.

Common reporting scenarios include pre-upgrade flexfield readiness checks, reconciliation after a flexfield change, and identifying flexfields that have never been compiled. Because the COMPILED_DEFINITION payload is Oracle-internal and effectively opaque, most practical queries operate on the identity and audit columns rather than parsing that column's contents.

Related Objects

The documented foreign key anchors this table to the broader flexfield data model. The principal related objects are:

  • FND_ID_FLEXS — The parent definition table. FND_COMPILED_ID_FLEXS.APPLICATION_ID and ID_FLEX_CODE join to this table; this is the primary FK relationship.
  • FND_SEGMENT_ATTRIBUTES_VL — Provides segment-level attributes and names for the compiled flexfield's segments at query time.
  • FND_FLEX_VALUES / FND_FLEX_VALUES_VL — Holds valid segment values validated against the compiled structure.
  • FND_ID_FLEX_STRUCTURES — Defines the flexfield structures that compile into this table's rows.
  • FND_FLEX_VALUE_SETS and FND_FLEX_VALUE_NORM_HIERARCHY — Value-set and hierarchy metadata relevant to compiled segment validation.
  • FND_COMPILED_ID_FLEXS_U1 — The unique index enforcing the business key (including ZD_EDITION_NAME).

Together these objects form the Key Flexfield metadata layer that this table's compiled data supports at runtime.