Search Results last_valid_period_name




Overview
Explore in AI Chat

Overview

GL_BUDGETS_CURRENT_V is a General Ledger (GL) reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It presents a consolidated, denormalized projection of budget definition and budget version data, joining master budget records in GL_BUDGETS to their associated versions in GL_BUDGET_VERSIONS. The ETRM documentation flags the object as "10SC ONLY," indicating that its intended scope was historically limited to a specific localization or deployment context; nonetheless, the view remains a valid, queryable APPS object in standard installations.

The view filters to budgets whose status falls within the open, current, or frozen lifecycle states ('O', 'C', 'F'), thereby excluding budgets that are still being defined or have been archived. This filtering makes the view suitable for runtime budget entry, inquiry screens, and integration extracts that must only reference active budget versions. Its primary value is that it exposes the version identifier and validity period range in a single row per budget version, sparing the caller the need to navigate the two-entity parent/child model directly.

Underlying Base Objects

The view is defined over two base objects, exposed to APPS as synonyms:

  • GL_BUDGETS (SYNONYM) — stores the budget header: budget name, budget type, ledger, and status. This is the driving table for name/type matching and status filtering.
  • GL_BUDGET_VERSIONS (SYNONYM) — stores each version of a budget, keyed by BUDGET_VERSION_ID and related to the parent by BUDGET_NAME and BUDGET_TYPE.

The join condition is an equi-join on BUDGET_NAME and BUDGET_TYPE between the two objects. This composite key reflects the fact that budget names are reusable across budget types within a ledger. Because the join is on descriptive attributes rather than a surrogate foreign key, cardinality assumes one or more versions per budget header. The status predicate is applied to the GL_BUDGETS side only.

Key Columns

  • BUDGET_VERSION_ID — Surrogate identifier of the budget version. This is the column most consumers will carry forward into detail tables or APIs.
  • BUDGET_NAME — User-defined name of the budget from GL_BUDGETS, used for display, LOV, and cross-reference.
  • LEDGER_ID — Ledger owning the budget; joins to GL_LEDGERS for ledger name, chart of accounts, and reporting currency.
  • FIRST_VALID_PERIOD_NAME — The earliest accounting period for which the budget holds balances. This column is the primary subject of the search term "first_valid_period_name," and enforces the start of the budget's effective date range.
  • LAST_VALID_PERIOD_NAME — The latest accounting period for which the budget is defined, paired with FIRST_VALID_PERIOD_NAME to bound the budget horizon.

Common Use Cases and Queries

Typical usage includes populating budget version LOVs, validating that a requested accounting period falls inside the budget horizon, and driving eligibility checks before budget uploads or allocations. A representative query lists current budget versions for a ledger, ordered by budget name and opening period:

  • SELECT budget_version_id, budget_name, first_valid_period_name, last_valid_period_name
FROM   gl_budgets_current_v
WHERE  ledger_id = :p_ledger_id
ORDER  BY budget_name, first_valid_period_name;
  • Period-range validation: test whether :p_period lies between FIRST_VALID_PERIOD_NAME and LAST_VALID_PERIOD_NAME for a given BUDGET_VERSION_ID.
  • Integration extracts that require an authoritative list of open/current/frozen budget versions, joined to GL_PERIODS or GL_LEDGERS for descriptive enrichment.

Because the view already constrains status, callers should not re-filter on GL_BUDGETS status unless they need to widen the scope.