Search Results from_segment_num

Overview

The view GL_IEA_SEGMENT_MAP_V is a General Ledger (GL) reporting object that exposes the segment mapping definitions used by Oracle's Intercompany/Inter-Entity Accounting (IEA) engine. It denormalizes the raw configuration held in GL_IEA_SEGMENT_MAP by joining each mapping row to the corresponding key flexfield segment definitions in FND_ID_FLEX_SEGMENTS, so that consumers receive human-readable segment names and numbers rather than the internal application column identifiers stored in the base table.

Its role is primarily diagnostic and reporting-oriented. Rather than maintaining mappings, it presents a read-only, query-friendly shape of how a source ("from") segment of one chart of accounts is mapped to a target ("to") segment of another chart of accounts during intercompany processing. Note that the ETRM metadata records this view as "Not implemented in this database" and lists no documented referenced base objects; the view text supplied in the documentation nevertheless defines the intended structure, so the description here is grounded in that definition.

Underlying Base Objects

The view is defined over three objects. The driving table is GL_IEA_SEGMENT_MAP (aliased SEG), which stores each intercompany segment mapping rule. It is joined to FND_ID_FLEX_SEGMENTS twice:

• FND_ID_FLEX_SEGMENTS FD1 — an inner join resolving the target segment. It is constrained to APPLICATION_ID = 101 (the GL application), ID_FLEX_CODE = 'GL#', and a chart-of-accounts ID_FLEX_NUM selected by GENERATE_TYPE_CODE: the receiver's chart for standard mappings, the sender's chart for 'SC' (single-value / copy) mappings. It matches on TO_APPLICATION_COLUMN_NAME.
• FND_ID_FLEX_SEGMENTS FD2 — an outer join ((+) notation) resolving the source segment against the sender's chart of accounts, keyed on FROM_APPLICATION_COLUMN_NAME. Because it is an outer join, rows where no source segment applies (for example, single-value mappings) are preserved.

Key Columns

• SEGMENT_MAP_ID — Primary identifier of the mapping rule.
• ROW_ID — ROWID from the base table, useful for distinct row identification.
• GENERATE_TYPE_CODE — Determines mapping behavior ('SC' for single-value generation, blank for standard segment-to-segment).
• SENDER_CHART_OF_ACCT_ID, RECEIVER_CHART_OF_ACCT_ID — Source and destination charts of accounts.
• FROM_APPLICATION_COLUMN_NAME, TO_APPLICATION_COLUMN_NAME — The underlying flexfield column identifiers.
• FROM_SEGMENT_NAME, FROM_SEGMENT_NUM — Source segment name and number, derived via DECODE; both are blanked (empty string) when GENERATE_TYPE_CODE = 'SC'.
• TO_SEGMENT_NAME, TO_SEGMENT_NUM — Target segment name and number resolved from FD1.
• SINGLE_VALUE — The literal value used when the rule is a single-value type.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — Descriptive flexfield columns carried through from the base table.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

This view is typically queried to audit or document intercompany account derivations, and to troubleshoot why a transaction mapped to an unexpected segment. A common request—matching the search term from_segment_num—is to list all mappings showing both source and target segment numbers:

SELECT segment_map_id,
       generate_type_code,
       from_segment_num,
       to_segment_num,
       single_value
FROM   gl_iea_segment_map_v
ORDER  BY segment_map_id;

To focus only on active segment-to-segment rules (excluding single-value rules, where from_segment_num is null/blank), filter on the generation type:

SELECT segment_map_id, from_segment_num, to_segment_num
FROM   gl_iea_segment_map_v
WHERE  generate_type_code <> 'SC';

Because FROM_SEGMENT_NUM is returned as a character field, comparisons against numeric segment positions should be made carefully, or the query restricted to the relevant chart of accounts via sender_chart_of_acct_id and receiver_chart_of_acct_id.