Search Results current_version_id

Overview

GL_BUDGETS is the master definition table for budgets within the Oracle General Ledger (GL) module of Oracle E-Business Suite. Housed in the GL schema, it stores one row for each budget defined in a given ledger, capturing the budget's identity, lifecycle status, validity period ranges, and version-tracking attributes. The table is central to the budgeting and budgetary control features of EBS: every budget definition, budget organization assignment, and budget version that users interact with through the GL Budgets form ultimately traces back to a row in GL_BUDGETS.

From a dimensional modeling perspective, the table exhibits satellite-leaning characteristics. Its business identity is a composite key of BUDGET_TYPE and BUDGET_NAME, while it also carries descriptive and volatile attributes such as STATUS, validity period ranges, and current version pointers. In a Data Vault representation it would most naturally be modeled as a satellite hanging off a budget hub, with GL_BUDGET_TYPES and the ledger acting as the referenced hubs or reference tables. This is a heuristic suggestion rather than a native EBS construct.

Key Information Stored

The documented physical schema for release 12.2.2 exposes 26 columns. The most operationally significant include:

• BUDGET_TYPE — Classifies the budget (for example, the type defined in GL_BUDGET_TYPES). Part of the composite primary key and a foreign key to GL_BUDGET_TYPES.
• BUDGET_NAME — The user-defined budget name. This is the second member of the composite primary key and the primary business-key candidate (unique index GL_BUDGETS_U1: BUDGET_NAME, BUDGET_TYPE).
• LEDGER_ID — Identifies the ledger to which the budget belongs; a foreign key that scopes the budget definition to a specific accounting ledger.
• STATUS — The lifecycle state of the budget (for example, open, frozen, or closed).
• CURRENT_VERSION_ID — Points to the budget version currently active for the budget.
• REQUIRE_BUDGET_JOURNALS_FLAG — Controls whether budget journals are mandatory for postings to this budget.
• LATEST_OPENED_YEAR — The most recent fiscal year opened for the budget.
• FIRST_VALID_PERIOD_NAME and LAST_VALID_PERIOD_NAME — Define the period range over which the budget is valid.
• DATE_CREATED and DATE_CLOSED — Record the creation and closure dates of the budget definition.
• DESCRIPTION — Free-text description of the budget.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.
• ATTRIBUTE1 through ATTRIBUTE8 and CONTEXT — Descriptive flexfield segments.

The surrogate-style primary key is GL_BUDGET_PK, defined on BUDGET_TYPE and BUDGET_NAME, which coincides with the unique index GL_BUDGETS_U1.

Common Use Cases and Queries

Typical reporting scenarios include listing all budgets for a ledger, identifying open budgets, and locating budgets with a specified validity window. A representative query joins GL_BUDGETS to GL_BUDGET_TYPES and filters by ledger and status:

• SELECT b.budget_name, b.budget_type, b.status, b.latest_opened_year FROM gl_budgets b WHERE b.ledger_id = :ledger_id AND b.status = 'O';
• Locating the currently active version: join GL_BUDGETS.CURRENT_VERSION_ID to GL_BUDGET_VERSIONS to surface the version in force.
• Auditing budget creation and closure: query DATE_CREATED, DATE_CLOSED, CREATED_BY, and LAST_UPDATED_BY for governance reporting.
• Flexfield reporting: extract ATTRIBUTE1–ATTRIBUTE8 and CONTEXT for user-defined budget attributes.

Related Objects

The table participates in several documented foreign key relationships:

• GL_BUDGET_TYPES — Referenced by GL_BUDGETS.BUDGET_TYPE; defines the valid budget types.
• GL_BUDGET_VERSIONS — References GL_BUDGETS via BUDGET_TYPE and BUDGET_NAME; stores the individual versions of each budget.
• GL_BUDGET_ASSIGNMENTS and budget organization components (not enumerated in the metadata) typically reference the same business key.
• GL_LEDGERS — Implied dependency via LEDGER_ID, which scopes each budget to a ledger.
• GL Budgets APIs and the Budgets form (GLXBUDFM) operate on this table for create, update, and freeze operations.