Search Results gl_entity_budgets




Overview
Explore in AI Chat

Overview

The GL_ENTITY_BUDGETS table is a core data object within the Oracle E-Business Suite General Ledger (GL) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to enforce budgetary control by defining which budget organizations, or entities, are "frozen" for specific budget versions. This mechanism is critical for the budget hierarchy and approval workflow, ensuring that once a budget is finalized for a particular organizational unit, further modifications are prevented until an appropriate unfreeze action is taken. The table acts as a junction or intersection table, maintaining the many-to-many relationship between budget entities and budget versions to track their freeze status.

Key Information Stored

The table's structure is defined by a composite primary key, which consists of two critical foreign key columns. The BUDGET_ENTITY_ID column stores the unique identifier for a budget organization, linking directly to the GL_BUDGET_ENTITIES table. The BUDGET_VERSION_ID column stores the unique identifier for a specific budget version, linking to the GL_BUDGET_VERSIONS table. The presence of a record in this table for a given pair of these IDs signifies that the specified budget entity is frozen for that particular budget version. The table does not typically contain additional descriptive columns; its existence itself is the data point indicating the freeze.

Common Use Cases and Queries

The primary use case is managing and reporting on the freeze status of budgets across the organizational hierarchy. System administrators and financial controllers use this data to validate budget entry and ensure compliance. A common reporting requirement is to list all frozen entities for a given budget. This can be achieved with a query such as:

  • SELECT geb.name budget_entity, gbv.budget_name, gbv.version_num FROM gl_entity_budgets gleb, gl_budget_entities geb, gl_budget_versions gbv WHERE gleb.budget_entity_id = geb.budget_entity_id AND gleb.budget_version_id = gbv.budget_version_id AND gbv.budget_name = '&BUDGET_NAME';

Conversely, to check if a specific entity is frozen for any budget, one would query for its BUDGET_ENTITY_ID. The table is also central to the application's logic when a user attempts to enter or adjust budget amounts, as the system checks this table to prevent updates against frozen entity-version combinations.

Related Objects

GL_ENTITY_BUDGETS is intrinsically linked to two master tables via foreign key constraints, forming the backbone of the budget freeze architecture.

  • GL_BUDGET_ENTITIES: This table defines the budget organizations within the system. The relationship is established through the GL_ENTITY_BUDGETS.BUDGET_ENTITY_ID column, which references GL_BUDGET_ENTITIES.BUDGET_ENTITY_ID.
  • GL_BUDGET_VERSIONS: This table stores the definitions for different budget versions. The relationship is established through the GL_ENTITY_BUDGETS.BUDGET_VERSION_ID column, which references GL_BUDGET_VERSIONS.BUDGET_VERSION_ID.

These relationships ensure referential integrity, meaning a freeze record cannot exist for a budget entity or version that has been deleted. All interactions with freeze status via the application's user interface ultimately manipulate records in this junction table.