Results for “fnd_id_flexs”

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

Overview

FND_ID_FLEXS is the registration repository for key flexfield definitions in Oracle E-Business Suite, owned by the APPLSYS schema and belonging to the FND — Application Object Library product. Each row registers a single key flexfield, such as the Accounting Flexfield (GL#), the Asset Category Flexfield, or the Item Category Flexfield, binding it to the application and underlying database table that physically stores its concatenated segment values. Because key flexfields underpin the majority of Oracle EBS subledger and general ledger processing, FND_ID_FLEXS functions as a foundational configuration reference rather than transactional data.

From a dimensional modeling perspective, the table behaves as a hub. Its natural business key is the combination of APPLICATION_ID and ID_FLEX_CODE, and it anchors relationships to structures, compiled definitions, segment attribute types, and flexfield-builder functions. This classification should be treated as a heuristic modeling suggestion rather than a definitive EDW design rule.

Key Information Stored

The table contains 21 documented columns. The most significant include:

• APPLICATION_ID — the owning application; part of the composite primary key FND_ID_FLEXS_PK.
• ID_FLEX_CODE — the short code uniquely identifying the flexfield (for example, GL#); the second component of the primary key.
• ID_FLEX_NAME — the descriptive display name; together with APPLICATION_ID, forms unique index FND_ID_FLEXS_UK1 / FND_ID_FLEXS_U2.
• TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME — the application and physical table that store the flexfield's combined segment values.
• APPLICATION_TABLE_TYPE — classifies the storage table type.
• UNIQUE_ID_COLUMN_NAME — the unique identifier column on the underlying table.
• SET_DEFINING_COLUMN_NAME — the column used to enforce set-defining behavior per structure.
• ALLOW_ID_VALUESETS — controls whether the flexfield permits ID value sets.
• DYNAMIC_INSERTS_FEASIBLE_FLAG — indicates whether dynamic insertion is allowed.
• MAXIMUM_CONCATENATION_LEN and CONCATENATION_LEN_WARNING — define concatenated segment length limits and warning thresholds.
• CONCATENATED_SEGS_VIEW_NAME and INDEX_FLAG — the concatenated segments view and indexing indicator.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 schema, appearing in unique indexes FND_ID_FLEXS_U1 and FND_ID_FLEXS_U2.
• DESCRIPTION, LAST_UPDATE_DATE, and audit columns — document and track the registration record.

The surrogate PK (APPLICATION_ID, ID_FLEX_CODE) should be distinguished from the business-key candidates exposed through FND_ID_FLEXS_U1 and FND_ID_FLEXS_U2, which add ZD_EDITION_NAME.

Common Use Cases and Queries

Typical scenarios include identifying which physical table stores a flexfield's values, resolving a flexfield code to its display name, and auditing which flexfields allow dynamic inserts or ID value sets.

• Resolve a flexfield by code: SELECT id_flex_name, application_table_name FROM fnd_id_flexs WHERE id_flex_code = 'GL#';
• Locate storage details for a flexfield: select APPLICATION_TABLE_NAME and UNIQUE_ID_COLUMN_NAME for a given APPLICATION_ID and ID_FLEX_CODE.
• Audit configuration: filter on ALLOW_ID_VALUESETS or DYNAMIC_INSERTS_FEASIBLE_FLAG to enumerate flexfields with specific behaviors.
• Join to FND_ID_FLEX_STRUCTURES to report on all structures built on each registered flexfield.
• Concatenation monitoring: compare MAXIMUM_CONCATENATION_LEN against CONCATENATION_LEN_WARNING for capacity planning.

Related Objects

• FND_ID_FLEX_STRUCTURES — joins on APPLICATION_ID and ID_FLEX_CODE; defines structures for each flexfield.
• FND_COMPILED_ID_FLEXS — joins on APPLICATION_ID and ID_FLEX_CODE; holds compiled flexfield definitions.
• FND_SEGMENT_ATTRIBUTE_TYPES — joins on APPLICATION_ID and ID_FLEX_CODE; defines segment attribute types.
• FND_FLEXBUILDER_FUNCTIONS — joins via FLEXFIELD_APPLICATION_ID and ID_FLEX_CODE.
• PA_FUNCTIONS — references APPLICATION_ID and ID_FLEX_CODE for project accounting functions.
• FND_APPLICATION — parent lookup on APPLICATION_ID.
• FND_TABLES — referenced through TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME.