Results for “journal_entry”

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

Overview

GLBV_JOURNAL_LINES is a read-only General Ledger view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents journal entry line detail in a denormalized, presentation-oriented form by joining GL_JE_LINES to GL_JE_HEADERS. The purpose of the view is to expose journal line attributes together with the parent journal entry name, allowing report writers, integrators, and functional analysts to query journal activity without performing the join themselves.

The view is defined with a WITH READ ONLY clause, so it can be queried but never updated, inserted, or deleted. Its definition also embeds a mandatory security predicate that references the ledger identifier and the code combination identifier. This reflects the standard Oracle EBS data-access model, in which General Ledger data is filtered by ledger and accounting flexfield security rules at runtime. For the user searching on journal_line_number, this view is the most direct reporting object, because it exposes the line sequence through the JOURNAL_LINE_NUMBER column.

Underlying Base Objects

The view is defined over two documented base tables:

• GL_JE_LINES — aliased as JOURNAL_LINE, the primary source of line-level data including amounts, periods, dates, and reference columns.
• GL_JE_HEADERS — aliased as JOURNAL_ENTRY, the source of header-level attributes. Only the header name is projected into the view.

The two tables are joined on JE_HEADER_ID (JOURNAL_LINE.JE_HEADER_ID = JOURNAL_ENTRY.JE_HEADER_ID), a one-to-many relationship from headers to lines. Because no outer join is used, only journal lines with a matching header are returned; orphaned lines are excluded. The embedded security predicate references JOURNAL_LINE.LEDGER_ID and JOURNAL_LINE.CODE_COMBINATION_ID, which are the two dimensions normally governed by ledger and cross-validation or flexfield security rules in General Ledger.

Key Columns

• JOURNAL_ENTRY_ID — the JE_HEADER_ID of the parent journal entry, the join key back to GL_JE_HEADERS.
• JOURNAL_ENTRY_NAME — the journal entry name (from GL_JE_HEADERS.NAME); the source of the journal's identifying label in reports.
• JOURNAL_LINE_NUMBER — the JE_LINE_NUM, the line sequence number within a journal entry. This is the column of interest for the search "journal_line_number".
• LEDGER_ID — the ledger to which the journal belongs; subject to ledger security.
• ACCOUNT_ID — the CODE_COMBINATION_ID of the accounting flexfield combination; subject to flexfield security.
• PERIOD_NAME and EFFECTIVE_DATE — the accounting period and effective date of the line.
• ENTERED_DR / ENTERED_CR — entered debit and credit amounts in the entered currency.
• CONVERTED_DR / CONVERTED_CR — accounted debit and credit amounts in the ledger currency.
• DESCRIPTION and STAT_AMOUNT — line description and statistical amount.
• SUBLEDGER_DOCUMENT_NUMBER — the subledger document sequence value of the originating transaction.
• REFERENCE_1 through REFERENCE_10 — open reference columns carrying subledger and user-defined context.

Common Use Cases and Queries

Typical uses include journal line extracts for reconciliation, subledger-to-GL tie-outs, and ad hoc reporting by journal entry name or line number. A representative query retrieving line detail for a given journal entry:

• SELECT JOURNAL_ENTRY_ID, JOURNAL_ENTRY_NAME, JOURNAL_LINE_NUMBER, ACCOUNT_ID, PERIOD_NAME, ENTERED_DR, ENTERED_CR FROM APPS.GLBV_JOURNAL_LINES WHERE JOURNAL_ENTRY_NAME = :je_name ORDER BY JOURNAL_LINE_NUMBER;
• SELECT JOURNAL_ENTRY_NAME, JOURNAL_LINE_NUMBER, REFERENCE_1, SUBLEDGER_DOCUMENT_NUMBER FROM APPS.GLBV_JOURNAL_LINES WHERE LEDGER_ID = :ledger_id AND PERIOD_NAME = :period;
• SELECT COUNT(*), SUM(NVL(ENTERED_DR,0) - NVL(ENTERED_CR,0)) FROM APPS.GLBV_JOURNAL_LINES WHERE JOURNAL_ENTRY_ID = :header_id;

Because the read-only security predicate is applied inside the view, any query returns only rows the requesting user is authorized to see, based on ledger and accounting flexfield access. This makes the view a safe foundation for custom reports and integration extracts in both 12.1.1 and 12.2.2.