Search Results igi_eer_je_lines_v

Overview

IGI_EER_JE_LINES_V is a reporting view owned by the APPS schema within the IGI – Public Sector Financials International product family in Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents journal entry line detail drawn from the General Ledger transaction model, joining batches, headers, and lines into a single denormalized result set. The view is designed to support external reporting, data extraction, and integration scenarios where consumers require journal line amounts alongside their batch and header context without having to reconstruct the three-way join themselves. Because it is defined over the GL journal tables but owned by the IGI module, it is most often encountered in public sector implementations that use IGI extensions layered on top of standard General Ledger functionality.

Users typically reach this object when searching for gl_je_lines, since the view is a thin, pre-joined projection of that base table. The view is documented as VALID in the ETRM metadata, confirming that its definition compiles cleanly against the referenced synonyms.

Underlying Base Objects

The view is defined explicitly over three General Ledger base objects, each referenced through a SYNONYM in the APPS schema:

• GL_JE_BATCHES — the journal batch, aliased as BAT, supplying batch identity and name.
• GL_JE_HEADERS — the journal header, aliased as HDR, supplying the journal entry name and source.
• GL_JE_LINES — the journal line, aliased as JEL, supplying line number, period, account, description, and accounted amounts.

The join predicates link HDR.JE_HEADER_ID to JEL.JE_HEADER_ID and HDR.JE_BATCH_ID to BAT.JE_BATCH_ID. The view text selects the row identifier from GL_JE_LINES, so the grain of the result set is one row per journal line, enriched with its parent header and batch attributes. No outer joins are used in the documented definition, so only lines with valid header and batch parents are returned.

Key Columns

• ROW_ID — the ROWID of the underlying GL_JE_LINES row, useful for precise row identification and updates.
• JE_HEADER_ID — foreign key to the journal header that owns the line.
• JE_LINE_NUM — the line number within the journal entry.
• PERIOD_NAME — the accounting period to which the line is posted.
• CODE_COMBINATION_ID — the accounting flexfield combination for the line.
• BATCH_NAME — the descriptive name of the parent journal batch.
• JE_BATCH_ID — the unique identifier of the parent batch.
• JOURNAL_ENTRY — the descriptive name of the journal header.
• JE_SOURCE — the source of the journal entry, identifying the originating subledger or manual entry.
• DESCRIPTION — the free-text description carried on the journal line.
• ACCOUNTED_DR — the accounted debit amount for the line.
• ACCOUNTED_CR — the accounted credit amount for the line.

Common Use Cases and Queries

Typical use cases include reconciliation of accounted debits and credits by period, extraction of journal detail for external reporting or data warehouse loads, audit review of manual versus subledger-sourced journals, and verification of batch totals against summed line amounts. A representative query follows.

SELECT je_header_id, je_line_num, period_name, batch_name, journal_entry, je_source, accounted_dr, accounted_cre FROM igi_eer_je_lines_v WHERE period_name = :period_name ORDER BY batch_name, journal_entry, je_line_num;

Because the view exposes CODE_COMBINATION_ID rather than a concatenated account string, consumers needing the descriptive account typically join to GL_CODE_COMBINATIONS or FND_FLEX_VALUES_VL on that identifier. Filtering by JE_SOURCE is a common technique for isolating journals originating from a specific subledger, while aggregating ACCOUNTED_DR and ACCOUNTED_CR by JE_BATCH_ID provides a rapid batch-level control total. The view is read-only and should be treated as a reporting construct rather than a maintenance path; DML against journal data must always target the GL_JE_LINES base table directly.