Results for “fnd_segment_attribute_values”

50+ results




Overview
Explore in AI Chat

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

Overview

FND_SEGMENT_ATTRIBUTE_VALUES 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 values of flexfield qualifiers assigned to individual segments within Key Flexfield (KFF) structures. In Oracle EBS, a key flexfield is defined by an ID_FLEX_CODE and a specific structure identified by ID_FLEX_NUM. Each structure is composed of one or more segments registered by the FND_ID_FLEX_SEGMENTS table. Qualifiers are segment-level properties—such as Balancing, Cost Center, Natural Account, or Intercompany—that convey functional meaning to the General Ledger, Oracle Subledgers, and other modules that consume the accounting flexfield. This table therefore acts as the persistence layer for the qualifier-to-segment mapping and is fundamental to how EBS interprets accounting, descriptive, and other key flexfields at runtime.

Under a heuristic Data Vault classification derived from the foreign-key structure, this object is best modeled as a link table. It captures the association between segments (via FND_ID_FLEX_SEGMENTS) and attribute types (via FND_SEGMENT_ATTRIBUTE_TYPES), together with the assigned value. This modeling suggestion emphasizes its role as a junction entity rather than a standalone hub or a purely descriptive satellite.

Key Information Stored

The documented physical schema contains twelve columns in the 12.2.2 ETRM metadata. The most significant include:

  • APPLICATION_ID — Identifies the application owning the key flexfield definition; first component of the primary key.
  • ID_FLEX_CODE — The key flexfield code (e.g., GL# for the Accounting Flexfield); part of the primary key.
  • ID_FLEX_NUM — The structure number that uniquely identifies the flexfield structure within the flexfield code; part of the primary key.
  • APPLICATION_COLUMN_NAME — The segment column name (e.g., SEGMENT1) that the qualifier applies to; part of the primary key.
  • SEGMENT_ATTRIBUTE_TYPE — The code identifying which qualifier is being set; part of the primary key and a foreign key to FND_SEGMENT_ATTRIBUTE_TYPES.
  • ATTRIBUTE_VALUE — The value assigned to the qualifier for that segment (typically a flag or code indicating whether the qualifier is enabled).
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns for audit tracking.
  • ZD_EDITION_NAME — Editioning column supporting Online Patching and edition-based redefinition in Release 12.2.

The surrogate primary key is FND_SEGMENT_ATTRIBUTE_VALUE_PK, defined on the combination of APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, APPLICATION_COLUMN_NAME, and SEGMENT_ATTRIBUTE_TYPE. The unique index FND_SEGMENT_ATTRIBUTE_VALS_U1 extends this set with ZD_EDITION_NAME, reflecting the business-key candidate used to enforce uniqueness across editions.

Common Use Cases and Queries

Developers and functional consultants query this table to determine which qualifiers are enabled on which segments of a given flexfield structure. A typical query retrieves all qualifiers for the Accounting Flexfield structure used by a ledger:

  • Diagnosing imbalance errors by verifying which segment carries the Balancing qualifier.
  • Reporting on qualifier configuration across all structures for a flexfield code before a patch or upgrade.
  • Validating multi-organization and intercompany setups by checking Intercompany and Natural Account qualifiers.
  • Extracting qualifier metadata for custom reporting or integration into external GL analytics.

A representative SQL pattern joins the table to FND_ID_FLEX_SEGMENTS on APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, and APPLICATION_COLUMN_NAME, filtering on ID_FLEX_CODE = 'GL#'. To resolve the qualifier name, it is joined to FND_SEGMENT_ATTRIBUTE_TYPES on APPLICATION_ID, ID_FLEX_CODE, and SEGMENT_ATTRIBUTE_TYPE. Because the table is keyed by structure, queries should always constrain on ID_FLEX_NUM to avoid returning qualifiers from inactive or legacy structures.

Related Objects

Several FND objects reference or depend on this table through documented foreign keys and business relationships:

  • FND_ID_FLEX_SEGMENTS — Parent of the segment definition; joined on APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, and APPLICATION_COLUMN_NAME.
  • FND_SEGMENT_ATTRIBUTE_TYPES — Defines the valid qualifier types; joined on APPLICATION_ID, ID_FLEX_CODE, and SEGMENT_ATTRIBUTE_TYPE.
  • FND_ID_FLEX_STRUCTURES — Defines the structure identified by ID_FLEX_NUM used throughout this table.
  • FND_FLEX_VALUES and FND_FLEX_VALUE_SETS — Consume segment qualifier definitions when validating flexfield values.
  • FND_KF_SEGMENTS_VL and related key flexfield views — Expose segment and qualifier metadata used by the Key Flexfield runtime APIs.
  • FND_FLEX_KEY_API (PL/SQL package) — Reads qualifier values during flexfield validation and derivation logic.