Search Results glbv_journal_batches




Overview
Explore in AI Chat

Overview

GLBV_JOURNAL_BATCHES is a read-only General Ledger view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents journal batch header information from GL_JE_BATCHES, but only for those batches that the currently logged-in user is authorized to see. It is best understood as a security-filtered, presentation-ready batch inquiry view rather than a base data source.

The "BV" prefix and the presence of column aliases such as "_LA:BATCH_STATUS" indicate that this view is designed for use by Oracle Application Framework (OAF) pages, specifically the Journals workbench and batch inquiry screens. Rather than storing data, it derives descriptive flexfield and lookup meanings at runtime, translating internal code values into user-facing descriptions.

Underlying Base Objects

ETRM formally documents no referenced base objects for this view, though the shipped view text clearly derives from GL_JE_BATCHES (aliased JOURNAL_BATCH), which supplies every direct column. The view also references GL_JE_HEADERS, GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, GL_JE_SEGMENT_VALUES, and GL_ACCESS_SET_ASSIGNMENTS inside an EXISTS subquery that enforces access-set security. Two correlated scalar subqueries resolve the approver's name from GL_HR_EMPLOYEES_CURRENT_V and the posting user's name from FND_USER.

The view is declared WITH READ ONLY, confirming it is intended strictly for query and reporting rather than DML.

Key Columns

  • JOURNAL_BATCH_ID — The surrogate key (JE_BATCH_ID) uniquely identifying the batch.
  • JOURNAL_BATCH_NAME — The user-defined batch name.
  • LEDGER_ID — Exposed as a NULL placeholder in the view text; ledger context is resolved through the access-set subquery.
  • "_LA:BATCH_STATUS" — Lookup-driven description of the batch status, derived from GL_LOOKUPS (BATCH_STATUS).
  • "_LA:BALANCE_TYPE" — Description of the batch's actual flag (Actual, Budget, Encumbrance) from GL_LOOKUPS (BATCH_TYPE).
  • PERIOD_NAME — The default accounting period assigned to the batch.
  • DATE_POSTED / DATE_CREATED — Posting and creation timestamps.
  • DESCRIP — Free-text batch description.
  • Approver and Posted By — Employee name and FND user name resolved via scalar subqueries for approver and posting user respectively.
  • Control and running totals — CONTROL_TOTAL, RUNNING_TOTAL_DR/CR, and the corresponding accounted totals used for batch balancing checks.

Common Use Cases and Queries

This view supports batch inquiry, reconciliation, and security-aware reporting. Because it applies the same access-set logic used by the GL Security package, it is suitable for exposing batch data to users whose ledger and balancing-segment privileges vary. It is commonly queried from concurrent programs, OAF-based inquiries, and custom reports where row-level ledger security must be respected.

  • List recent posted batches:
SELECT journal_batch_id, journal_batch_name, period_name,
       date_posted, "_LA:BATCH_STATUS" status
FROM   apps.glbv_journal_batches
WHERE  date_posted IS NOT NULL
ORDER BY date_posted DESC;
  • Find batches out of balance:
SELECT journal_batch_id, journal_batch_name, control_total,
       running_total_dr, running_total_cr
FROM   apps.glbv_journal_batches
WHERE  running_total_dr <> running_total_cr;
  • Batch approval tracking: select the approver and posted-by names to audit who authorized and released each batch.

Because the view enforces security through GL_SECURITY_PKG.LOGIN_ACCESS_ID, queries must be executed in a session context that has a valid login access set; concurrent programs and self-service pages automatically satisfy this requirement.