Search Results close_acct_seq_value




Overview
Explore in AI Chat

Overview

The view GLFV_ENCUMB_JOURNAL_ENTRIES is a General Ledger (GL) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes encumbrance journal entry headers in a flattened, security-filtered form. Its name follows the standard Oracle EBS convention of a "GLFV" prefix, indicating a General Ledger view intended for form and inquiry access. The view consolidates attributes from journal headers, batches, ledgers, categories, sources, and encumbrance types into a single denormalized row per encumbrance journal entry, so that downstream reporting, inquiry forms, and integrations can retrieve encumbrance activity without joining the base GL tables manually. Because it embeds GL_SECURITY_PKG.LOGIN_ACCESS_ID logic, the view returns only those journal entries the logged-in user is authorized to see under the active access set.

Underlying Base Objects

Per the documented view text, GLFV_ENCUMB_JOURNAL_ENTRIES is defined over the following base objects. GL_JE_HEADERS appears three times as the primary and self-joined alias sources (JE1, JE2, JE3) to resolve parent and reversed header names. Supporting tables include GL_LEDGERS, GL_ENCUMBRANCE_TYPES, GL_JE_BATCHES, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_ACCESS_SETS, and GL_ACCESS_SET_LEDGERS. Data-security filtering is enforced through the access-set tables and, where segment-level security applies, through correlated subqueries against GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS. Note that the ETRM metadata records no independently documented referenced base objects and states the view is not implemented in the source database from which the metadata was captured.

Key Columns

Common Use Cases and Queries

Typical uses include encumbrance inquiry forms, period-end encumbrance reporting, commitment/obligation analysis, and reconciliation of budget-check activity. Because the view applies access-set security internally, queries automatically respect the caller's ledger and segment privileges. A representative query selecting the searched REFERENCE_DATE alongside core encumbrance attributes follows:

  • SELECT je_header_id, name, ledger_id, period_name, encumbrance_type, reference_date, control_total, running_total_dr, running_total_cr FROM glfv_encumb_journal_entries WHERE reference_date BETWEEN :start_date AND :end_date;
  • Filter by encumbrance type: ... WHERE encumbrance_type = :enc_type AND period_name = :period;
  • Drill to reversal links: SELECT name, parent_je_header_id, reversed_je_header_id, accrual_rev_status FROM glfv_encumb_journal_entries WHERE period_name = :period;

Consultants should confirm the view's implementation status in each target environment, since the captured metadata records it as not implemented in the source database.