Results for “gl_budgets_target_budgets_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_BUDGETS_TARGET_BUDGETS_V is a General Ledger (GL) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as "10SC ONLY," indicating the view exists to support a specific localized or downstream reporting requirement rather than the core General Ledger budget maintenance screens. The view joins budget definitions to their budget versions and to the period status records that mark the budget's active range, exposing both the starting and ending period of each budget in a single queryable row.

Its purpose is to present target budget scope information: for a given ledger and budget name, it delivers the descriptive text, the budget version identifier, and the calendar periods that bound the budget. Because both the start and end periods are resolved from GL_PERIOD_STATUSES, the view is useful wherever a report or interface must determine the exact period window over which a budget is valid without performing those lookups manually.

Underlying Base Objects

The view is defined over four sources, all referenced through APPS synonyms: GL_BUDGETS, GL_BUDGET_VERSIONS, and GL_PERIOD_STATUSES (used twice, aliased PS1 and PS2).

• GL_BUDGETS (B) supplies the budget description, ledger identifier, and the first and last valid period names that define the budget's range.
• GL_BUDGET_VERSIONS (BV) supplies the budget name and the budget_version_id, joined to GL_BUDGETS on budget_name.
• GL_PERIOD_STATUSES PS1 resolves the first valid period name into a period number and period year, filtered to application_id 101 (General Ledger) and matched on ledger_id.
• GL_PERIOD_STATUSES PS2 performs the equivalent resolution for the last valid period name.

The join therefore requires that periods for both the start and end of the budget exist in GL_PERIOD_STATUSES for the same ledger and for the GL application. If either period is absent, no row is returned for that budget.

Key Columns

• BUDGET_NAME – the budget identifier from GL_BUDGET_VERSIONS, joined to GL_BUDGETS on the same column.
• BUDGET_VERSION_ID – the unique version identifier associated with the budget.
• DESCRIPTION – the descriptive text of the budget from GL_BUDGETS.
• LEDGER_ID – the ledger to which the budget and periods belong.
• START_PERIOD_NAME, START_PERIOD_NUM, START_PERIOD_YEAR – the first valid period, expressed as name, number, and accounting year. The user's search term, start_period_year, corresponds to the accounting year of the budget's opening period.
• END_PERIOD_NAME, END_PERIOD_NUM, END_PERIOD_YEAR – the last valid period, expressed in the same three attributes.

Common Use Cases and Queries

Typical scenarios include identifying budgets that begin or end in a particular accounting year, validating that a budget covers a requested reporting range, and populating interfaces that require the period window alongside the budget name and version.

• List budgets whose opening period falls in a given year:
  SELECT budget_name, budget_version_id, description, ledger_id, start_period_name, start_period_year FROM gl_budgets_target_budgets_v WHERE start_period_year = 2013;
• Restrict to a single ledger and order by the opening period:
  SELECT budget_name, start_period_name, end_period_name FROM gl_budgets_target_budgets_v WHERE ledger_id = 1 ORDER BY start_period_year, start_period_num;
• Find budgets active across a period range:
  SELECT budget_name, budget_version_id FROM gl_budgets_target_budgets_v WHERE start_period_num <= :p_start_num AND end_period_num >= :p_end_num;

The last query is efficient because multi-table joins are resolved in the view definition, so callers simply filter or sort on the exposed period columns such as start_period_year rather than joining the underlying GL tables themselves.