Results for “igi_bud_variance_bal_v”

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

Overview

IGI_BUD_VARIANCE_BAL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI - Public Sector Financials International product family. It is defined over the General Ledger balances data model and presents budget variance balance information in a form suited to public-sector budget execution and variance reporting. In Oracle EBS 12.1.1 and 12.2.2, the view retains a VALID status and is registered against the APPS schema, meaning it is available to any responsibility or concurrent program that can query APPS-owned objects without additional grants.

The view is essentially a presentation and enrichment layer over GL_BALANCES. Rather than storing data itself, it reads the standard GL balance rows and applies currency conversion logic, period-to-date, quarter-to-date, project-to-date and year-to-date derivation, and factor normalization through the GLR03300_PKG and IGIGGACC_PKG packages. This design allows IGI budget variance reports, inquiries and analytics to consume GL balance facts with the amount columns already expressed in the convention the reporting layer expects.

Underlying Base Objects

The documented base objects referenced by the view are:

• GL_BALANCES (accessed via synonym) — the primary source of rows, supplying the set of books, period, currency, code combination, actual flag, encumbrance type, budget version, and the various debit and credit balance columns.
• GL_LEDGERS (accessed via synonym) — the ledger definition used to establish ledger context for the balances returned.
• GLR03300_PKG — a General Ledger package supplying the functional currency code and the reporting factor used to normalize amounts (GET_FUNCTIONAL_CURRENCY_CODE, GET_FACTOR).
• IGIGGACC_PKG — an IGI package consulted for the budget status flag (GET_BUD_STATUS_FLAG), which governs whether year-to-date amounts are presented.

Because every amount column is derived rather than stored, the view reflects the current state of GL_BALANCES at query time. Balance translation and factor behavior therefore follow the same rules used by the core General Ledger currency engine.

Key Columns

• SET_OF_BOOKS_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM — ledger and accounting period identification.
• CURRENCY_CODE, TRANSLATED_FLAG — currency of the balance row and whether it carries translated amounts.
• CODE_COMBINATION_ID — the accounting flexfield combination to which the balance belongs.
• ACTUAL_FLAG, ENCUMBRANCE_TYPE_ID, BUDGET_VERSION_ID — distinguishing actual, budget and encumbrance balances.
• ENTERED_PERIOD_NET_DR / ENTERED_PERIOD_NET_CR — period net debit and credit in entered currency, divided by the GLR03300_PKG factor.
• FUNCTIONAL_PERIOD_NET_DR / FUNCTIONAL_PERIOD_NET_CR — functional-currency equivalents, suppressed when the entered currency is already functional or statistical.
• ENTERED_QUARTER_TO_DATE and ENTERED_PROJECT_TO_DATE — cumulative net amounts derived from quarter-to-date and project-to-date columns plus the current period net.
• Year-to-date entries gated by IGIGGACC_PKG.GET_BUD_STATUS_FLAG, combining begin balance with period net activity.

Common Use Cases and Queries

The view typically supports budget vs. actual variance reports, fund availability inquiries, and public-sector appropriation monitoring. A representative query retrieves period balances for a ledger and period:

• SELECT period_name, code_combination_id, entered_period_net_dr, entered_period_net_cr FROM igi_bud_variance_bal_v WHERE set_of_books_id = :ledger_id AND period_name = :period AND actual_flag = 'B';
• SELECT code_combination_id, SUM(entered_quarter_to_date) FROM igi_bud_variance_bal_v WHERE set_of_books_id = :ledger_id AND budget_version_id = :version GROUP BY code_combination_id;
• Join to GL_CODE_COMBINATIONS on code_combination_id to render account segment descriptions alongside the variance amounts.

Because amount columns depend on package calls, performance tuning should focus on filtering by set of books, period and code combination before aggregation.