Search Results actual_journal_batch

Overview

GLBV_ACTUAL_JOURNAL_BATCHES is an Oracle E-Business Suite view owned by the APPS schema that exposes journal batch header information from the General Ledger for batches classified as actual (as opposed to budget or encumbrance). The view name derives from the GLBV prefix, which denotes a General Ledger Business View, and its suffix reflects the underlying GL_JE_BATCHES entity filtered to actual journal batches. It is a read-only view; the defining query terminates with WITH READ ONLY, so no DML may be performed against it.

Its core role in Oracle EBS 12.1.1 and 12.2.2 is to provide a secured, presentation-ready projection of journal batch data. Two characteristics distinguish it from a direct query against GL_JE_BATCHES. First, it restricts output to rows where ACTUAL_FLAG = 'A', excluding budget and encumbrance batches. Second, it embeds a data-access security predicate that joins the batch to GL_JE_HEADERS and then to GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, and, where applicable, GL_JE_SEGMENT_VALUES and GL_ACCESS_SET_ASSIGNMENTS, evaluated against GL_SECURITY_PKG.login_access_id. This ensures a session sees only batches belonging to ledgers and segment-value ranges within its assigned data access set. The view also resolves several coded columns into descriptive lookups and joins to secondary tables to return employee and user names, making it suitable for reporting layers and integrations that require decoded, security-filtered batch metadata.

Underlying Base Objects

The view is defined directly over a single base table, GL_JE_BATCHES, aliased as ACTUAL_JOURNAL_BATCH. The access-set security predicate references GL_JE_HEADERS (alias JEH), GL_ACCESS_SETS (ACC), GL_ACCESS_SET_LEDGERS (LGR), and, in the nested sub-query, GL_JE_SEGMENT_VALUES (SV) and GL_ACCESS_SET_ASSIGNMENTS (ASA). Two scalar sub-queries in the select list reference GL_HR_EMPLOYEES_CURRENT_V (for the approver name) and FND_USER (for the posted-by user name). The documented metadata lists no referenced base objects, so the relationships above are drawn from the view text itself. Key join logic: the outer batch is correlated to GL_JE_HEADERS on JE_BATCH_ID; the access set is correlated through GL_SECURITY_PKG.login_access_id; ledgers link via ACCESS_SET_ID and LEDGER_ID; and full ('F') privileges at either the security segment or ledger level bypass the more granular segment-value check.

Key Columns

• JE_BATCH_ID — primary identifier of the journal batch.
• NAME — batch name.
• STATUS — decoded batch status via GL_LOOKUPS (BATCH_STATUS).
• DEFAULT_PERIOD_NAME — default accounting period for the batch.
• POSTED_DATE, DATE_CREATED — posting and creation timestamps.
• DESCRIPTION — batch description.
• AVERAGE_JOURNAL_FLAG — decoded journal type via GL_LOOKUPS (AB_JOURNAL_TYPE).
• BUDGETARY_CONTROL_STATUS — decoded via GL_LOOKUPS (JE_BATCH_BC_STATUS).
• APPROVAL_STATUS_CODE — decoded via GL_LOOKUPS (JE_BATCH_APPROVAL_STATUS).
• CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_ACCOUNTED_DR, RUNNING_TOTAL_ACCOUNTED_CR — batch control and running debit/credit totals.
• APPROVER_EMPLOYEE_ID / approver name — approver identity, name resolved from GL_HR_EMPLOYEES_CURRENT_V.
• POSTED_BY / user name — posting user, name resolved from FND_USER.
• Two TO_NUMBER(NULL) placeholders appear for columns not populated by this view.

Common Use Cases and Queries

Typical uses include secured journal batch listings, reconciliation of posted totals, and feeds into downstream reporting or integration programs that must honor GL data access security. Because the view resolves lookup codes to descriptions, it is convenient for user-facing reports and BI Publisher data sets without additional lookup joins.

• List recent actual batches: SELECT je_batch_id, name, status, default_period_name, control_total FROM apps.glbv_actual_journal_batches ORDER BY date_created DESC;
• Filter by posting period: add WHERE default_period_name = :period.
• Identify approved batches: WHERE approval_status_code = 'APPROVED' (decoded value per JE_BATCH_APPROVAL_STATUS).
• Audit who posted: select POSTED_BY and its resolved user name.
• Balance check: compare CONTROL_TOTAL against RUNNING_TOTAL_DR and RUNNING_TOTAL_CR.

Because security is enforced inside the view, callers inherit the session's data access set automatically; no additional ledger filter is required, though adding one for performance is often advisable.