Search Results gl_je_lines




Overview
Explore in AI Chat

Overview

GL_JE_LINES is the core line-level detail table of the Oracle General Ledger journal entry model. Owned by the GL schema and valid in both Oracle E-Business Suite 12.1.1 and 12.2.2, it stores the individual debit and credit distribution lines that make up every journal entry created, imported, or generated in the ledger. Each row represents a single line, carrying the entered amounts, the accounted amounts, the accounting flexfield combination, and the reference and tax information associated with that distribution. The table is one of the most heavily accessed objects in the EBS financials footprint, both by concurrent programs that validate and post journals and by the reporting and reconciliation processes that extract balances and subledger detail.

The heuristic Data Vault classification for this object is hub-leaning. This reflects that GL_JE_LINES behaves primarily as a hub-style entity anchored to stable business keys rather than as a mutable descriptive satellite. Its composite primary key, GL_JE_LINES_PK on (JE_HEADER_ID, JE_LINE_NUM), and the unique index GL_JE_LINES_U1 on the same pair, confirm that the journal line identity is stable and declaratively enforced.

Key Information Stored

The documented physical schema lists 94 columns. The most significant are the following:

  • JE_HEADER_ID — The parent journal entry identifier. Together with the line number it forms the primary key and links back to GL_JE_HEADERS.
  • JE_LINE_NUM — The sequential line number within the journal entry; part of the composite primary key.
  • LEDGER_ID — The ledger to which the line belongs, referencing GL_LEDGERS.
  • CODE_COMBINATION_ID — The accounting flexfield combination that identifies the distribution account, referencing GL_CODE_COMBINATIONS.
  • PERIOD_NAME — The accounting period in which the line is recorded.
  • EFFECTIVE_DATE — The accounting date used for period and rate determination.
  • STATUS — The line status (for example, unposted or posted), driving posting eligibility.
  • ENTERED_DR / ENTERED_CR — The debit and credit amounts in the entered currency.
  • ACCOUNTED_DR / ACCOUNTED_CR — The debit and credit amounts in the ledger (accounted) currency.
  • DESCRIPTION — Free-text explanation carried on the line.
  • LINE_TYPE_CODE — The journal line type classification.
  • REFERENCE_1 through REFERENCE_10 — User-definable reference fields used for reconciliation and subledger tracing.
  • GL_SL_LINK_ID / GL_SL_LINK_TABLE — The link back to the originating subledger transaction.
  • ATTRIBUTE1 through ATTRIBUTE20 — Descriptive flexfield attribute columns.
  • TAX_CODE, TAX_TYPE_CODE, TAXABLE_LINE_FLAG, AMOUNT_INCLUDES_TAX_FLAG — Tax-related attributes supporting tax journal processing.

The surrogate identity is the composite (JE_HEADER_ID, JE_LINE_NUM); the unique index GL_JE_LINES_U1 on the same columns is the business-key candidate. The foreign keys to GL_JE_HEADERS, GL_LEDGERS, and GL_CODE_COMBINATIONS define the natural dimensional context of each line.

Common Use Cases and Queries

Typical usage centers on extracting journal detail, validating posting balances, and reconciling subledger activity. A representative pattern joins the line to its header and ledger:

  • Reporting journal detail for a period: select from GL_JE_LINES where PERIOD_NAME equals the target period and STATUS indicates posted, joining GL_JE_HEADERS on JE_HEADER_ID.
  • Account activity analysis: group ACCOUNTED_DR and ACCOUNTED_CR by CODE_COMBINATION_ID and PERIOD_NAME to reproduce account balances at the line level.
  • Subledger reconciliation: filter by GL_SL_LINK_ID and GL_SL_LINK_TABLE to trace postings back to the originating subledger transaction.
  • Balance verification: compare summed ENTERED_DR against ENTERED_CR for each JE_HEADER_ID to confirm the entry balances before posting.

Related Objects

GL_JE_LINES sits at the center of a wide relationship graph. The most significant dependents and parents are: