Search Results journal_entry3

Overview

APPS.GLFV_BUDGET_JOURNAL_ENTRIES is a General Ledger consolidation and reporting view that exposes budget journal entry header information to Oracle E-Business Suite users. The "FV" designation identifies it as part of the GL Financials View family, a set of views that flatten and enrich the core GL journal tables with descriptive fields drawn from related lookup, category, source, batch, ledger, and budget-version tables. In Oracle EBS 12.1.1 and 12.2.2 it is most commonly used for reporting, reconciliation, and integration of budget journals, where the raw GL_JE_HEADERS structure is insufficient because it stores surrogate identifiers rather than user-meaningful names.

The view is constrained by Oracle's data-access-set security model. Its WHERE clause joins GL_ACCESS_SETS and GL_ACCESS_SET_LEDGERS to GL_SECURITY_PKG.login_access_id, ensuring that only journals belonging to ledgers and segments the current user is authorized to see are returned. This makes the view safe to expose directly in custom inquiries, BI Publisher reports, and outbound interfaces without additional row-level filtering.

Underlying Base Objects

The view is defined over eight documented base objects. The driving table is GL_JE_HEADERS, aliased JOURNAL_ENTRY1, which supplies the journal header identifier, name, ledger, period, currency, batch, running totals, reference data, and reversal attributes. A self-join to GL_JE_HEADERS, aliased JOURNAL_ENTRY3, resolves the name of the originating reversed journal when REVERSED_JE_HEADER_ID is populated.

The remaining objects provide descriptive context: GL_LEDGERS supplies the ledger name, GL_BUDGET_VERSIONS supplies the budget name associated with BUDGET_VERSION_ID, GL_JE_BATCHES supplies the batch name, GL_JE_CATEGORIES supplies the user-defined category name, and GL_JE_SOURCES supplies the user-defined source name. GL_ACCESS_SETS and GL_ACCESS_SET_LEDGERS implement the security restriction described above. Note that although the base tables are not individually documented in the ETRM entry, the view text clearly evidences these dependencies.

Key Columns

• JE_HEADER_ID — Primary key of the journal header; the driving identifier for joins back to GL_JE_HEADERS.
• NAME — System-generated journal name, typically the batch name concatenated with a sequence number.
• LEDGER_ID / LEDGER.NAME — The ledger surrogate key and its user-facing name.
• USER_JE_CATEGORY_NAME / USER_JE_SOURCE_NAME — Journal category and source names for reporting groupings.
• PERIOD_NAME, CURRENCY_CODE, DEFAULT_EFFECTIVE_DATE — Accounting period, currency, and effective date of the entry.
• BUDGET_VERSION_ID / BUDGET_NAME — Links the entry to its budget version definition.
• JE_BATCH_ID / JOURNAL_BATCH.NAME — Batch identifier and name for batch-level reconciliation.
• ACCRUAL_REV_EFFECTIVE_DATE, ACCRUAL_REV_PERIOD_NAME, ACCRUAL_REV_STATUS — Reversal scheduling attributes; the status is decoded through the JE_REVERSAL_STATUS lookup.
• REVERSED_JE_HEADER_ID — For reversal journals, the header identifier of the journal being reversed; paired with JOURNAL_ENTRY3.NAME, which returns the original journal's name. This is the column most frequently used to trace reversal relationships.
• DESCRIPTION, EXTERNAL_REFERENCE, REFERENCE_DATE — Free-form and external identifiers for the entry.
• CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR — Batch control total plus accumulated debit and credit amounts.
• DOC_SEQUENCE_VALUE, POSTING_ACCT_SEQ_VALUE, CLOSE_ACCT_SEQ_VALUE — Document sequence and accounting sequence values assigned during posting and closing.

Common Use Cases and Queries

A primary use case is identifying which journals are reversals and what they reverse. For example:

SELECT je_header_id, name, period_name, reversed_je_header_id FROM apps.glfv_budget_journal_entries WHERE reversed_je_header_id IS NOT NULL;

Analysts also use the view to list all budget journals posted to a ledger or period, aggregating control totals by budget version. The view supports drill-down from a reversal journal to its original entry via the self-join exposed as REVERSED_JE_HEADER_ID, and it is well suited to period-end reporting where category, source, and batch names are required rather than coded values.