Search Results jgzz_recon_ref




Overview
Explore in AI Chat

Overview

GL_JE_LINES_RECON_V is an APPS-owned database view in the General Ledger product of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents journal entry line detail joined to reconciliation attributes, providing a denormalized reporting surface over the GL journal tables and the GL_JE_LINES_RECON reconciliation table. The view is validated and exposes both the standard journal line accounting content — entered and accounted debits and credits, period name, effective date, line number, status, and code combination — and the reconciliation metadata maintained by the JGZZ reconciliation columns introduced by the ETRM reconciliation functionality. As a view rather than a table, it carries no data of its own; it derives rows at runtime from its underlying synonyms, which means its availability and performance depend on the base tables and their indexes, not on any ETRM-managed storage. Its principal role is to support reporting and integration queries that need journal line balances alongside the reconciliation status and reference recorded for each line.

Underlying Base Objects

The documented metadata lists nine referenced base objects, all accessed through APPS synonyms: FND_DOCUMENT_SEQUENCES, GL_CODE_COMBINATIONS, GL_JE_BATCHES, GL_JE_CATEGORIES, GL_JE_HEADERS, GL_JE_LINES, GL_JE_LINES_RECON, GL_JE_SOURCES, and GL_PERIOD_STATUSES. The join topology is a classical GL reporting join: GL_JE_BATCHES supplies the batch name; GL_JE_HEADERS supplies header attributes including currency, description, external reference, and document sequence values; GL_JE_LINES supplies the line-level accounting amounts, period, status, and code combination; GL_CODE_COMBINATIONS supplies the individual accounting flexfield segments SEGMENT1 through SEGMENT30; GL_JE_SOURCES and GL_JE_CATEGORIES supply the user-facing source and category names; FND_DOCUMENT_SEQUENCES supplies the sequence name; GL_PERIOD_STATUSES supplies the effective period number; and GL_JE_LINES_RECON supplies the reconciliation columns JGZZ_RECON_STATUS, JGZZ_RECON_DATE, JGZZ_RECON_ID, and JGZZ_RECON_REF. The view therefore straddles two functional areas — core General Ledger journal content and the reconciliation extension — and any query against it will implicitly require access to all nine objects.

Key Columns

Common Use Cases and Queries

Typical usage includes reconciliation reporting, audit extracts of journals with their reconciliation references, and integration queries that reconcile General Ledger journal lines against an external system using the JGZZ reconciliation reference. Because the view exposes entered and accounted amounts together with the accounting flexfield segments and reconciliation status, it is convenient for period-end reconciliation listings.

A minimal query retrieving reconciliation references for a ledger and period:

  • SELECT je_header_id, je_line_num, period_name, segment1, segment2, entered_dr, entered_cr, jgzz_recon_status, jgzz_recon_date, jgzz_recon_ref FROM gl_je_lines_recon_v WHERE ledger_id = :ledger_id AND period_name = :period_name ORDER BY je_header_id, je_line_num;

To locate specific reconciliation references:

  • SELECT je_header_id, je_line_num, jgzz_recon_id, jgzz_recon_ref FROM gl_je_lines_recon_v WHERE jgzz_recon_ref = :reference;

Because the view is a multi-table join, predicates on LEDGER_ID, PERIOD_NAME, JE_HEADER_ID, or JGZZ_RECON_REF are important for restricting the driving set of rows and avoiding unnecessary processing across the large GL_JE_LINES population. All queries must reference the view with the APPS schema or an appropriate synonym context.