Search Results to_segment_name




Overview
Explore in AI Chat

Overview

APPS.GL_CONS_SEGMENT_ACTIONS_V is a supplementary view in the Oracle E-Business Suite General Ledger module, owned by the APPS schema and registered under FND Design Data as SQLGL.GL_CONS_SEGMENT_ACTIONS_V. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view type is classified as a supplementary view used to simplify forms coding, meaning it exists primarily to support the Oracle Forms-based Consolidation user interface rather than to serve as a general-purpose reporting or integration object.

The view exposes the segment-level mapping rules that govern how chart of accounts segments are translated during a consolidation or elimination run. It surfaces the relationship between a source ("from") segment and a target ("to") segment within a consolidation mapping, along with the flexfield and value set metadata needed to resolve each segment. Because it is a forms-support view, Oracle explicitly warns that querying or altering data through it is not recommended, and that its definition may change dramatically in subsequent minor or major releases. The user search term "from_segment_num" corresponds directly to the FROM_SEGMENT_NUM column, which identifies the ordinal position of the source segment in the source chart of accounts.

Underlying Base Objects

The view is defined over three documented base objects. GL_CONS_SEGMENT_MAP, referenced as a synonym, is the principal consolidation mapping table that stores the segment mapping definitions themselves. FND_ID_FLEX_SEGMENTS, also referenced as a synonym, is the Oracle Application Object Library table that defines the individual segments of an accounting flexfield, providing segment names, segment numbers, and flexfield identifiers. GL_CONS_SEGMENT_ACTIONS_PKG is the consolidation segment actions PL/SQL package, which participates in the view's dependencies and supplies the procedural logic that the forms layer invokes. In the documented dependency graph, APPS.GL_CONS_SEGMENT_ACTIONS_V is not referenced by any other database object, confirming that it is a terminal presentation-layer view rather than an intermediate object consumed by further database code.

Key Columns

Common Use Cases and Queries

The principal use case is diagnostic and reference: understanding how consolidation mappings translate source segments to target segments, and confirming which source segment numbers and value sets participate in each mapping. Because Oracle advises against direct querying, any use should be read-only and treated as informational.

A representative query filtering by the searched column is:

  • SELECT SEGMENT_MAP_ID, MAPPING_ID, FROM_SEGMENT_NUM, FROM_SEGMENT_NAME, TO_SEGMENT_NUM, TO_SEGMENT_NAME, SINGLE_VALUE FROM APPS.GL_CONS_SEGMENT_ACTIONS_V WHERE FROM_SEGMENT_NUM = :p_segment_num;
  • SELECT MAPPING_ID, SEGMENT_MAP_TYPE, FROM_SEGMENT_NAME, TO_SEGMENT_NAME FROM APPS.GL_CONS_SEGMENT_ACTIONS_V ORDER BY MAPPING_ID, FROM_SEGMENT_NUM;

For production reporting, join the underlying GL_CONS_SEGMENT_MAP and FND_ID_FLEX_SEGMENTS tables directly rather than relying on this view, since its columns and joins are subject to change across releases.