Search Results all_ind_columns




Overview
Explore in AI Chat

Overview

FND_INDEXED_SEGS_V is an APPS-owned database view in Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. The view exists to answer a narrow but important metadata question: which segments of the GL Accounting Flexfield (ID_FLEX_CODE = 'GL#') are physically indexed as the leading column of an index on the GL_CODE_COMBINATIONS table. Because the Accounting Flexfield is the backbone of the General Ledger chart of accounts, performance of queries and integrations that filter on a single balancing or cost center segment depends heavily on whether that segment is indexed. This view exposes that fact declaratively, allowing reporting, diagnostics, and validation logic to identify indexed segments without hard-coding index definitions. It is a metadata/configuration view rather than a transactional one; it returns a small, slowly changing result set reflecting the intersection of Flexfield segment definitions and physical index columns.

Underlying Base Objects

The view is defined over two referenced base objects, both resolved through synonyms in the APPS schema:

The correlation restricts the result to enabled GL segments whose column occupies the first position of an index on GL_CODE_COMBINATIONS. This is the documented linkage the user implicitly sought when searching for "all_ind_columns"; that dictionary view is the second half of the join that makes this view meaningful.

Key Columns

  • SEGMENT_NAME — the name of the Accounting Flexfield segment (for example, Company, Cost Center, Account), sourced from FND_ID_FLEX_SEGMENTS.
  • APPLICATION_COLUMN_NAME — the underlying GL_CODE_COMBINATIONS column name that stores the segment value; this is the column matched against ALL_IND_COLUMNS.COLUMN_NAME.
  • ID_FLEX_NUM — the numeric identifier of the flexfield definition, useful for joining back to key flexfield metadata such as FND_ID_FLEXS and FND_ID_FLEX_STRUCTURES.

The view does not expose index name, uniqueness, or column ordering beyond the implicit position-one constraint, so consumers requiring index names must query ALL_IND_COLUMNS or ALL_INDEXES directly.

Common Use Cases and Queries

Typical uses include performance diagnostics, indexing gap analysis, and validation of chart-of-accounts design. A simple listing follows:

  • SELECT SEGMENT_NAME, APPLICATION_COLUMN_NAME, ID_FLEX_NUM FROM APPS.FND_INDEXED_SEGS_V;
  • Join to segment metadata to report attributes of indexed segments, e.g. SELECT v.SEGMENT_NAME, s.FLEX_VALUE_SET_ID FROM APPS.FND_INDEXED_SEGS_V v, APPS.FND_ID_FLEX_SEGMENTS s WHERE v.APPLICATION_COLUMN_NAME = s.APPLICATION_COLUMN_NAME AND s.ID_FLEX_CODE = 'GL#'.
  • Compare against all enabled GL segments to identify unindexed segments that may cause full-table scans on GL_CODE_COMBINATIONS.

Because the view is a metadata join, it is read-only, safe for concurrent querying, and requires no special initialization beyond access to the APPS synonyms. Results should be interpreted per the active GL chart of accounts and the physical indexes actually present in the database.