Results for “igi_bud_variance_sec_bal_v”

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

Overview

IGI_BUD_VARIANCE_SEC_BAL_V is a public-sector reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product. It is defined over General Ledger balances and presents budget-versus-actual variance information at the balance level. The view is designed to support budgetary control and variance analysis, particularly for government and public sector organizations that must monitor appropriations, budgets, and expenditures against authoritative funding limits.

The view exposes debit, credit, quarter-to-date, project-to-date, and year-to-date amounts, normalizing stored balances into entered and functional currency values. It is registered as VALID and documented in ETRM for releases 12.1.1 and 12.2.2. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying GL balances at query time. It is typically consumed by concurrent programs, FSG-style reports, and custom budget-variance inquiries within the IGI module.

Underlying Base Objects

The view is documented as based on GL_BALANCES. The base objects referenced in the metadata are:

• GL_BALANCES (SYNONYM) – the primary source of period balances, including period net debit/credit, quarter-to-date, project-to-date, and beginning balance columns aliased as BA.
• GLR03300_PKG (PACKAGE) – provides GET_FACTOR and GET_FUNCTIONAL_CURRENCY_CODE, used to scale amounts and to determine whether a balance row is already in functional currency.
• IGIGGACC_PKG (PACKAGE) – provides GET_BUD_STATUS_FLAG, used to conditionally compute year-to-date amounts based on budget status.
• GL_LEDGERS (SYNONYM) – referenced for ledger and set-of-books context associated with the balances.

The join between GL_BALANCES and these packages allows the view to harmonize stored, potentially translated balances into a consistent presentation layer without duplicating GL data.

Key Columns

The view projects balance-identifying columns and derived amount columns. Principal identifiers include SET_OF_BOOKS_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, CURRENCY_CODE, CODE_COMBINATION_ID, ACTUAL_FLAG, ENCUMBRANCE_TYPE_ID, BUDGET_VERSION_ID, TRANSLATED_FLAG, and TEMPLATE_ID. These keys align the row to a specific ledger, accounting period, account combination, and budget or encumbrance dimension.

Derived amount columns include:

• ENTERED_PERIOD_NET_DR / ENTERED_PERIOD_NET_CR – period debit and credit amounts divided by the GL factor.
• FUNCTIONAL_PERIOD_NET_DR / FUNCTIONAL_PERIOD_NET_CR – functional-currency equivalents, null when the row is already in functional or statistical currency.
• ENTERED_QUARTER_TO_DATE – net quarter-to-date activity (dr minus cr) added to period net activity.
• ENTERED_PROJECT_TO_DATE – net project-to-date activity combined with current period net movement.

Year-to-date amounts are computed conditionally, gated by IGIGGACC_PKG.GET_BUD_STATUS_FLAG, reflecting beginning balance plus period activity when budget status permits.

Common Use Cases and Queries

Typical scenarios include budget variance reports, appropriation monitoring, and reconciliation of encumbrance or budget balances by account and period. A representative query follows:

• SELECT set_of_books_id, period_name, code_combination_id, currency_code, entered_period_net_dr, entered_period_net_cr, entered_project_to_date FROM apps.igi_bud_variance_sec_bal_v WHERE period_name = :period AND set_of_books_id = :sob ORDER BY code_combination_id;
• SELECT period_year, period_num, budget_version_id, SUM(entered_quarter_to_date) FROM apps.igi_bud_variance_sec_bal_v WHERE code_combination_id = :ccid GROUP BY period_year, period_num, budget_version_id;
• SELECT code_combination_id, entered_project_to_date - entered_quarter_to_date variance FROM apps.igi_bud_variance_sec_bal_v WHERE actual_flag = 'B';

Because the view depends on PL/SQL package functions for factor and budget-status resolution, performance is best served by filtering on SET_OF_BOOKS_ID, PERIOD_NAME, and CODE_COMBINATION_ID, and by ensuring package state is initialized before large reports execute.