Results for “gl_entity_budgets”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_ENTITY_BUDGETS is a General Ledger (GL) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that controls the freezing of budget organizations in relation to specific budget versions. Its documented purpose is to "freeze budget organizations for particular budgets," meaning it records which combinations of a budget entity (budget organization) and a budget version have been locked against further modification. This freeze mechanism enforces data integrity once a budget has been approved or finalized, preventing subsequent entries from altering an organization's budget balances.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is modeled as a link table. This is a reasonable modeling suggestion: the table does not hold descriptive attributes about a single business entity but rather resolves a many-to-many relationship between budget entities and budget versions. The intersection of these two dimensions is the core of its business meaning.

Key Information Stored

The table contains 14 documented columns, of which the most significant are the following:

• BUDGET_ENTITY_ID — Identifies the budget organization (budget entity) being frozen. This is a foreign key to GL_BUDGET_ENTITIES.
• BUDGET_VERSION_ID — Identifies the budget version to which the freeze applies. This is a foreign key to GL_BUDGET_VERSIONS.
• FROZEN_FLAG — Indicates whether the budget organization is currently frozen for the associated budget version, serving as the operative status indicator for the record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified the record and when.
• ATTRIBUTE1 through ATTRIBUTE5 and CONTEXT — The standard descriptive flexfield (DFF) columns, available for customer-specific extension of the freeze record.

The documented primary key is GL_ENTITY_BUDGETS_PK, a composite key on BUDGET_ENTITY_ID and BUDGET_VERSION_ID. The same two columns also form the unique index GL_ENTITY_BUDGETS_U1, confirming that the business key is the combination of budget entity and budget version, and that only one freeze record can exist per entity-version pairing. There is no separate single-column surrogate key documented; the composite of the two foreign keys serves as both the surrogate and business key candidate.

Common Use Cases and Queries

Typical scenarios include determining whether a budget organization may still receive budget entries, auditing which organizations have been locked for a given budget, and reporting freeze status across the organization hierarchy.

A representative query to list frozen budget organizations for a specific budget version:

• SELECT eb.BUDGET_ENTITY_ID, eb.BUDGET_VERSION_ID, eb.FROZEN_FLAG FROM GL_ENTITY_BUDGETS eb WHERE eb.BUDGET_VERSION_ID = :version_id AND eb.FROZEN_FLAG = 'Y';

A join-based query to retrieve descriptive names by resolving the foreign keys:

• SELECT be.NAME, bv.NAME, eb.FROZEN_FLAG FROM GL_ENTITY_BUDGETS eb, GL_BUDGET_ENTITIES be, GL_BUDGET_VERSIONS bv WHERE eb.BUDGET_ENTITY_ID = be.BUDGET_ENTITY_ID AND eb.BUDGET_VERSION_ID = bv.BUDGET_VERSION_ID;

These patterns support reconciliation and audit reports that verify which organizations are protected against budget modification before period close or budget approval cycles.

Related Objects

The following objects are the most significant references and dependencies for GL_ENTITY_BUDGETS, based on the documented foreign key relationships:

• GL_BUDGET_ENTITIES — Referenced via GL_ENTITY_BUDGETS.BUDGET_ENTITY_ID; supplies the budget organization definition.
• GL_BUDGET_VERSIONS — Referenced via GL_ENTITY_BUDGETS.BUDGET_VERSION_ID; supplies the budget version definition.
• GL_BUDGET_ENTITIES and GL_BUDGET_VERSIONS again appear as the paired foreign table endpoints in the documented relationship data, reinforcing that these two tables are the sole direct parents of the freeze link.
• The primary key GL_ENTITY_BUDGETS_PK and unique index GL_ENTITY_BUDGETS_U1 are the dependent constraint objects defined on this table.

Downstream, budget entry and approval processes in General Ledger consult this table indirectly through the budget entity and budget version components to enforce freeze rules, making it a supporting control table rather than a transactional fact source.