Search Results glbv_gl_budgets

Overview

GLBV_GL_BUDGETS is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite, marked VALID in the ETRM registry for both 12.1.1 and 12.2.2. It is a denormalized, read-only reporting surface that joins budget definition data held in GL_BUDGETS with budget version data held in GL_BUDGET_VERSIONS, exposing one row per budget version. Its practical role is to give concurrent programs, Discoverer worksheets, BI Publisher reports, and inbound integration extracts a single, security-filtered source for budget names, owning ledgers, and the version lifecycle attributes (status, valid period ranges, open year, and journal-requirement flag) without requiring the developer to hand-code the BUDGET_NAME/BUDGET_TYPE join.

Underlying Base Objects

Per the supplied ETRM metadata, the view text references two real tables — GL_BUDGETS (aliased GL_BUDGET) and GL_BUDGET_VERSIONS (aliased GL_BUDGET_VERSION) — while "referenced base objects" lists none documented, so the view text itself is the authoritative source. The join is non-standard: the two tables are correlated on the composite key of BUDGET_NAME and BUDGET_TYPE rather than on an ID column, and the result is constrained by the sub-clause '_SEC:GL:GL_BUDGET.LEDGER_ID' IS NOT NULL. In Oracle EBS, that underscore-prefixed token is a semantic anchor consumed by the GL security/access control layer, so the view returns only budget versions whose owning LEDGER_ID is accessible to the invoking responsibility's data access set. The view is declared WITH READ ONLY, guaranteeing that no SQL statement executed against it can modify underlying budget records.

Key Columns

• BUDGET_VERSION_ID — Primary identifier of the budget version drawn from GL_BUDGET_VERSIONS; the most granular key returned.
• BUDGET_NAME — The budget definition name from GL_BUDGETS; combined with BUDGET_TYPE it forms the correlation to the version table.
• LEDGER_ID — The ledger that owns the budget and the column against which row-level ledger security is enforced.
• DATE_CREATED / DATE_FROZEN / DATE_CLOSED — Lifecycle timestamps. The excerpt lists DATE_FROZEN among columns though the visible SELECT emits DATE_CREATED and DATE_CLOSED, indicating the published column list is broader than the excerpted text.
• FIRST_VALID_PERIOD_NAME / LAST_VALID_PERIOD_NAME (published as FIRST_BUDGET_PERIOD / LAST_BUDGET_PERIOD) — The accounting period range over which the version may hold budget amounts.
• LATEST_OPENED_YEAR — The most recent fiscal year still open for budget entry; used by validation logic to block entries into closed years.
• DESCRIPTION — Free-text description of the budget.
• "_LA:STATUS" — Status meaning looked up from GL_LOOKUPS under lookup type PLAN/VERSION STATUS.
• "_LA:REQUIRE_BUDGET_JE_FLAG" — YES/NO meaning from GL_LOOKUPS indicating whether budget journals are required for this budget.

Common Use Cases and Queries

Typical uses include budget-versions LOVs, listing budgetable versions for a ledger, and pre-validation in budget upload interfaces. A representative query:

SELECT budget_version_id, budget_name, ledger_id,
       first_budget_period, last_budget_period,
       latest_opened_year, "_LA:STATUS" status_meaning
FROM   apps.glbv_gl_budgets
WHERE  ledger_id = :p_ledger_id
ORDER  BY budget_name;

For an entry-eligibility check, filter on the open-year and journal-requirement columns before permitting upload; for reconciliation, join BUDGET_VERSION_ID to GL_BUDGET_VERSIONS or GL_BUDGET_ASSIGNMENTS to compare defined versus assigned budgets. Because ledger security is applied inside the view, queries should not attempt to re-implement data access set filtering.