Search Results converted_batch_total_cr




Overview
Explore in AI Chat

Overview

APPS.GLBV_JOURNAL_BATCHES is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents General Ledger journal batch information in a denormalized, reporting-friendly form. Journal batches are groups of related journal entries that share the same General Ledger period, and this view exposes batch-level attributes alongside translated (lookup-decoded) status values and posted-by descriptors that are otherwise scattered across base tables.

The object is registered under FND Design Data as SQLGL.GLBV_JOURNAL_BATCHES with a status of VALID. Because it is a view rather than a table, it holds no data of its own; every query resolves against the underlying General Ledger and HR tables at runtime. The "BV" naming convention identifies it as a business view intended for ad-hoc query, reporting, and integration consumption rather than for transactional insert, update, or delete operations. The columns prefixed with _LA: are columns whose underlying lookup codes are automatically translated into descriptive meanings by the BIS view definition, simplifying interpretation for report authors.

Underlying Base Objects

The view is defined over a documented dependency set that includes APPS.GL_JE_BATCHES, which supplies the core batch record, and APPS.GL_JE_HEADERS for journal header level attributes. Segment and security context is provided through APPS.GL_JE_SEGMENT_VALUES, APPS.GL_ACCESS_SETS, APPS.GL_ACCESS_SET_ASSIGNMENTS, APPS.GL_ACCESS_SET_LEDGERS, and APPS.GL_SECURITY_PKG, which together enforce ledger and data-access security for the querying user.

Employee and user information is drawn from APPS.GL_HR_EMPLOYEES_CURRENT_V, APPS.FND_USER, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY, supporting the APPROVER, APPROVER_EMPLOYEE_ID, POSTED_BY, and POSTED_BY_ID columns. The view is not referenced by any dependent database objects, confirming its role as a terminal reporting object. No base objects are separately documented in the ETRM 12.2.2 metadata beyond this reference list.

Key Columns

Common Use Cases and Queries

The view is typically used to report on posting activity, audit posted batches within a period, and reconcile batch control totals. A representative query filtering on the searched column is:

SELECT JOURNAL_BATCH_ID, JOURNAL_BATCH_NAME, PERIOD_NAME, DATE_POSTED, POSTED_BY, CONTROL_TOTAL FROM APPS.GLBV_JOURNAL_BATCHES WHERE DATE_POSTED BETWEEN :p_from AND :p_to ORDER BY DATE_POSTED;

Additional scenarios include identifying unposted batches (WHERE _LA:BATCH_STATUS = 'Unposted'), reconciling entered versus converted totals, and auditing approval versus posting users. Because the view enforces GL and HR security through its dependent packages, results are automatically restricted to ledgers and employees the querying user is authorized to see. All access should be read-only.