Results for “gl_budget_versions”

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

Overview

GL_BUDGET_VERSIONS is the General Ledger master table that stores budget version definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a uniquely named budget version, defined by a budget name and a budget type, which together form the business identity of the version. Budget versions are the containers against which budgetary control, encumbrance checking, funds reservation, and budget-to-actual reporting are performed. A version may be opened, made active, archived, or closed through status transitions captured in the table, and a version may optionally be linked to a control version through CONTROL_BUDGET_VERSION_ID for comparative or enacted-versus-proposed budget analysis.

The table resides in the GL schema and is classified heuristically as hub-leaning in a Data Vault model, meaning it functions as a central reference entity (hub) whose surrogate key is propagated as a foreign key into a large family of transactional and summary satellites. The primary key GL_BUDGET_VERSIONS_PK is defined on BUDGET_VERSION_ID, and the unique index GL_BUDGET_VERSIONS_U1 also enforces uniqueness of BUDGET_VERSION_ID, confirming the surrogate key as the stable join path across the schema.

Key Information Stored

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

• BUDGET_VERSION_ID — Surrogate primary key; the value referenced by all dependent tables.
• BUDGET_NAME — Business name of the budget version; participates with BUDGET_TYPE in the unique business key (GL_BUDGET_VERSIONS_UK1).
• BUDGET_TYPE — Classifies the version (for example, budget or forecast type) and is foreign-keyed to GL_BUDGET_TYPES and to GL_BUDGETS.
• VERSION_NUM — Numeric version sequence for versions sharing the same budget name.
• STATUS — Lifecycle state of the version, governing whether it can accept entries or be used in reporting.
• DATE_OPENED, DATE_ACTIVE, DATE_ARCHIVED — Key lifecycle dates that drive period and audit reporting.
• CONTROL_BUDGET_VERSION_ID — Self-referencing foreign key identifying the controlling or comparison version.
• DESCRIPTION — Free-text explanation of the version's purpose.
• IGI_BUD_NYC_FLAG — Public-sector specific flag used by the IGI (Public Sector) budgeting extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit and concurrent-program context columns.
• ATTRIBUTE1–ATTRIBUTE8 and CONTEXT — Descriptive flexfield storage used for client-specific budget version attributes.

Common Use Cases and Queries

Budget versions are queried during budgetary control setup, funds availability checks, and budget-to-actual reporting. A frequent pattern resolves the version identifier for a given name and type:

• SELECT BUDGET_VERSION_ID, BUDGET_NAME, BUDGET_TYPE, STATUS FROM GL_BUDGET_VERSIONS WHERE BUDGET_NAME = :name AND BUDGET_TYPE = :type;
• Listing active versions for a period: WHERE STATUS = 'O' or filtering on DATE_ACTIVE ranges.
• Comparing a working version to its control version by self-joining on CONTROL_BUDGET_VERSION_ID.
• Joining to GL_BALANCES on BUDGET_VERSION_ID to extract budget balances per account and period for GL trial balance and budget inquiry reports.
• Joining to GL_BUDGET_TYPES to categorize versions and to GL_BUDGETS to reconcile version configuration with budget setup.

Reporting use cases include listing all versions with open/archived status, tracking version usage through GL_JE_HEADERS, and validating that no orphaned BUDGET_VERSION_ID values exist in balances tables.

Related Objects

The table is referenced by a broad set of GL objects through BUDGET_VERSION_ID, and itself references two objects:

• GL_BUDGET_TYPES — referenced by BUDGET_TYPE; defines allowable version categories.
• GL_BUDGETS — referenced by BUDGET_TYPE and BUDGET_NAME; holds budget definition headers.
• GL_BALANCES and GL_ARCHIVE_BALANCES — store budget balances keyed by BUDGET_VERSION_ID.
• GL_BC_PACKETS and GL_BC_PACKETS_HISTS — budgetary control packets referencing both BUDGET_VERSION_ID and FUNDING_BUDGET_VERSION_ID.
• GL_BUDGET_ASSIGNMENTS and GL_BUDGET_ASSIGNMENT_RANGES — map funding versions to ranges.
• GL_ENTITY_BUDGETS — associates budget versions with entities.
• GL_JE_HEADERS and GL_INTERFACE — journal and interface records carrying the version context.
• GL_BUDGET_BATCHES, GL_BUDGET_INTERFACE, and GL_BUDGET_PERIOD_RANGES — support budget upload, loading, and range definition.
• CE_FORECAST_ROWS, GL_CONSOLIDATION_HISTORY, and GL_TRANSLATION_TRACKING — consume budget versions in forecasting, consolidation, and translation processes.
• GL_BUDGET_VERSIONS self-reference via CONTROL_BUDGET_VERSION_ID for control-versus-working relationships.