Search Results batch_context2




Overview
Explore in AI Chat

Overview

GL_JE_BATCHES_HEADERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined by the ETRM repository as a VALID object within the General Ledger (GL) product family. In both 12.1.1 and 12.2.2, this view is a denormalized join that flattens the parent journal batch record together with its child journal header records, exposing the two levels of the GL journal hierarchy through a single access point. Because a journal entry batch (GL_JE_BATCHES) can contain multiple journal headers (GL_JE_HEADERS), the view returns one row per header while repeating the batch-level attributes on each row. This design makes the view particularly convenient for batch and header status reporting, posting and reconciliation queries, and integration interfaces that need to consume both the batch context and its constituent headers without performing the join themselves.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through synonyms: GL_JE_BATCHES and GL_JE_HEADERS. The batch table supplies the columns prefixed with BATCH_ in the projection, while the header table supplies the header columns. The view text aliases the batch table as B and the header table as H, and it begins with B.ROWID as BATCH_ROW_ID and H.ROWID as ROW_ID and HEADER_ROW_ID, preserving row identifiers for both levels. The join key is JE_BATCH_ID, which appears as B.JE_BATCH_ID and H.JE_BATCH_ID, with the header-side copy additionally exposed as HEADER_JE_BATCH_ID_QRY. Because GL_JE_HEADERS is the child of GL_JE_BATCHES, the view effectively reports the many-to-one relationship between headers and batches as an outer-facing row set keyed at header granularity.

Key Columns

The view projects a broad set of batch and header attributes. Batch-level columns include JE_BATCH_ID, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE, PERIOD_NAME, ACTUAL_FLAG (distinguishing actual from budget journals), BATCH_STATUS, BUDGETARY_CONTROL_STATUS, BATCH_NAME, BATCH_DESCRIPTION, BATCH_DATE_CREATED, BATCH_POSTED_DATE, BATCH_CONTROL_TOTAL, the running total columns BATCH_RUNNING_TOTAL_DR/CR and BATCH_RUN_TOTAL_ACCOUNTED_DR/CR, APPROVAL_STATUS_CODE, POSTING_RUN_ID, REQUEST_ID, and STATUS_VERIFIED. The descriptive flexfield columns BATCH_ATTRIBUTE1 through BATCH_ATTRIBUTE10, BATCH_CONTEXT, and BATCH_CONTEXT2 are also exposed—BATCH_CONTEXT2 being the column referenced in the search term batch_context2. Header-level columns include JE_HEADER_ID, HEADER_ROW_ID, and the header batch reference HEADER_JE_BATCH_ID_QRY. Audit columns such as BATCH_CREATED_BY, BATCH_CREATION_DATE, BATCH_LAST_UPDATED_BY, and BATCH_LAST_UPDATE_DATE support lineage and troubleshooting.

Common Use Cases and Queries

Typical uses include batch status dashboards, unposted journal monitoring, posting-run reconciliation, and custom integrations that read batch and header context in one pass. A representative query follows:

  • SELECT je_batch_id, batch_name, period_name, batch_status, je_header_id FROM gl_je_batches_headers_v WHERE period_name = 'JAN-24';
  • SELECT je_batch_id, je_header_id, batch_context, batch_context2 FROM gl_je_batches_headers_v WHERE batch_context2 = :context_value;
  • SELECT je_batch_id, batch_control_total, batch_running_total_dr, batch_running_total_cr FROM gl_je_batches_headers_v WHERE batch_status = 'U';
  • SELECT batch_name, batch_posted_date, je_header_id FROM gl_je_batches_headers_v WHERE posting_run_id IS NOT NULL;

Because the view repeats batch attributes for every header, aggregate queries should group by JE_BATCH_ID to avoid double counting batch totals. The BATCH_CONTEXT2 column is commonly queried to retrieve descriptive flexfield segments captured at batch entry, making the view a practical source for context-driven reporting and downstream data extracts.