Search Results gl_budget_entities




Overview
Explore in AI Chat

Overview

The GL_BUDGET_ENTITIES table is a core data definition table within the Oracle E-Business Suite General Ledger (GL) module, serving as the master repository for budget organization definitions. In the context of Oracle EBS 12.1.1 and 12.2.2, it is the foundational object for establishing and managing budget entities, which are distinct organizational units created specifically for budgeting and planning purposes. A budget entity is a logical grouping of accounts and other dimensions, enabling the creation and maintenance of multiple, independent budgets within a single ledger. This structure is critical for supporting complex financial planning, allowing organizations to segregate budget data (e.g., for different departments, projects, or scenarios) from actual financial transactions while maintaining a coherent chart of accounts.

Key Information Stored

The table stores the essential attributes that define a budget entity. The primary identifier is the BUDGET_ENTITY_ID, a system-generated unique key. The NAME column holds the user-defined name of the budget entity, which must be unique within its associated ledger. The LEDGER_ID is a mandatory foreign key that ties the budget entity to a specific primary ledger in the GL_LEDGERS table, establishing the legal and accounting context. Other significant columns include REQUEST_ID, which links to the FND_CONCURRENT_REQUESTS table to track the concurrent request that created or updated the entity, and various descriptive columns for status, creation, and last update details that are standard in Oracle EBS tables.

Common Use Cases and Queries

This table is central to any process involving budget setup, inquiry, or maintenance. A common reporting requirement is to list all budget entities within a specific ledger for administration or audit purposes. A typical query would join to GL_LEDGERS to display the ledger name.

SELECT gbe.NAME budget_entity,
       gbe.BUDGET_ENTITY_ID,
       gl.NAME ledger_name
FROM GL.GL_BUDGET_ENTITIES gbe,
     GL.GL_LEDGERS gl
WHERE gbe.LEDGER_ID = gl.LEDGER_ID
AND gl.NAME = '&LEDGER_NAME'
ORDER BY gbe.NAME;

Another critical use case is during the budget upload process via the GL Budget Interface, where the BUDGET_ENTITY_ID must be correctly referenced in the GL_BUDGET_INTERFACE table to ensure data is loaded to the correct budget organization. System administrators may also query this table to investigate data integrity issues or to understand the relationships between budget entities and their associated budget balances and assignments.

Related Objects

The GL_BUDGET_ENTITIES table has extensive relationships with other budget-related tables, as documented by its foreign key constraints. It is the parent table for numerous child tables that store transactional and assignment data, creating a central hub for the budget architecture.

  • GL_ENTITY_BUDGETS: Stores the budget balances (amounts) for each budget entity. Joined via BUDGET_ENTITY_ID.
  • GL_BUDGET_ASSIGNMENTS / GL_BUDGET_ASSIGNMENT_RANGES: Define which accounts, cost centers, or other segment value ranges are included within a specific budget entity. Joined via BUDGET_ENTITY_ID.
  • GL_BUDGET_INTERFACE / GL_BUDGET_INTERIM / GL_BUDGET_RANGE_INTERIM: Staging and interface tables for loading budget data and budget ranges. Joined via BUDGET_ENTITY_ID.
  • GL_BUDGET_FROZEN_RANGES: Tracks periods where budget data for an entity is locked from changes. Joined via BUDGET_ENTITY_ID.
  • GL_LEDGERS (implied): The parent ledger definition, joined via the LEDGER_ID column.
  • FND_CONCURRENT_REQUESTS: Tracks the process that created the budget entity record, joined via REQUEST_ID.