Search Results gl_cons_flexfield_map_high

Overview

GL_CONS_FLEXFIELD_MAP_HIGH is a reporting view in the Oracle E-Business Suite General Ledger module. Its purpose is narrow and specific: it exposes the high-range key flexfield segment columns (SEGMENT1_HIGH through SEGMENT30_HIGH) of the GL_CONS_FLEXFIELD_MAP table, along with the identifying and audit columns needed to make those segments meaningful. In consolidation and elimination processing, the parent (target) chart of accounts must be mapped against the child (source) accounts, and a mapping definition frequently describes a range of source or target accounts rather than a single discrete combination. This view surfaces the upper bound of such ranges, segment by segment, up to the maximum of thirty key flexfield segments supported by the Accounting Flexfield structure.

From a reporting and integration standpoint, the view acts as the "high" counterpart to the equivalent low-range view. Instead of returning individual code combination identifiers, it publishes the raw segment values that define the ceiling of each mapped range. Because the Accounting Flexfield may use as few as one and as many as thirty segments depending on configuration, the view materializes every segment position; unused positions remain null or unpopulated. ETRM metadata explicitly notes that this object is "Not implemented in this database," meaning it exists as a defined database object but is not necessarily instantiated in every environment. Developers querying it should confirm its presence and validity before relying on it in production code.

Underlying Base Objects

Although the ETRM metadata lists "Referenced base objects: none documented," the view text makes the relationship unambiguous: it selects directly from the GL_CONS_FLEXFIELD_MAP table. There are no joins, unions, or subqueries in the definition. The view is a pure column projection of a single base table, restricted to the high-range segment columns plus the surrounding key, audit, and descriptive flexfield columns.

This one-to-one projection means the view inherits the cardinality of GL_CONS_FLEXFIELD_MAP. Each row of the base table corresponds to exactly one row in the view, and there is no aggregation or filtering logic. The view therefore has no independent data of its own; it is entirely dependent on the parent table for content and integrity.

Key Columns

• FLEXFIELD_MAP_ID — Primary identifier of the flexfield map record; the join key back to the base table.
• CONSOLIDATION_ID — Identifies the consolidation definition to which the mapping belongs, linking the range to a specific consolidation or elimination run.
• TO_CODE_COMBINATION_ID — The target code combination that the range resolves to; this is the destination account for mapping purposes.
• SEGMENT1_HIGH through SEGMENT30_HIGH — The defining columns of the view. Each represents the upper bound segment value for the corresponding Accounting Flexfield segment position. SEGMENT30_HIGH is the last valid position; where a chart of accounts defines fewer than thirty segments, the higher positions are not used.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns supporting change tracking and attribution.
• ATTRIBUTE1 through ATTRIBUTE5, CONTEXT — Descriptive flexfield (DFF) columns allowing extendable, customer-defined attributes to be stored alongside the mapping.

Common Use Cases and Queries

The view is typically used to reconstruct or validate the upper bounds of consolidation account ranges. A common pattern joins the view to GL_CONS_FLEXFIELD_MAP to pair low and high bounds, or to the consolidation definition tables to trace which source ranges map to a given target account.

A basic existence and extraction query:

• SELECT FLEXFIELD_MAP_ID, CONSOLIDATION_ID, TO_CODE_COMBINATION_ID, SEGMENT1_HIGH, SEGMENT2_HIGH, SEGMENT3_HIGH FROM GL_CONS_FLEXFIELD_MAP_HIGH WHERE CONSOLIDATION_ID = :p_consolidation_id;

To locate the ceiling value for a specific segment position across a consolidation:

• SELECT FLEXFIELD_MAP_ID, SEGMENT30_HIGH FROM GL_CONS_FLEXFIELD_MAP_HIGH WHERE CONSOLIDATION_ID = :p_consolidation_id AND SEGMENT30_HIGH IS NOT NULL;

Because the view contains no joins, it is inexpensive to query and well suited to ad-hoc reporting, data extracts, and integration routines that require the high-end segment values in a form ready for comparison against transaction or balance data. When combining it with the low-range view, both can be joined on FLEXFIELD_MAP_ID to produce complete range definitions for reconciliation and audit reporting.