Results for “gl_control_budget_balances_v”

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

Overview

GL_CONTROL_BUDGET_BALANCES_V is a predefined Oracle E-Business Suite view owned by the APPS schema and registered as VALID in both 12.1.1 and 12.2.2. It belongs to the General Ledger (GL) product family and is designed to surface budget balances for a specific account combination in the context of the Budget Inquiry/control-budget inquiry screens. Rather than storing data, the view projects dynamically calculated period-to-date (PTD), year-to-date (YTD), quarter-to-date (QTD), and project-to-date (PJTD) control balances for the budget version, code combination, currency, and template currently selected by the runtime package BUDGET_INQUIRY_PKG.

The view is fundamentally a "control" view: it drives the values shown when a user reviews budget balances through the Budget Inquiry form, and it is also used in reporting and integration scenarios where a conformed, translated budget balance is required. Because the view depends on session/context values returned by BUDGET_INQUIRY_PKG, it is not a general-purpose extraction view; it is intended to be consumed within the Budget Inquiry flow or after that package's global variables have been initialized.

Underlying Base Objects

The view is defined over two base objects, with an outer join path and a dependent package:

• GL_PERIOD_STATUSES — provides the calendar PERIOD_NAME, PERIOD_YEAR, and PERIOD_NUM; the view filters on APPLICATION_ID = 101 (General Ledger).
• GL_BALANCES — the source of budget balance amounts. The join is outer ((+)) to GL_PERIOD_STATUSES, so periods without a stored budget balance still appear with null balances.
• BUDGET_INQUIRY_PKG — a package supplying the runtime dimension values (GET_BVID, GET_CCID, GET_CURRENCY, GET_TEMPLATE_ID, GET_FACTOR, GET_FUNCT_CURR) used in the join predicates and in the balance calculations.

The budget rows are restricted by ACTUAL_FLAG = 'B' and a translation predicate that resolves to 'X' or 'R' depending on the selected currency, ensuring only the appropriate translated or entered balances are returned.

Key Columns

• PERIOD_NAME / PERIOD_YEAR / PERIOD_NUM — the accounting period identifiers from GL_PERIOD_STATUSES.
• LEDGER_ID — the ledger associated with the period status and balance row.
• CODE_COMBINATION_ID — the account combination for the returned budget balance.
• CURRENCY_CODE — the currency of the balance (or the special value STAT).
• BUDGET_VERSION_ID / TEMPLATE_ID — the budget version and control template being queried.
• CONTROL_BALANCE_PTD / _YTD / _QTD / _PJTD — the computed dr-minus-cr net amounts, divided by BUDGET_INQUIRY_PKG.GET_FACTOR for scale/rounding.
• ROW_ID — the GL_BALANCES row identifier, used as an existence indicator (DECODE nulls the balances when no row matches).
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard audit columns from GL_BALANCES.

Common Use Cases and Queries

The view is normally invoked from the Budget Inquiry form. In custom reporting, it should be used after initializing the package context, and joins to GL_PERIOD_STATUSES should be filtered to the desired ledger.

• Current-period control budget review — retrieve PTD/YTD control balances for the active budget version and account.
• Period-by-period budget trend — list all periods for a ledger ordered by PERIOD_NUM to analyse CONTROL_BALANCE_PTD progression.
• Reconciliation — compare CONTROL_BALANCE_YTD against the sum of PTD amounts to validate consistency.

SELECT PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM,
       CODE_COMBINATION_ID, CURRENCY_CODE,
       CONTROL_BALANCE_PTD, CONTROL_BALANCE_QTD,
       CONTROL_BALANCE_YTD, CONTROL_BALANCE_PJTD
FROM   APPS.GL_CONTROL_BUDGET_BALANCES_V
WHERE  LEDGER_ID = :p_ledger_id
AND    PERIOD_YEAR = :p_year
ORDER  BY PERIOD_NUM;

Because the balance columns are null-protected via DECODE on B.ROWID, periods with no budget activity return NULL rather than zero, which must be anticipated in downstream reporting logic.