Results for “glfv_budget_balances”
13 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GLFV_BUDGET_BALANCES is an APPS-owned read-only view in the General Ledger (GL) product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It presents budget balances from the GL_BALANCES table in a denormalized, reporting-friendly form, joining ledger, budget version, code combination, and currency lookup information so that budget data can be queried without additional joins. The view is defined with WITH READ ONLY, confirming it is intended strictly for query and reporting, not for DML. It is frequently surfaced in Oracle EBS reporting and integration contexts — particularly in the Financial Statement Generator (FSG), Discoverer, and custom SQL extracts — where budget-versus-actual comparisons are required.
The view's distinguishing feature is the exposure of a project-to-date (PTD) pair of columns derived by adding the period activity to the stored project-to-date balance: (PROJECT_TO_DATE_DR + PERIOD_NET_DR) and (PROJECT_TO_DATE_CR + PERIOD_NET_CR). This matches the user's search term "project_to_date_dr," reflecting a common need to retrieve cumulative budget debit balances including the current period.
Underlying Base Objects
Although the documented metadata lists no base objects, the view text unambiguously references four base tables:
- GL_BALANCES (aliased GL_STANDARD_BALANCE) — the primary source of budget balance rows, filtered by
ACTUAL_FLAG = 'B'to restrict to budget data only. - GL_LEDGERS — supplies the ledger name and functional currency used for currency-type derivation.
- GL_CODE_COMBINATIONS (aliased GCC) — provides the account structure and the summary flag used for the "_LA:SUMMARY_FLAG" attribute.
- GL_BUDGET_VERSIONS — supplies the budget name for each BUDGET_VERSION_ID.
- GL_LOOKUPS (aliased LK) — joined on LOOKUP_TYPE = 'CURRENCY_TYPE' to give a currency-type meaning via complex DECODE logic on CURRENCY_CODE, TRANSLATED_FLAG, and the ledger's functional currency.
The "_KF:SQLGL:GL#:GCC" token signals that the CODE_COMBINATION_ID column carries the GL accounting flexfield key, enabling flexfield-based reporting.
Key Columns
- LEDGER_ID / LEDGER_NAME — ledger identifier and its descriptive name.
- ACCOUNT_ID ("_KF:ACCOUNT") — the code combination identifier exposed with the accounting flexfield key marker.
- CURRENCY / CURRENCY_T — the currency code and its derived currency-type meaning (e.g., entered, translated, functional, statistical).
- PERIOD_NAME — the accounting period of the balance row.
- BUDGET_VERSION_ID / BUDGET_NAME — identifies which budget the balance belongs to.
- PERIOD_NET_DR / PERIOD_NET_CR — period activity, debit and credit.
- QTD_DR / QTD_CR — quarter-to-date = QUARTER_TO_DATE_DR + PERIOD_NET_DR (and CR equivalent).
- YTD_DR / YTD_CR — year-to-date = BEGIN_BALANCE_DR + PERIOD_NET_DR (and CR equivalent).
- PROJECT_TO_DATE_DR / PROJECT_TO_DATE_CR (="project_to_date_dr") — cumulative project-to-date amount plus current period activity. This is the primary column of interest for the searched term, and is the conceptual "PTD" figure used where balances accumulate over the life of a project or budget horizon.
- BEGIN_BALANCE_DR / BEGIN_BALANCE_CR — opening balances for the period.
Common Use Cases and Queries
Typical uses include budget-versus-budget analysis, cumulative budget reporting, and feeding balances into external reporting or reconciliation processes. Because the view already joins ledger, budget, and lookup details, ad-hoc queries avoid re-implementing that logic.
To retrieve project-to-date debit balances for a specific ledger and budget:
SELECT LEDGER_NAME, BUDGET_NAME, ACCOUNT_ID, PERIOD_NAME, PROJECT_TO_DATE_DR, PROJECT_TO_DATE_CR FROM APPS.GLFV_BUDGET_BALANCES WHERE LEDGER_ID = :ledger_id AND BUDGET_VERSION_ID = :budget_version_id;- Filter by
PERIOD_NAMEto isolate a single accounting period, or omit it to review cumulative PTD movement across periods. - Join to GL_CODE_COMBINATIONS on ACCOUNT_ID for account descriptions, or to GL_PERIODS for fiscal calendar attributes not already exposed.
Because the view is defined WITH READ ONLY, it should be used only for extraction and reporting, not for updating budget balances. For any source-level adjustment, the underlying GL_BALANCES or budget maintenance programs in the GL module must be used instead.
-
View: GLFV_BUDGET_BALANCES 12.1.1
APPS.GLFV_BUDGET_BALANCES·↳ GL_BALANCES·↳ GL_BUDGET_VERSIONS·↳ GL_CODE_COMBINATIONS·Explore GL module →
-
View: GLFV_BUDGET_BALANCES 12.2.2
Not implemented in this database·Explore GL module →
-
SYNONYM: APPS.GL_BALANCES 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.GL_LOOKUPS 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
SYNONYM: APPS.GL_LEDGERS 12.1.1
-
USSGL transaction codes
-
12.1.1 DBA Data 12.1.1
-
USSGL transaction codes