Search Results gl_budget_frozen_ranges




Overview
Explore in AI Chat

Overview

The GL_BUDGET_FROZEN_RANGES table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module, specifically for the budgeting functionality in releases 12.1.1 and 12.2.2. It serves a critical control function by defining specific ranges of accounting flexfield (code combination) segments that are restricted from budget entry or modification. This "freezing" mechanism ensures data integrity by preventing changes to budget amounts for designated accounts, either for a specific budget version or across an entire budget organization (entity). Its role is to enforce budgetary discipline and audit trails during the budget preparation and maintenance cycles.

Key Information Stored

The table stores the definitions of frozen account ranges. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal its essential structure. The primary key is the RANGE_ID, a unique identifier for each frozen range record. Two critical foreign keys define the scope of the freeze: BUDGET_VERSION_ID links to the GL_BUDGET_VERSIONS table, applying the freeze to a specific budget version, and BUDGET_ENTITY_ID links to the GL_BUDGET_ENTITIES table, applying it to an entire budget organization. The table must also contain columns to define the actual account range, typically segment-specific columns like SEGMENT_LOW and SEGMENT_HIGH for the relevant flexfield structure, along with standard WHO columns (CREATED_BY, CREATION_DATE, etc.) for auditing.

Common Use Cases and Queries

A primary use case is generating a report of all frozen accounts for audit or troubleshooting purposes, particularly when users encounter errors during budget entry. System administrators may query this table to verify or modify freeze rules during a budget cycle. A common diagnostic query joins to related budget tables to provide context. For example, to list all frozen ranges for a specific budget version:

  • SELECT bvr.range_id, bev.name budget_version, bee.name budget_entity, bvr.segment1_low, bvr.segment1_high FROM gl_budget_frozen_ranges bvr, gl_budget_versions bev, gl_budget_entities bee WHERE bvr.budget_version_id = bev.budget_version_id AND bvr.budget_entity_id = bee.budget_entity_id AND bev.name = '&BUDGET_VERSION_NAME';

Another key use is within the application's validation logic itself; before posting a budget line, the system queries this table to check if the account combination falls within any defined frozen range for the relevant version or entity.

Related Objects

The table maintains defined foreign key relationships with two central budget setup tables, as documented in the ETRM metadata:

  • GL_BUDGET_VERSIONS: Joined via GL_BUDGET_FROZEN_RANGES.BUDGET_VERSION_ID = GL_BUDGET_VERSIONS.BUDGET_VERSION_ID. This links a frozen range to a specific budget version.
  • GL_BUDGET_ENTITIES: Joined via GL_BUDGET_FROZEN_RANGES.BUDGET_ENTITY_ID = GL_BUDGET_ENTITIES.BUDGET_ENTITY_ID. This links a frozen range to a budget organization.

These relationships ensure referential integrity, meaning a frozen range cannot exist without being associated with a valid budget version or entity. The table is also referenced by the application's budgeting forms and underlying PL/SQL logic that enforces the freeze during data entry.