Search Results fnd_segment_attribute_values




Overview
Explore in AI Chat

Overview

The FND_SEGMENT_ATTRIBUTE_VALUES table is a core repository table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It serves as the central data store for flexfield qualifier values assigned to specific segments of key flexfield structures. A flexfield qualifier is an attribute that defines the meaning and functional behavior of a segment, such as identifying it as a Balancing Segment, Cost Center Segment, or Natural Account Segment. This table is essential for the correct configuration and operation of key flexfields, including the General Ledger Accounting Flexfield (GL#) and the Asset Key Flexfield (CAT#), by storing the specific qualifier-to-segment assignments for every active flexfield structure in the system.

Key Information Stored

The table's primary key uniquely identifies a qualifier assignment through a combination of columns that define the flexfield context and the specific segment. The APPLICATION_ID and ID_FLEX_CODE identify the flexfield application and its internal code (e.g., 101 for GL, 140 for FA). The ID_FLEX_NUM specifies the particular structure number within that flexfield. The APPLICATION_COLUMN_NAME identifies the database column (e.g., SEGMENT1, SEGMENT2) that holds the segment value for this structure. Finally, the SEGMENT_ATTRIBUTE_TYPE column stores the specific type of qualifier assigned, such as 'FA_COST_CTR' or 'GL_BALANCING'. The table's design enforces data integrity through foreign key relationships to the definitions of segments and qualifier types.

Common Use Cases and Queries

This table is primarily queried for configuration analysis, troubleshooting, and reporting on flexfield setups. A common use case is to generate a report of all segment qualifier assignments for a critical flexfield like the Accounting Flexfield to validate configuration against business requirements. Another typical scenario involves troubleshooting issues in modules like Assets or Payables where transaction posting fails due to missing or incorrect segment qualifier assignments. Developers and functional consultants often query this table to understand the underlying setup that drives application logic.

Sample Query: List Qualifiers for the Accounting Flexfield

  • SELECT fsav.application_column_name,
           fsav.segment_attribute_type,
           fifsv.segment_name
    FROM fnd_segment_attribute_values fsav,
         fnd_id_flex_structures_vl fifs,
         fnd_id_flex_segments_vl fifsv
    WHERE fsav.id_flex_code = 'GL#'
    AND fsav.application_id = 101
    AND fifs.application_id = fsav.application_id
    AND fifs.id_flex_code = fsav.id_flex_code
    AND fifs.id_flex_num = fsav.id_flex_num
    AND fifsv.application_id = fsav.application_id
    AND fifsv.id_flex_code = fsav.id_flex_code
    AND fifsv.id_flex_num = fsav.id_flex_num
    AND fifsv.application_column_name = fsav.application_column_name
    ORDER BY fsav.id_flex_num, fsav.application_column_name;

Related Objects

The FND_SEGMENT_ATTRIBUTE_VALUES table maintains documented foreign key relationships with two fundamental definition tables, ensuring its data is consistent with the overall flexfield metadata.

  • FND_ID_FLEX_SEGMENTS: This relationship ties each qualifier value record to the specific segment definition it modifies. The join is performed on the columns APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, and APPLICATION_COLUMN_NAME.
  • FND_SEGMENT_ATTRIBUTE_TYPES: This relationship validates that the SEGMENT_ATTRIBUTE_TYPE used is a defined and valid qualifier for the given flexfield. The join is performed on the columns APPLICATION_ID, ID_FLEX_CODE, and SEGMENT_ATTRIBUTE_TYPE.

These relationships are critical for maintaining a coherent flexfield configuration where qualifiers are only assigned to existing segments of valid types.