Search Results gl_budget_versions_uk1

Overview

The GL_BUDGET_VERSIONS table is a core repository for budget version definitions within the Oracle E-Business Suite General Ledger (GL) module. It serves as the master table for all distinct budget versions created across the enterprise, enabling sophisticated financial planning and control. Each record in this table represents a unique version of a budget, which is a critical component for comparative analysis, forecasting, and budgetary control processes. The table's integrity is maintained through its relationships with GL_BUDGET_TYPES and GL_BUDGETS, ensuring that every version is linked to a valid budget name and type. Its central role is evidenced by its extensive foreign key relationships with numerous transactional and balance tables, such as GL_BALANCES and GL_BC_PACKETS, which store actual budget amounts and encumbrances against these defined versions.

Key Information Stored

The table's primary identifier is the BUDGET_VERSION_ID, a system-generated sequence used as the primary key for efficient relational joins. Two other columns form a unique key (GL_BUDGET_VERSIONS_UK1), defining the essential attributes of a version: BUDGET_NAME and BUDGET_TYPE. This combination ensures uniqueness of a version name within a specific budget type. A significant structural column is CONTROL_BUDGET_VERSION_ID, which creates a self-referential foreign key within the same table. This relationship is fundamental for implementing control budgets, where one budget version (the control) is used to set limits or validate transactions posted against another related budget version, a core feature for budgetary control and funds checking.

Common Use Cases and Queries

This table is central to reporting and validating budget structures. A common administrative query lists all budget versions for a specific budget, often used for setup verification or audit trails. For budgetary control processes, identifying which budget versions are designated as control budgets is essential for configuration analysis. Furthermore, when troubleshooting funds checking errors or reviewing budget balances, joining GL_BUDGET_VERSIONS to GL_BALANCES or GL_BC_PACKETS is a standard pattern to retrieve human-readable budget names alongside financial data.

• Listing all versions for a budget: SELECT budget_version_id, last_update_date FROM gl_budget_versions WHERE budget_name = '&BUDGET_NAME' ORDER BY creation_date;
• Finding control budget relationships: SELECT v1.budget_name, v1.budget_version_id, v2.budget_version_id control_version_id FROM gl_budget_versions v1, gl_budget_versions v2 WHERE v1.control_budget_version_id = v2.budget_version_id(+);
• Reporting budget balances with version names: SELECT gbv.budget_name, gb.* FROM gl_balances gb, gl_budget_versions gbv WHERE gb.budget_version_id = gbv.budget_version_id AND gb.period_name = 'JAN-2024';

Related Objects

As indicated by the extensive foreign key metadata, GL_BUDGET_VERSIONS is a foundational table referenced by a wide array of GL sub-modules. Key related objects include:

• GL_BUDGET_TYPES: Defines the type (e.g., "Encumbrance", "Budget") via the BUDGET_TYPE foreign key.
• GL_BALANCES: Stores period-end and project-to-date budget balances for each version.
• GL_BC_PACKETS / GL_BC_PACKETS_HISTS: Reference the version for funds checking (BUDGET_VERSION_ID) and the specific funding budget (FUNDING_BUDGET_VERSION_ID) against which transactions are reserved.
• GL_BUDGET_ASSIGNMENTS: Uses the FUNDING_BUDGET_VERSION_ID to define budget account ranges and rules for automatic funds reservation.
• Archive and History Tables (GL_ARCHIVE_*, GL_AUTO_ALLOC_SET_HISTORY): Maintain historical references to budget versions used in archival and allocation processes.