Search Results master_budget_version_id




Overview
Explore in AI Chat

Overview

GL_BUDGETS_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite, marked VALID in both 12.1.1 and 12.2.2 environments. The view presents budget definition and budget version information for a ledger, joining budget headers to their versions, their associated period status ranges, the target ledger, and lookup-driven status descriptions. Its role is to provide a denormalized, report-ready projection that combines budget header attributes (name, status, type, validity period range, flags, audit columns, and descriptive flexfield attributes) with version, ledger, and period context in a single row per budget version.

The ETRM documentation labels the description as "10SC ONLY," which indicates the object is maintained or surfaced only for a specific localization or release scope rather than a general-purpose, cross-release deliverable. This designation matters when assessing portability: consumers should confirm whether the view is present and populated in their specific installation before building dependent logic. The view text provides the authoritative definition and should be treated as the reference for column semantics.

Underlying Base Objects

The view is defined over five documented base objects, resolved in APPS through synonyms and views:

  • GL_BUDGETS (synonym, alias B) — the driving budget header table supplying name, status, validity periods, flags, ledger, and audit/DESC flex columns.
  • GL_BUDGET_VERSIONS (synonym, aliases BV and MBV) — joined twice: once for the budget's own version and once (outer join) for the master/control budget version via BV.CONTROL_BUDGET_VERSION_ID = MBV.BUDGET_VERSION_ID.
  • GL_PERIOD_STATUSES (synonym, aliases START_PER and DEST_PER) — supplies the period year, period number, start date, and end date for the first and last valid period names of the budget.
  • GL_LEDGERS (synonym, alias LDG) — supplies the ledger name for the budget's ledger.
  • GL_LOOKUPS (view, alias ST) — supplies the user-facing status meaning for the budget status code using lookup type 'PLAN/VERSION STATUS'.

Because GL_BUDGETS is the only table without an outer-join marker in the joins shown, it acts as the primary source, with version and master-version attributes attached through equality and outer-join predicates respectively.

Key Columns

Common Use Cases and Queries

Typical uses include budget inventory reporting per ledger, identifying open versus closed budgets, validating validity-period coverage, and determining the master version relationship for control budgets. A representative query listing active budgets and their effective ranges is:

  • SELECT budget_name, show_status, ledger_name, budget_type, first_valid_period_name, last_valid_period_name FROM gl_budgets_v WHERE ledger_id = :ledger_id ORDER BY budget_name;
  • SELECT budget_name, master_budget_name, current_version_id FROM gl_budgets_v WHERE master_budget_version_id IS NOT NULL;
  • SELECT budget_name, start_date, end_date FROM gl_budgets_v WHERE SYSDATE BETWEEN start_date AND end_date;

All queries should qualify by LEDGER_ID where relevant, since budget names are ledger-scoped, and should avoid relying on status text alone because SHOW_STATUS is derived through GL_LOOKUPS.