Search Results gl_je_journal_lines_v




Overview
Explore in AI Chat

Overview

GL_JE_JOURNAL_LINES_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger. It presents journal entry data across all three levels of the GL journal model — batch, header, and line — as a single flat row set, joined to period status and ledger relationship information. The view is defined in the ETRM metadata as a VALID object under the GL product for both 12.1.1 and 12.2.2. Its purpose is to provide a convenient, query-ready projection of journal batches, headers, and distribution lines without requiring the caller to reconstruct the batch-to-header-to-line joins, decode the ACTUAL_FLAG dimension, or resolve period year and period number values manually. This makes it a natural fit for custom reports, data extracts, reconciliation scripts, and integration interfaces that must reproduce GL journal content outside the standard Oracle forms and concurrent programs. The view text itself is generated by the GLR03300_PKG package, indicating Oracle builds the defining query programmatically rather than maintaining it as static SQL.

Underlying Base Objects

The documented base objects referenced by the view are GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES (all exposed as APPS synonyms), alongside GL_LEDGER_RELATIONSHIPS and GL_PERIOD_STATUSES, with GLR03300_PKG as the defining package. GL_JE_BATCHES supplies batch-level control and status information, aliased as B in the view text; GL_JE_HEADERS supplies header-level attributes such as journal source and category, aliased as H; and GL_JE_LINES supplies the accounting distribution rows, which carry the code combination and entered/debited/credited amounts. GL_PERIOD_STATUSES contributes PERIOD_YEAR, PERIOD_NUM, and EFFECTIVE_PERIOD_NUM for the batch default period. GL_LEDGER_RELATIONSHIPS is used in DECODE expressions that null out the accounted running totals for 'BALANCE' relationship types, so that primary and secondary ledger figures are not double-counted in reporting.

Key Columns

The view exposes batch attributes including JE_BATCH_ID, PERIOD_NAME, LEDGER_ID, ACTUAL_FLAG, BATCH_STATUS, BATCH_CONTROL_TOTAL, BATCH_RUNNING_TOTAL_DR, and BATCH_RUNNING_TOTAL_CR, plus the BATCH_RUN_TOTAL_ACCOUNTED_DR/CR pair that is conditionally suppressed based on ledger relationship type. Header columns include JE_HEADER_ID, HEADER_NAME, JE_SOURCE, and JE_CATEGORY. Line-level identifiers include JE_HEADER_ID and the journal line identity used to tie back to GL_JE_LINES. The column most frequently sought by users, line_code_combination_id, identifies the accounting flexfield combination assigned to each journal line — the key that links the distribution to the chart of accounts and, through it, to account balances. Entered and accounted debit/credit amounts, currency information, and statistical flags are also carried at the line level.

Common Use Cases and Queries

Typical usage includes extracting all lines for a given code combination to trace postings, reconciling batch control totals against line sums, and feeding downstream subledger or data-warehouse processes. A representative query is:

  • SELECT je_batch_id, je_header_id, period_name, je_source, je_category, line_code_combination_id, entered_dr, entered_cr FROM gl_je_journal_lines_v WHERE period_name = :period AND ledger_id = :ledger;
  • Filtering on line_code_combination_id to isolate activity for one account across journals.
  • Joining to GL_CODE_COMBINATIONS to resolve segment values for reporting.
  • Aggregating BATCH_RUNNING_TOTAL_DR/CR to reconcile batch control totals.

Because the view carries no ROWID-based update path and omits statutory or subledger-specific columns, it is intended for read-only querying; inserts and updates must target the underlying base tables.