Search Results batch_context




Overview
Explore in AI Chat

Overview

GL_JE_BATCHES_HEADERS_V is an Oracle EBS General Ledger (GL) view owned by the APPS schema, with status VALID in both 12.1.1 and 12.2.2. It is a join view that presents journal batch and journal header information in a single, denormalized result set. Rather than querying GL_JE_BATCHES and GL_JE_HEADERS independently, developers, report writers, and integrators use this view to retrieve batch-level attributes alongside their corresponding header-level attributes in one pass. The view exposes columns from both parent and child objects, prefixed with BATCH_ or HEADER_/ROW_ to disambiguate their origin. Note the naming convention is significant: batch columns carry the BATCH_ prefix, and the view also renames several header columns (for example, the header's own JE_BATCH_ID appears as HEADER_JE_BATCH_ID_QRY) to avoid collision with the batch's JE_BATCH_ID. This view is commonly referenced in custom reports, Oracle Discoverer/BI Publisher data models, interfaces, and conversion programs that need batch header context without maintaining their own joins.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, this view is defined over two objects: GL_JE_BATCHES (SYNONYM) and GL_JE_HEADERS (SYNONYM). These synonyms resolve to the base GL application tables of the same names. GL_JE_BATCHES is the parent table holding batch-level control and status data; GL_JE_HEADERS is the child table holding individual journal entry headers, related to batches through JE_BATCH_ID. The view text confirms an equi-join between the two, aliased B (batch) and H (header). Each row in the view therefore represents a journal header together with the attributes of the batch that contains it. Because the underlying objects are synonyms in the APPS schema, queries should normally be issued against the APPS-owned view or its public synonym.

Key Columns

The view surfaces a comprehensive set of batch and header attributes. Important batch-side columns include:

Header-side columns are prefixed HEADER_/ROW_ and include HEADER_ROW_ID, JE_HEADER_ID, and HEADER_JE_BATCH_ID_QRY (the header's batch foreign key).

Common Use Cases and Queries

Typical uses include reconciliations of batch control totals to header activity, status and posting audits, and extraction of batch descriptive flexfield data. A representative query listing batch context and status for a period:

SELECT je_batch_id,
       batch_name,
       batch_status,
       batch_context,
       batch_context2,
       batch_effective_date
FROM   apps.gl_je_batches_headers_v
WHERE  period_name = :p_period
  AND  batch_status = 'U';

To validate balancing, compare control and running totals:

SELECT je_batch_id,
       batch_control_total,
       batch_running_total_dr,
       batch_running_total_cr
FROM   apps.gl_je_batches_headers_v
WHERE  batch_control_total <> batch_running_total_dr - batch_running_total_cr;

Because the view joins batch and header rows, note that multi-header batches yield one row per header, so batch-level aggregates must account for this duplication when counted.