Search Results first_valid_year

Overview

APPS.GL_BUDGETS_V is a supplementary Oracle E-Business Suite view that presents budget definition and budget version information from the General Ledger schema in a denormalized, report-friendly form. Its documented purpose is to simplify forms coding; Oracle explicitly warns that the view is not intended as a general-purpose query or data manipulation interface and that its definition may change significantly between minor or major releases. Despite this caveat, the view is widely referenced in custom reporting, conversions, and integration logic where a consolidated read of budget header attributes, ledger context, and version status is required. The view is owned by the APPS schema, carries FND Design Data identifier SQLGL.GL_BUDGETS_V, and holds VALID status in the ETRM repository for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the following documented base objects: GL_BUDGETS, GL_BUDGET_VERSIONS, GL_LEDGERS, and GL_PERIOD_STATUSES, all referenced as synonyms, plus the GL_LOOKUPS view. GL_BUDGETS supplies the budget definition itself, including budget name, budget type, and the master budget relationship. GL_BUDGET_VERSIONS supplies version-level attributes, including the current version identifier, version status, and the valid period and year boundaries that drive the FIRST_VALID_PERIOD_NUM column of interest. GL_LEDGERS provides ledger context such as LEDGER_ID and LEDGER_NAME, reflecting the 12.x shift from set of books to ledger. GL_PERIOD_STATUSES contributes period-open and period-status information used to derive the latest opened year and the bound period names. GL_LOOKUPS is used to resolve coded status values into the descriptive SHOW_STATUS text exposed by the view.

Key Columns

• BUDGET_NAME, BUDGET_VERSION_ID, CURRENT_VERSION_ID — budget identity and the currently active version for the budget.
• STATUS, SHOW_STATUS — the version status code and its decoded display form, derived with GL_LOOKUPS.
• FIRST_VALID_PERIOD_NAME, LAST_VALID_PERIOD_NAME — the period name boundaries of the budget version.
• FIRST_VALID_PERIOD_NUM, LAST_VALID_PERIOD_NUM — the numeric period sequence for those boundaries; FIRST_VALID_PERIOD_NUM is the searched term and is the reliable numeric key when ordering or range-filtering periods, since period names sort alphabetically rather than chronologically.
• FIRST_VALID_YEAR, LAST_VALID_YEAR — the fiscal years enclosing the valid range.
• LATEST_OPENED_YEAR — the most recent year for which periods remain open, useful for determining whether budget entry is permissible.
• START_DATE, END_DATE, DATE_CREATED, DATE_CLOSED — lifecycle timestamps for the budget version.
• LEDGER_ID, LEDGER_NAME — the ledger to which the budget belongs.
• BUDGET_TYPE, MASTER_BUDGET_NAME, MASTER_BUDGET_VERSION_ID, REQUIRE_BUDGET_JOURNALS_FLAG — classification and control attributes.
• ATTRIBUTE1 through ATTRIBUTE8 and CONTEXT — descriptive flexfield context and segment values.

Common Use Cases and Queries

Typical scenarios include listing all budgets for a ledger, identifying the current version of each budget, comparing the valid period window against the latest opened year, and locating budgets whose validity begins before a specified fiscal period. Because FIRST_VALID_PERIOD_NUM and FIRST_VALID_YEAR are numeric, they support efficient range predicates that period names cannot. A representative query follows:

SELECT budget_name, budget_version_id, status, show_status, first_valid_year, first_valid_period_num, first_valid_period_name, last_valid_year, last_valid_period_num, ledger_name FROM apps.gl_budgets_v WHERE ledger_id = :p_ledger_id AND budget_version_id = current_version_id AND first_valid_year <= :p_year ORDER BY budget_name, first_valid_period_num;

A further pattern joins the view to GL_BUDGET_ASSIGNMENTS or GL_BUDGET_INTERFACE on BUDGET_VERSION_ID to reconcile budget definitions with their assigned accounts or upload interface records. Analysts should treat the view strictly as read-only, avoid depending on undocumented behavior, and validate results against GL_BUDGETS and GL_BUDGET_VERSIONS whenever view definitions change across releases.