Search Results segment_map_type_display

Overview

APPS.GL_CONS_SEGMENT_MAP_V is a consolidation-oriented reporting view in the Oracle E-Business Suite General Ledger module, documented in ETRM for releases 12.1.1 and 12.2.2. It exposes the segment-level mapping definitions that drive chart of accounts mapping between a source and a target chart of accounts, as used by consolidation, elimination, and transfer processes. Each row represents a single segment-to-segment correspondence within a parent mapping (a COA_MAPPING_ID), enriched with descriptive attributes such as segment names, segment numbers, validation type, and the user-facing mapping type meaning.

The view is a presentation and decoding layer: rather than forcing report authors and integration developers to resolve lookup codes and key flexfield segment numbers themselves, it joins the underlying mapping data to FND_ID_FLEX_SEGMENTS, FND_FLEX_VALUE_SETS, and GL_LOOKUPS so that the result set is immediately readable. The specific column the user searched for, SEGMENT_MAP_TYPE_DISPLAY, is produced by decoding the SEGMENT_MAP_TYPE lookup code against the SEGMENT_MAP_TYPE lookup type in GL_LOOKUPS. This makes the view particularly popular in value-set-driven Flexfields, BI Publisher reports, OAF/Forms extensions, and interface extracts where a human-readable mapping type label is required.

Underlying Base Objects

The view is defined over four documented objects:

• GL_SEGMENT_MAP_CONS_V (aliased MAPV) — the principal source, supplying the mapping row identity, segment map type, to/from value sets and columns, chart of accounts IDs, single value, rollup and DFF attribute columns. This is a view over the consolidation segment mapping table.
• FND_ID_FLEX_SEGMENTS (aliased FFS1, FFS2) — the key flexfield segment definitions for application 101 (General Ledger) and structure code GL#. FFS1 resolves the to segment name and number; FFS2 resolves the from segment name and number using an outer join, since the from-side is optional in some mapping configurations.
• GL_LOOKUPS (aliased L) — the GL lookup view. Joined on lookup_type = 'SEGMENT_MAP_TYPE' and lookup_code = mapv.SEGMENT_MAP_TYPE to derive SEGMENT_MAP_TYPE_DISPLAY from MEANING.
• FND_FLEX_VALUE_SETS (aliased FVS) — joined on flex_value_set_id = mapv.to_value_set_id to supply the VALIDATION_TYPE of the target value set.

Key Columns

• ROW_ID, SEGMENT_MAP_ID, MAPPING_ID — identifiers for the mapping row and its parent chart of accounts mapping.
• TO_VALUE_SET_ID, TO_APPLICATION_COLUMN_NAME, TO_SEGMENT_NAME, TO_SEGMENT_NUM — the target value set, column, and resolved segment definition.
• FROM_VALUE_SET_ID, FROM_APPLICATION_COLUMN_NAME, FROM_SEGMENT_NAME, FROM_SEGMENT_NUM — the corresponding source-side attributes (may be null).
• SEGMENT_MAP_TYPE and SEGMENT_MAP_TYPE_DISPLAY — the coded mapping type and its decoded meaning, the latter sourced from GL_LOOKUPS.MEANING.
• SINGLE_VALUE, PARENT_ROLLUP_VALUE — control values governing how the mapping resolves a segment.
• VALIDATION_TYPE — validation type of the to-side value set, from FND_FLEX_VALUE_SETS.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus CONTEXT and ATTRIBUTE1–ATTRIBUTE5 DFF columns.

Common Use Cases and Queries

Typical uses include: auditing which chart of accounts mapping rules are active, building consolidation mapping reports with readable segment and type labels, and diagnosing elimination or transfer mapping failures. A representative query retrieves the decoded mapping type and segment details for a given mapping:

• SELECT mapping_id, from_segment_name, to_segment_name, segment_map_type, segment_map_type_display, single_value
• FROM apps.gl_cons_segment_map_v
• WHERE mapping_id = :p_mapping_id
• ORDER BY to_segment_num;

To list all distinct mapping types with their display meanings, use SELECT DISTINCT segment_map_type, segment_map_type_display FROM apps.gl_cons_segment_map_v ORDER BY 1;. When filtering by value set validation, join on validation_type to isolate independent or dependent value set segments. Because the view relies on the key flexfield structure code GL#, it reflects the current segment configuration of both the from and to chart of accounts.