Results for “glbv_encumbrance_balances”

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

Overview

GLBV_ENCUMBRANCE_BALANCES is an Oracle E-Business Suite General Ledger view that presents encumbrance balances by ledger, account, period, and encumbrance type. It is a reporting and integration-oriented object, exposed in ETRM documentation for release 12.1.1 and 12.2.2, and is typically consumed by Business Intelligence Publisher reports, Discoverer workbooks, custom concurrent programs, and outbound interfaces that require a denormalized, human-readable projection of encumbrance activity in the GL_BALANCES repository.

The view converts the transactional key identifiers of the general ledger into business-friendly attributes: it resolves LEDGER_ID to the ledger name, CODE_COMBINATION_ID to the account combination via the GL_CODE_COMBINATIONS key flexfield reference, and ENCUMBRANCE_TYPE_ID to the encumbrance type name. Critically, the view filters GL_BALANCES with ACTUAL_FLAG = 'E', which isolates the encumbrance balance rows (as opposed to 'A' for actuals and 'B' for budgets). The documentation notes that this object is "Not implemented in this database" in the ETRM reference environment, meaning the view is not deployed in that particular instance but its definition is documented for reference. All output is read-only, enforced by the WITH READ ONLY clause on the view text.

Underlying Base Objects

The documented view text joins four base objects:

• GL_BALANCES (aliased GL_STANDARD_BALANCE) — the primary source of balance amounts and the driving table of the join; only rows with ACTUAL_FLAG = 'E' qualify.
• GL_LEDGERS — supplies the ledger name via the LEDGER_ID join.
• GL_CODE_COMBINATIONS (GCC) — supplies the account combination referenced by the account flexfield token; the join is on CODE_COMBINATION_ID.
• GL_ENCUMBRANCE_TYPES — supplies the descriptive ENCUMBRANCE_TYPE name, joined on ENCUMBRANCE_TYPE_ID.

The view also embeds a security predicate, '_SEC:GL:GL_STANDARD_BALANCE.LEDGER_ID, GL_STANDARD_BALANCE.CODE_COMBINATION_ID', which applies the standard GL data-access-set security so that users see only ledgers and accounts they are authorized for. Because it is a view, no data is duplicated; runtime performance is governed by the indexes on GL_BALANCES and the joined dimension tables.

Key Columns

• LEDGER_ID / LEDGER_NAME — the ledger identifier and its display name.
• ACCOUNT_ID — the CODE_COMBINATION_ID, exposed with the "_KF:ACCOUNT" key flexfield descriptor.
• PERIOD_NAME — the accounting period of the balance row.
• ENCUMBRANCE_TYPE_ID / ENCUMBRANCE_TYPE — the encumbrance category (for example, purchase order or requisition encumbrances as configured).
• PERIOD_TO_DATE_DR / PERIOD_TO_DATE_CR — the period net debit and credit, derived from PERIOD_NET_DR and PERIOD_NET_CR.
• QUARTER_TO_DATE_DR / QUARTER_TO_DATE_CR — quarter balance computed as the stored quarter-to-date amount plus the period net amount.
• YEAR_TO_DATE_DR / YEAR_TO_DATE_CR — year-to-date balance computed as BEGIN_BALANCE_DR/CR plus PERIOD_NET_DR/CR.
• PROJECT_TO_DATE_DR / PROJECT_TO_DATE_CR — project-to-date balance similarly derived.
• BEGINNING_BALANCE_DR / BEGINNING_BALANCE_CR — the period beginning balance columns carried from GL_BALANCES. Users frequently reference BEGINNING_BALANCE_DR when reconciling opening encumbrance positions, and selection on this column is typical in query predicates.

Common Use Cases and Queries

Typical uses include encumbrance position reports, month-end opening-balance reconciliation, encumbrance type analysis, and feeds to budgeting or funds-availability tooling.

A representative query selecting the area of interest around BEGINNING_BALANCE_DR:

SELECT ledger_name, account_id, period_name, encumbrance_type, beginning_balance_dr, beginning_balance_cr, period_to_date_dr, period_to_date_cr, year_to_date_dr, year_to_date_cr FROM glbv_encumbrance_balances WHERE period_name = :period AND ledger_id = :ledger ORDER BY account_id, encumbrance_type;

To look for non-zero opening debit encumbrances:

SELECT account_id, period_name, encumbrance_type, beginning_balance_dr FROM glbv_encumbrance_balances WHERE beginning_balance_dr <> 0 AND period_name = :period;

Because balances appear at the account-combination and encumbrance-type grain, any aggregation or pivot must account for both dimensions. Security is applied automatically, so users require the appropriate GL data access privileges to see all ledgers and accounts.