Search Results segment3_high

Overview

GL_BUDGET_ASSIGNMENT_RANGES_V is an APPS-owned view in the Oracle E-Business Suite General Ledger module, documented with the status VALID and a description of "10SC ONLY." It exposes budget assignment range definitions maintained in Oracle General Ledger, presenting the account segment low and high boundaries that define which accounting flexfield combinations fall within a given budget assignment range. In EBS 12.1.1 and 12.2.2, this view functions primarily as a reporting and integration layer, allowing external processes, custom reports, and inquiries to read range definitions in a denormalized, consumer-friendly form. It is particularly relevant to users investigating how budget ranges are scoped across the accounting flexfield, since it surfaces columns such as SEGMENT2_HIGH and its counterparts for every enabled segment position.

Underlying Base Objects

The view is defined over two documented referenced objects: GL_BUDGET_ASSIGNMENT_RANGES (referenced through a synonym) and GL_LOOKUPS (a view). GL_BUDGET_ASSIGNMENT_RANGES is the base table holding the actual range records, including ledger, budget entity, range identifier, sequence, currency, entry code, and the low and high values for each of the thirty segment positions. GL_LOOKUPS supplies the decoded meaning for the status code, aliased in the view text as SHOW_STATUS via the L3.MEANING column. The view therefore performs a straightforward join between the range table and the lookup view, projecting the base row identifier (BAR.ROWID as ROW_ID) alongside ledger and entity keys and the full set of segment boundary columns.

Key Columns

The view projects identity and control columns—LEDGER_ID, BUDGET_ENTITY_ID, RANGE_ID, and SEQUENCE_NUMBER—that together describe the ownership and ordering of each range. CURRENCY_CODE and ENTRY_CODE capture the currency and entry context of the range, while STATUS holds the coded value and SHOW_STATUS its human-readable meaning from GL_LOOKUPS. The range boundaries are then exposed as paired low/high columns for each segment position: SEGMENT1_LOW through SEGMENT30_LOW, and SEGMENT1_HIGH through SEGMENT30_HIGH. A user searching for "segment2_high" is looking at the upper bound of the second accounting flexfield segment within a given assignment range. SEGMENT2_HIGH must be read in conjunction with SEGMENT2_LOW to understand the inclusive span of that segment for the range.

Common Use Cases and Queries

Typical usage includes validating how budget ranges are scoped per ledger, auditing overlapping or malformed ranges, and feeding downstream allocation or reporting logic. The following query retrieves range boundaries for a specific ledger, focusing on the second segment:

• SELECT ledger_id, budget_entity_id, range_id, sequence_number, segment2_low, segment2_high, show_status FROM apps.gl_budget_assignment_ranges_v WHERE ledger_id = :ledger_id ORDER BY sequence_number;
• SELECT range_id, segment2_low, segment2_high FROM apps.gl_budget_assignment_ranges_v WHERE segment2_high IS NOT NULL AND show_status = 'Active';

Because the view is read-only and built on the assignment ranges table, all queries are safe for reporting workloads. Joining to GL_LEDGERS via LEDGER_ID and to budget entity definitions enriches results with descriptive names. Given the "10SC ONLY" designation, access may be restricted to certain configurations, so validation against the target instance is advisable before relying on it in production integrations.