Results for “fnd_id_segment_name_ap_v”

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

Overview

FND_ID_SEGMENT_NAME_AP_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Payables (AP) product family and is documented in ETRM as an object originally introduced for Release 10SC. The view exposes a summarized list of enabled key flexfield segment names for the General Ledger chart of accounts associated with the Payables system's set of books.

Functionally, the view answers a narrow but recurring question: which accounting flexfield segments are enabled for the ledger currently configured in Payables, and in what order do they appear? It derives this information from the key flexfield definition tables rather than from transaction or balance data, making it a metadata-oriented view useful for reporting headers, validation logic, and integration routines that must present or interpret the accounting flexfield structure dynamically.

A notable characteristic is that the view is not restricted by ledger in the sense of exposing all ledgers; instead, it pins itself to the single set of books identified by AP_SYSTEM_PARAMETERS. In multi-org or multi-ledger implementations, this behavior means the result set reflects only the ledger tied to the Payables system parameters record, which is a critical constraint to understand before relying on the view for cross-ledger reporting.

Underlying Base Objects

The view is defined over three documented referenced objects: FND_ID_FLEX_SEGMENTS (exposed as a synonym), AP_SYSTEM_PARAMETERS (synonym), and GL_SETS_OF_BOOKS (view). The core logic performs a self-join of FND_ID_FLEX_SEGMENTS, aliased A and B, filtered to enabled segments (ENABLED_FLAG = 'Y') within the same ID_FLEX_CODE and ID_FLEX_NUM. The join condition A.SEGMENT_NUM >= B.SEGMENT_NUM drives a cumulative count, producing a running segment position for each segment name.

The result is further constrained to the Accounting Flexfield by the literal filter A.ID_FLEX_CODE = 'GL#'. The ID_FLEX_NUM is supplied by a scalar subquery joining GL_SETS_OF_BOOKS to AP_SYSTEM_PARAMETERS on SET_OF_BOOKS_ID, returning GL.CHART_OF_ACCOUNTS_ID. This linkage is what binds the flexfield definition to the ledger configured for Payables.

Key Columns

• SEGMENT_NAME — The name of the enabled accounting flexfield segment (for example, Company, Cost Center, Account).
• SEGMENT_NUM — A cumulative count derived from the self-join that effectively represents the ordinal position or segment number of the segment within the enabled structure.

The grouping is performed on ID_FLEX_CODE, ID_FLEX_NUM, and SEGMENT_NAME, so the output contains one row per enabled segment name for the qualified chart of accounts.

Common Use Cases and Queries

Typical scenarios include generating dynamic column headers for accounting reports, validating that a required segment is enabled before posting, and populating segment prompts in custom concurrent programs or forms. A representative query is:

SELECT segment_name, segment_num FROM apps.fnd_id_segment_name_ap_v ORDER BY segment_num;

Because the view restricts to the ledger referenced by AP_SYSTEM_PARAMETERS, callers should not expect it to enumerate segments for every ledger in the instance. Where multi-ledger segment metadata is required, querying FND_ID_FLEX_SEGMENTS directly with an explicit CHART_OF_ACCOUNTS_ID is the appropriate alternative.