Results for “fnd_id_flex_segments”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_ID_FLEX_SEGMENTS is a core Application Object Library (FND) table in the APPLSYS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition and setup information for individual key flexfield segments, together with the mapping between physical table columns and those segments. Every key flexfield structure registered in FND_ID_FLEX_STRUCTURES is decomposed into one or more rows in this table, one per segment, so the table effectively encodes the segment-level configuration of the Accounting Flexfield, the Item Flexfield, and all other key flexfields across the E-Business Suite.

The object is documented with 26 columns and is classified heuristically as hub-leaning in a Data Vault modeling sense. In practice, the natural composite identifier formed by application, flexfield code, flexfield number, and column name behaves much like a hub business key, while attributes such as display flags, default values, and security flags would typically be modeled as satellite attributes. This classification is a modeling suggestion only, and should be validated against the specific integration or warehouse design.

Key Information Stored

The primary key, FND_ID_FLEX_SEGMENTS_PK, is a composite of APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, and APPLICATION_COLUMN_NAME. The two documented unique indexes, FND_ID_FLEX_SEGMENTS_U1 and FND_ID_FLEX_SEGMENTS_U2, add ZD_EDITION_NAME to those columns; U2 substitutes SEGMENT_NAME for APPLICATION_COLUMN_NAME, enforcing that each segment name within a structure is unique.

  • APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM — identify the owning application and the specific key flexfield structure to which the segment belongs.
  • APPLICATION_COLUMN_NAME — the physical table column to which the segment is mapped, such as SEGMENT1.
  • SEGMENT_NAME — the business-facing name of the segment (for example, Company or Cost Center).
  • SEGMENT_NUM — the ordinal position of the segment within the structure.
  • FLEX_VALUE_SET_ID — foreign key to FND_FLEX_VALUE_SETS, determining the values the segment may accept.
  • ENABLED_FLAG, REQUIRED_FLAG, DISPLAY_FLAG — control whether the segment is active, mandatory, and visible.
  • DISPLAY_SIZE — the display width of the segment in the client.
  • SECURITY_ENABLED_FLAG — indicates whether value-set security applies to the segment.
  • DEFAULT_TYPE and DEFAULT_VALUE — define defaulting behaviour for the segment.
  • RANGE_CODE and ADDITIONAL_WHERE_CLAUSE — restrict the valid value range at runtime.
  • FLEX_VALUE_SET_ID, LAST_UPDATE_DATE, CREATED_BY — standard audit and referential columns.
  • ZD_EDITION_NAME — supports edition-based redefinition used in 12.2 online patching.

Common Use Cases and Queries

FND_ID_FLEX_SEGMENTS is queried whenever the segment layout of a key flexfield must be resolved, for example to confirm the column-to-segment mapping before writing accounting or item interfaces, or to report which value sets a flexfield uses.

The following pattern lists the enabled segments of a structure in display order:

  • SELECT APPLICATION_COLUMN_NAME, SEGMENT_NAME, SEGMENT_NUM, FLEX_VALUE_SET_ID FROM APPLSYS.FND_ID_FLEX_SEGMENTS WHERE APPLICATION_ID = :app AND ID_FLEX_CODE = :code AND ID_FLEX_NUM = :num AND ENABLED_FLAG = 'Y' ORDER BY SEGMENT_NUM;
  • Joining to FND_FLEX_VALUE_SETS on FLEX_VALUE_SET_ID resolves validation details for each segment.
  • Joining to FND_ID_FLEX_STRUCTURES on APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM returns the structure and title context.
  • Filtering on REQUIRED_FLAG identifies mandatory segments for interface validation logic.

Typical reporting uses include tracing where a value set is applied across flexfields, documenting segment configuration for audit or migration, and diagnosing missing default or range settings on a segment.

Related Objects

  • FND_ID_FLEX_STRUCTURES — parent structure definition; joined on APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM.
  • FND_FLEX_VALUE_SETS — referenced through FLEX_VALUE_SET_ID.
  • FND_ID_FLEX_SEGMENTS_TL — translation table keyed on APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, APPLICATION_COLUMN_NAME.
  • FND_SEGMENT_ATTRIBUTE_VALUES — stores per-segment attribute values, joined on the same four key columns.
  • FND_FLEX_VALIDATION_RULES — references the table for error segment column definitions.
  • FND_FLEXBUILDER_PARAMETERS — references the flexfield and column combination.