Search Results gl_cons_segment_map_v

Overview

The APPS.GL_CONS_SEGMENT_MAP_V view is a General Ledger (GL) dictionary object that exposes consolidation segment mapping definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM description is annotated "10SC ONLY," indicating that the view is intended exclusively for the 10SC source consolidation product rather than for general ledger reporting at large. The view denormalizes the physical segment-map table (GL_SEGMENT_MAP_CONS_V) by joining it to flexfield segment definitions, value set metadata, and lookup values, thereby presenting human-readable segment names, value-set attributes, and a decoded segment map type. Because the searched column, SEGMENT_MAP_ID, functions as the primary unique key of this view, it is the natural correlation point for consolidation mapping rows when joining to other consolidation tables or to the underlying base entities. The view is a read-only presentation layer; no data is inserted, updated, or deleted through it.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over four referenced objects:

• GL_SEGMENT_MAP_CONS_V (VIEW) — supplies the driving rows and most of the exposed columns, aliased as MAPV, including ROW_ID, SEGMENT_MAP_ID, COA_MAPPING_ID, the from/to value set and column names, SEGMENT_MAP_TYPE, SINGLE_VALUE, PARENT_ROLLUP_VALUE, CONTEXT, ATTRIBUTE1 through ATTRIBUTE5, and the standard WHO audit columns.
• FND_ID_FLEX_SEGMENTS (SYNONYM) — joined twice (FFS1 and FFS2) against APPLICATION_ID = 101 and ID_FLEX_CODE = 'GL#'. The FFS1 join is inner on TO_CHART_OF_ACCOUNTS_ID and TO_APPLICATION_COLUMN_NAME; the FFS2 join is outer on FROM_CHART_OF_ACCOUNTS_ID and FROM_APPLICATION_COLUMN_NAME, yielding TO_SEGMENT_NAME/TO_SEGMENT_NUM and FROM_SEGMENT_NAME/FROM_SEGMENT_NUM respectively.
• GL_LOOKUPS (VIEW) — joined on LOOKUP_TYPE = 'SEGMENT_MAP_TYPE' and LOOKUP_CODE = SEGMENT_MAP_TYPE to provide the SEGMENT_MAP_TYPE_DISPLAY meaning.
• FND_FLEX_VALUE_SETS (SYNONYM) — joined on FLEX_VALUE_SET_ID = TO_VALUE_SET_ID to supply VALIDATION_TYPE.

Key Columns

• SEGMENT_MAP_ID — primary identifier for a segment mapping; the value most commonly used to look up individual mappings.
• ROW_ID — row identifier from the underlying consolidation segment-map view.
• MAPPING_ID — the COA_MAPPING_ID, linking this segment map to its parent chart-of-accounts mapping definition.
• TO_VALUE_SET_ID / TO_APPLICATION_COLUMN_NAME / TO_SEGMENT_NAME / TO_SEGMENT_NUM — describe the target value set and target GL segment.
• FROM_VALUE_SET_ID / FROM_APPLICATION_COLUMN_NAME / FROM_SEGMENT_NAME / FROM_SEGMENT_NUM — describe the source value set and segment; the outer join permits unmapped sources to appear with null segment names.
• SEGMENT_MAP_TYPE / SEGMENT_MAP_TYPE_DISPLAY — the mapping type code and its decoded lookup meaning.
• SINGLE_VALUE — indicates whether the mapping resolves to a single source value or a range/hierarchy.
• PARENT_ROLLUP_VALUE — rollup parent used in parent-child consolidation mapping.
• VALIDATION_TYPE — validation type of the target value set.
• CONTEXT, ATTRIBUTE1–ATTRIBUTE5 — descriptive flexfield context and attribute values.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically queried during consolidation setup and diagnostics to verify that source and target segments resolve correctly. A typical lookup by primary key is:

• SELECT segment_map_id, mapping_id, from_segment_name, to_segment_name, segment_map_type_display, single_value FROM apps.gl_cons_segment_map_v WHERE segment_map_id = :p_segment_map_id;
• To list all mappings for a parent COA mapping: SELECT segment_map_id, to_segment_name, from_segment_name FROM apps.gl_cons_segment_map_v WHERE mapping_id = :p_mapping_id ORDER BY to_segment_num;
• To inspect the target value sets and their validation: SELECT segment_map_id, to_segment_name, to_value_set_id, validation_type FROM apps.gl_cons_segment_map_v WHERE to_value_set_id = :p_value_set_id;

Because the object is documented as "10SC ONLY," queries should be confined to consolidation-related reporting and integration, and results should not be treated as a general-purpose GL segment cross-reference.