Search Results batch_effective_date




Overview
Explore in AI Chat

Overview

GL_JOURNAL_REPORTS_ITF_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite General Ledger (GL) module. It is defined as a denormalized, read-only interface that consolidates journal batch, header, and control information into a single queryable structure. Rather than exposing the numerous normalized tables that underlie General Ledger journal processing, the view presents a flattened projection suited to journal entry reporting, extract generation, and downstream integration. Its status is documented as VALID in the ETRM repository for releases 12.1.1 and 12.2.2.

The view is oriented toward the journal reporting interface table (GL_JOURNAL_REPORTS_ITF), from which it derives its core column set, and is joined against the master transaction tables to resolve descriptive attributes such as batch name, category name, source name, and the identity of the last updater. Because it is a view, it carries no persisted data of its own; every access executes the underlying join. The ORDERED and USE_NL hints embedded in its definition indicate that the optimizer is deliberately directed to drive from the interface table and use nested loops, reflecting an expectation of selective, indexed access patterns.

Underlying Base Objects

The documented base objects referenced by the view are APPS synonyms resolving to the following tables:

  • FND_USER — supplies the user name of the header last updater.
  • GL_JE_BATCHES — provides batch-level attributes including name, status, dates, and running totals.
  • GL_JE_CATEGORIES — supplies the user-defined journal category name.
  • GL_JE_HEADERS — supplies header-level currency, conversion, totals, and reference data.
  • GL_JE_LINES — the journal line detail associated with each header.
  • GL_JE_SOURCES — supplies the user-defined journal source name.
  • GL_JOURNAL_REPORTS_ITF — the driving interface table from which ROWID, request ID, audit columns, and batch identifiers are selected.

The view therefore bridges the journal reporting interface with the operational GL journal tables, resolving surrogate identifiers into meaningful descriptive values.

Key Columns

Columns are grouped by the reporting grain they serve:

Common Use Cases and Queries

Typical uses include reconciliation of journal batches against reporting extracts, audit of posted and unposted journals, and extraction of journal detail for external reporting or reconciliation tooling. Because the view is keyed to REQUEST_ID, it supports request-scoped reporting runs.

A sample query retrieving batch-level totals for a specific reporting request:

  • SELECT REQUEST_ID, BATCH_NAME, BATCH_STATUS, BATCH_PERIOD_NAME, BATCH_RUN_TOTAL_DR, BATCH_RUN_TOTAL_CR FROM APPS.GL_JOURNAL_REPORTS_ITF_V WHERE REQUEST_ID = :p_request_id ORDER BY BATCH_NAME;

To inspect header-level currency and conversion detail:

  • SELECT HEADER_ID, HEADER_NAME, CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_DATE, HEADER_RUN_TOTAL_DR, HEADER_RUN_TOTAL_CR FROM APPS.GL_JOURNAL_REPORTS_ITF_V WHERE CURRENCY_CODE <> FUNCTIONAL_CURRENCY_CODE;

To identify journals by source and category for a given period:

  • SELECT BATCH_PERIOD_NAME, HEADER_SOURCE, HEADER_CATEGORY, COUNT(*) FROM APPS.GL_JOURNAL_REPORTS_ITF_V WHERE BATCH_PERIOD_NAME = :p_period GROUP BY BATCH_PERIOD_NAME, HEADER_SOURCE, HEADER_CATEGORY;

Consumers should apply result-set and indexing awareness when querying large datasets, since the view performs nested-loop joins across multiple GL tables and its cost scales with interface table volume.