Search Results gl_cons_segment_actions_v




Overview
Explore in AI Chat

Overview

GL_CONS_SEGMENT_ACTIONS_V is a General Ledger (GL) consolidation view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents the segment-level mapping definitions used by the Global Consolidation System (GCS) to translate account segments from a source (from) chart of accounts into the corresponding segments of a target (to) chart of accounts. In practical terms, the view answers the question: "for a given parent mapping between two charts of accounts, how does each individual balancing or management segment in the source ledger map to a segment in the receiving ledger?"

The object is a view, not a table, and is therefore read-only. It is generated dynamically at query time, with context-sensitive values supplied by the GL_CONS_SEGMENT_ACTIONS_PKG package (notably GET_COA_MAPPING_ID, GET_TO_COA_ID, and GET_FROM_COA_ID). Because those package functions depend on session state established by the consolidation setup forms, the view is primarily intended for reporting, diagnostics, and integration use cases where the current mapping context has already been initialized.

Underlying Base Objects

According to the documented metadata, GL_CONS_SEGMENT_ACTIONS_V is defined over three referenced base objects:

The view therefore acts as a resolved join between flexfield segment metadata (FND_ID_FLEX_SEGMENTS) and consolidation mapping data (GL_CONS_SEGMENT_MAP), scoped by session context from the package. Note that the join to FFS2 and to GL_CONS_SEGMENT_MAP is outer (indicated by the (+) operator), while the join to FFS1 is effectively mandatory, so the view returns one row per enabled target COA segment even when no source mapping exists.

Key Columns

Because the view uses GROUP BY on COA_MAPPING_ID, SEGMENT_NAME, SEGMENT_NUM, and FLEX_VALUE_SET_ID, all non-grouped columns are wrapped in MAX aggregates, which means the view returns one consolidated row per target segment mapping context.

Common Use Cases and Queries

Typical uses include verifying that every enabled target segment has a corresponding mapping, auditing the mapping type used per segment, and extracting mapping definitions for migration or reconciliation. A representative query is:

  • List all segment mappings for the current consolidation context:
    SELECT TO_SEGMENT_NAME, FROM_SEGMENT_NAME, SEGMENT_MAP_TYPE, SINGLE_VALUE, LAST_UPDATE_DATE FROM APPS.GL_CONS_SEGMENT_ACTIONS_V ORDER BY TO_SEGMENT_NUM;
  • Find unmapped target segments:
    SELECT TO_SEGMENT_NAME, SEGMENT_MAP_TYPE FROM APPS.GL_CONS_SEGMENT_ACTIONS_V WHERE SEGMENT_MAP_TYPE = 'N';
  • Trace single-value mappings:
    SELECT TO_SEGMENT_NAME, SINGLE_VALUE FROM APPS.GL_CONS_SEGMENT_ACTIONS_V WHERE SEGMENT_MAP_TYPE = 'S';

Because the view depends on package-supplied context values, queries should be executed within the consolidation setup flow or after invoking GL_CONS_SEGMENT_ACTIONS_PKG to initialize GET_COA_MAPPING_ID and the related chart identifiers; otherwise TO_SEGMENT_NAME or FROM_SEGMENT_NAME may be null or the result set may be empty.