Search Results encumb_journal_batch

Overview

APPS.GLBV_ENCUMB_JOURNAL_BATCHES is a read-only Oracle EBS view that exposes encumbrance journal batches for reporting and integration purposes. It is defined as a "WITH READ ONLY" view, meaning it cannot be used for DML operations and serves strictly as a query surface. The view selects from GL_JE_BATCHES (aliased as ENCUMB_JOURNAL_BATCH), filtered to rows where ACTUAL_FLAG = 'E', so it isolates encumbrance batches from the broader journal batch population. The "GLBV" prefix reflects its role as a General Ledger Business View, a class of views commonly used by Oracle Business Intelligence, Discoverer, and other reporting tools to present GL batch data in a business-friendly form without exposing the raw transactional table directly.

The reference to "LA" lookup tags embedded in the SELECT list (such as '_LA:ENCUMB_JOURNAL_BATCH.STATUS:GL_LOOKUPS:BATCH_STATUS:DESCRIPTION') indicates this view is designed to participate in Oracle's Lookups/Alias (LA) mechanism, where coded values in the underlying tables are resolved to human-readable descriptions at query time through the GL_LOOKUPS table.

Underlying Base Objects

Although the documented base objects are listed as none, the view text shows it is defined primarily over GL_JE_BATCHES. Supporting objects referenced in the definition include GL_HR_EMPLOYEES_CURRENT_V (a subquery resolves APPROVER_EMPLOYEE_ID to a name), FND_USER (to resolve POSTED_BY to a user name), and GL_JE_HEADERS for the EXISTS access-control clause.

Data security is enforced through GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, and GL_ACCESS_SET_ASSIGNMENTS. The EXISTS predicate uses GL_SECURITY_PKG.login_access_id to restrict rows to ledgers and segments the current session is authorized to view, honoring both full access (SECURITY_SEGMENT_CODE 'F' or ACCESS_PRIVILEGE_CODE 'F') and segment-value-level access via GL_JE_SEGMENT_VALUES.

Key Columns

• JE_BATCH_ID — primary key of the batch.
• NAME — batch name.
• STATUS — lookup-derived description from GL_LOOKUPS (BATCH_STATUS).
• DEFAULT_PERIOD_NAME — accounting period the batch posts to.
• POSTED_DATE / DATE_CREATED — posting and creation timestamps.
• DESCRIPTION — free-text batch description.
• BUDGETARY_CONTROL_STATUS — lookup-derived meaning (JE_BATCH_BC_STATUS).
• APPROVAL_STATUS_CODE — lookup-derived approval meaning (JE_BATCH_APPROVAL_STATUS).
• CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR — batch control and debit/credit totals.
• APPROVER_EMPLOYEE_ID and resolved employee name.
• POSTED_BY and resolved FND user name.

Common Use Cases and Queries

Typical uses include encumbrance reporting, budget-versus-actual reconciliation, and batch control audits. A simple query lists encumbrance batches for a period:

• SELECT je_batch_id, name, default_period_name, control_total, posted_date FROM apps.glbv_encumb_journal_batches WHERE default_period_name = :period;
• SELECT name, status, approval_status_code, approver_employee_id FROM apps.glbv_encumb_journal_batches ORDER BY date_created DESC;

Because access is filtered by GL security, queries automatically return only authorized data, making the view suitable for self-service reporting. The "editor" search term likely reflects a user looking at the LA lookup metadata in the view definition.