Search Results gl_je_lines_recon_u1




Overview

GL.GL_JE_LINES_RECON is a General Ledger reconciliation table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores reconciliation state and reference information for individual journal entry lines. Physically it belongs to the GL schema, is registered under FND Design Data as SQLGL.GL_JE_LINES_RECON, holds status VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its indexes live in APPS_TS_TX_IDX. Functionally, the table extends the core journal line identity (header plus line number) with reconciliation attributes, notably reconciliation status, date, identifier, and reference. It is delivered with a warning that it is for Oracle Internal Use Only and unsupported for direct customer access outside standard Oracle Applications programs, which is typical of "recon"-suffixed staging and control objects.

Mined from its foreign key structure, the heuristic Data Vault classification for this object is link. In Data Vault modeling terms it behaves less like a pure transactional fact and more like a relationship/association record binding a journal line to a reconciliation event or reference, with descriptive attributes attached. This should be treated as a modeling suggestion rather than an Oracle-supplied classification.

Key Information Stored

The table contains twelve documented columns. The most important are the following:

  • JE_HEADER_ID (NUMBER 15, mandatory) — journal entry header defining column; first component of the primary key.
  • JE_LINE_NUM (NUMBER 15, mandatory) — journal entry line number; second component of the primary key.
  • LEDGER_ID (NUMBER 15) — ledger defining column, used to scope reconciliation by ledger.
  • JGZZ_RECON_STATUS (VARCHAR2) — reconciliation status of the line, the principal state indicator.
  • JGZZ_RECON_DATE (DATE) — date the reconciliation was performed.
  • JGZZ_RECON_ID (NUMBER) — reconciliation identifier, linking the line to a reconciliation grouping or run.
  • JGZZ_RECON_REF (VARCHAR2 240) — free-form reconciliation reference used to record the match source or remark.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns providing audit trail and concurrency information.

Physically the primary key GL_JE_LINES_RECON_PK is documented as (JE_HEADER_ID, JE_LINE_NUM), and the unique index GL_JE_LINES_RECON_U1 on the same two columns is the business-key candidate (the user search term). GL_JE_LINES_RECON_N1 is a non-unique index on (JGZZ_RECON_ID, JGZZ_RECON_REF), and GL_JE_LINES_RECON_N2 is a non-unique index on (JGZZ_RECON_STATUS, LEDGER_ID), supporting status-based reporting by ledger.

Common Use Cases and Queries

Typical uses include reconciliation status reporting, identifying unreconciled journal lines, and auditing reconciliation activity by ledger or reconciliation reference. A representative query projects the reconciliation attributes for a given ledger and status, exploiting the GL_JE_LINES_RECON_N2 index path:

  • Filter by LEDGER_ID and JGZZ_RECON_STATUS to list lines in a particular reconciliation state.
  • Join to GL_JE_HEADERS on JE_HEADER_ID to obtain journal name, period, and journal source for reconciliation reports.
  • Join to GL_LEDGERS on LEDGER_ID to resolve ledger name and currency.
  • Group by JGZZ_RECON_STATUS to produce dashboard counts of reconciled versus outstanding lines.
  • Search on JGZZ_RECON_REF to trace a line back to an external reconciliation reference.

Because the object is flagged Oracle Internal Use Only, queries should be read-only; any write-back must occur through supported Oracle reconciliation programs rather than direct DML.

Related Objects

The most significant related objects, grounded in the documented dependency and foreign key data, are:

  • GL.GL_JE_HEADERS — referenced via GL_JE_LINES_RECON.JE_HEADER_ID → GL_JE_HEADERS; provides header context such as journal source, category, and period.
  • GL.GL_LEDGERS — referenced via GL_JE_LINES_RECON.LEDGER_ID → GL_LEDGERS; resolves ledger identity and attributes.
  • GL.GL_JE_LINES — the base journal line entity sharing the JE_HEADER_ID / JE_LINE_NUM key with this reconciliation table.
  • GL.GL_JE_LINES_RECON# — the shadow/base object explicitly listed as referencing GL.GL_JE_LINES_RECON in the dependency information.

The table is documented as referencing no other database objects beyond the two foreign keys above, and no additional dependents beyond GL_JE_LINES_RECON# are listed in the supplied metadata. Any reconciliation processing that populates or reads this table from the application layer should be regarded as internal and accessed only through standard Oracle Applications reconciliation programs.