Search Results igi_com_gl_je_lines_v




Overview
Explore in AI Chat

Overview

The IGI_COM_GL_JE_LINES_V view is a reporting object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product. It presents a denormalized, joined perspective of General Ledger journal entry data, combining header, batch, line, and journal source information into a single queryable structure. Its primary role is to expose journal lines together with their associated batch and header context, which simplifies ad-hoc reporting, reconciliation extracts, and downstream integration logic that would otherwise require joining multiple GL base tables.

A defining characteristic of the view is that it is not a raw mirror of the General Ledger tables. The WHERE clause restricts the result set to headers whose status equals 'P', meaning only posted journal entries are returned. Additionally, the join to GL_JE_SOURCES_TL is filtered by LANGUAGE = USERENV('LANG'), so the journal source name is returned in the language of the current session. Because the view does not expose a batch description column named identically to the base table, users searching for batch_description will find it aliased as BATCH_DESCRIPTION (sourced from GL_JE_BATCHES.DESCRIPTION).

Underlying Base Objects

The view is defined over four base objects within the APPS schema:

The joins are established on JE_BATCH_ID (batches to headers) and JE_HEADER_ID (headers to lines), producing one row per journal line with the full batch-to-header-to-line hierarchy repeated in each row. ETRM metadata additionally lists DUAL (via a synonym) as a referenced base object, which reflects the internal dependency chain rather than a functional join, since DUAL is used in Oracle's internal view compilation and resolution machinery.

Key Columns

  • ROW_ID — the ROWID of the underlying GL_JE_LINES row, a unique line-level identifier useful for record-level tracing.
  • JE_BATCH_ID, JE_HEADER_ID — foreign keys linking back to the batch and header records respectively.
  • BATCH_NAME, BATCH_DESCRIPTION, BATCH_STATUS — batch-level identification and posting status of the parent journal batch.
  • HEADER_NAME, HEADER_DESCRIPTION, JE_CATEGORY, JE_SOURCE, USER_JE_SOURCE_NAME — header-level identification, including the translated journal source name.
  • PERIOD_NAME, SET_OF_BOOKS_ID, CURRENCY_CODE, ACTUAL_FLAG — accounting period, ledger, currency, and actual/budget indicator.
  • LINE_JE_LINE_NUM, LINE_CODE_COMBINATION_ID, LINE_ENTERED_DR, LINE_ENTERED_CR, LINE_DESCRIPTION — line-level detail for amounts, accounting flexfield combinations, and narrative.
  • BUDGET_VERSION_ID, ENCUMBRANCE_TYPE_ID — populate for budget and encumbrance journal entries respectively.

Common Use Cases and Queries

Typical scenarios include reconciling posted journal activity by batch and period, extracting journal lines for a specific ledger or source, and feeding downstream reporting or integration processes. Because only posted headers are returned, the view is well suited to finalized accounting data extraction.

To retrieve all lines for a batch using its description:

SELECT batch_name, batch_description, header_name,
       line_je_line_num, line_entered_dr, line_entered_cr
FROM   apps.igi_com_gl_je_lines_v
WHERE  batch_description = :p_batch_description;

To summarize posted journal amounts by period and source:

SELECT period_name, user_je_source_name,
       SUM(line_entered_dr) AS total_dr,
       SUM(line_entered_cr) AS total_cr
FROM   apps.igi_com_gl_je_lines_v
GROUP  BY period_name, user_je_source_name;

Because the view enforces the posted-status and session-language filters internally, consumers should be aware that unposted journals and non-current-language source translations will not appear, and that results are inherently one row per journal line.