Search Results entered_batch_total_dr




Overview
Explore in AI Chat

Overview

GLBV_ENCUMB_JOURNAL_BATCHES is a read-only Oracle EBS view owned by the APPS schema in the General Ledger (GL) product. It exposes encumbrance journal batches — journal batch records whose ACTUAL_FLAG is set to 'E' — and is primarily intended for reporting, inquiry, and integration use where encumbrance activity must be presented in a user-friendly, security-filtered form. The prefix "BV" indicates a business view, and the column aliases using the "_LA:" convention denote descriptive flexfield or value-set-backed attributes that are resolved dynamically at runtime (for example, BATCH_STATUS and APPROVAL_STATUS are displayed through GL_LOOKUPS).

The view is relevant to users searching on date_posted. The column DATE_POSTED (mapped from GL_JE_BATCHES.POSTED_DATE) records the date the encumbrance batch was posted to the ledger. Because the view restricts to encumbrance batches only, DATE_POSTED is only populated once the batch has been posted; unposted encumbrances will return NULL for this column. This makes it a natural filter for reconciliation and period-close reporting.

Underlying Base Objects

The view is defined over GL_JE_BATCHES, aliased internally as ENCUMB_JOURNAL_BATCH. The WHERE clause enforces two conditions: the batch must have ACTUAL_FLAG = 'E' (encumbrance), and the batch must be visible to the logged-in user's security context.

Security is applied through a correlated EXISTS subquery joining GL_JE_HEADERS, GL_ACCESS_SETS, and GL_ACCESS_SET_LEDGERS, with additional resolution against GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS. This enforces data-access-set (security segment and privilege) restrictions so that only batches belonging to ledgers and segment values the user may see are returned. Two scalar subqueries enrich the result: GL_HR_EMPLOYEES_CURRENT_V resolves the approver's employee name, and FND_USER resolves the posting user's name. The view is defined WITH READ ONLY.

Key Columns

Common Use Cases and Queries

Typical scenarios include period-close reconciliation of encumbrance postings, auditing who posted which encumbrance batch, and integration extracts feeding downstream budgeting or reporting systems. Because the view is security-aware, it can be queried directly without re-implementing access-set logic.

  • Listing encumbrance batches posted within a period: SELECT JOURNAL_BATCH_NAME, PERIOD_NAME, DATE_POSTED FROM GLBV_ENCUMB_JOURNAL_BATCHES WHERE DATE_POSTED BETWEEN :start_date AND :end_date;
  • Reviewing unposted encumbrances: SELECT JOURNAL_BATCH_NAME FROM GLBV_ENCUMB_JOURNAL_BATCHES WHERE DATE_POSTED IS NULL;
  • Auditing approver and posting user activity for encumbrances within a ledger security context.

Note that LEDGER_ID is returned as NULL, so ledger-based filtering should be performed through related GL views or base tables rather than this column.