Results for “reference_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_JE_HEADERS_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module, valid in both 12.1.1 and 12.2.2. It exposes journal entry header information stored in the GL_JE_HEADERS base table, joined to GL_JE_BATCHES to surface the chart of accounts and accounting period attributes that reside at the batch level rather than at the header level. Because journal header data is central to subledger transfer, posting, reconciliation, and reporting, this view is widely referenced by concurrent programs, Oracle Reports, Oracle Forms LOVs, and custom integration code.

The view is not a substitute for the base table in transactional logic; it is a reporting and querying convenience layer. It denormalizes key batch attributes (chart of accounts identifier, period set name, and accounted period type) onto the header row, so a query can evaluate balancing and posting questions without an explicit join to GL_JE_BATCHES.

Underlying Base Objects

Per the ETRM metadata, GL_JE_HEADERS_V is defined over two referenced base objects, both exposed to APPS through synonyms: GL_JE_BATCHES and GL_JE_HEADERS. The view text confirms this relationship. The SELECT list draws H.* columns from GL_JE_HEADERS (aliased H) and B.* columns from GL_JE_BATCHES (aliased B). The batch-derived columns are B.CHART_OF_ACCOUNTS_ID, B.PERIOD_SET_NAME, and B.ACCOUNTED_PERIOD_TYPE; all remaining columns, including the searched BALANCED_JE_FLAG, originate from GL_JE_HEADERS.

The view also exposes H.ROWID as ROW_ID, providing a stable row identifier for the header record, and it applies TRUNC() to DATE_CREATED and POSTED_DATE so date-only comparisons behave predictably in reports.

Key Columns

• BALANCED_JE_FLAG — Indicates whether the journal entry header is balanced (debits equal credits). This is the column referenced in the user's search and is the primary flag for detecting out-of-balance entries prior to posting.
• JE_HEADER_ID / JE_BATCH_ID — Primary key of the header and the foreign key to its owning batch. Together they define the batch–header hierarchy.
• STATUS — Journal status (for example, Unposted, Posted, or Error) used to filter entries by posting state.
• LEDGER_ID, PERIOD_NAME, CURRENCY_CODE — Ledger, accounting period, and entered currency of the entry. These are the standard filtering dimensions for GL reporting.
• CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR — Entered-currency control and running debit/credit totals used to verify balance at the header level.
• RUNNING_TOTAL_ACCOUNTED_DR / RUNNING_TOTAL_ACCOUNTED_CR — Accounted-currency equivalents of the running totals.
• ACTUAL_FLAG, JE_SOURCE, JE_CATEGORY — Distinguish actual versus budget/encumbrance entries and classify the journal by source and category.
• BALANCING_SEGMENT_VALUE, MULTI_BAL_SEG_FLAG, ORIGINATING_BAL_SEG_VALUE — Support intercompany and balancing-segment processing.
• ACCRUAL_REV_FLAG, ACCRUAL_REV_PERIOD_NAME, ACCRUAL_REV_STATUS — Govern accrual reversal behavior and status.
• EXTERNAL_REFERENCE, DOC_SEQUENCE_VALUE, UNIQUE_DATE, POSTED_DATE — Audit, document sequencing, and posting-date tracking attributes.

Common Use Cases and Queries

The most frequent use of this view is identifying journal entries that are not balanced, auditing posted versus unposted entries, and feeding GL reconciliation extracts. A representative query to locate unbalanced journals is:

SELECT je_header_id, name, je_batch_id, period_name,
       currency_code, control_total, status
  FROM apps.gl_je_headers_v
 WHERE balanced_je_flag = 'N'
   AND ledger_id = :p_ledger_id
   AND period_name = :p_period_name;

A second common pattern lists headers for a given batch with posting status:

SELECT je_header_id, name, je_source, je_category,
       balanced_je_flag, status
  FROM apps.gl_je_headers_v
 WHERE je_batch_id = :p_batch_id
 ORDER BY je_header_id;

Because the view already supplies CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, and ACCOUNTED_PERIOD_TYPE from the batch, these columns can be compared directly to ledger and period-set definitions without joining GL_JE_BATCHES. When batch-level attributes beyond those three are required (for example, batch name or batch status), an explicit join back to GL_JE_BATCHES on JE_BATCH_ID is still necessary, since the view exposes only the selected batch columns.