Search Results journal_entry1

Overview

The GLFV_BUDGET_JOURNAL_ENTRIES view belongs to the Oracle General Ledger (GL) module of Oracle E-Business Suite, version 12.1.1 / 12.2.2. It exposes journal entry header information restricted to budget-related journals by joining GL_JE_HEADERS to GL_BUDGET_VERSIONS. The view is a "flexfield" (FV) style reporting object, meaning it flattens descriptive identifiers — ledger names, category names, source names, and budget version names — onto a single row so that downstream reports, OBIEE extracts, Discoverer worksheets, and custom SQL do not have to repeat lookup joins.

The view is documented as Not implemented in this database, meaning it is delivered as a database object but not seeded with data of its own; its rows are derived entirely at query time. Its practical role is to provide a consolidated, security-aware read layer over budget journal headers, including the EXTERNAL_REFERENCE column that users search on to reconcile budget entries against legacy or third-party systems.

Underlying Base Objects

The ETRM metadata documents no persistent base tables separate from the SQL text. The view is defined over the following GL objects:

• GL_JE_HEADERS JOURNAL_ENTRY1 — the driving table supplying journal header attributes.
• GL_JE_HEADERS JOURNAL_ENTRY3 — self-join used to resolve the NAME of the reversed journal entry via REVERSED_JE_HEADER_ID.
• GL_LEDGERS LEDGER — supplies the ledger name for LEDGER_ID.
• GL_BUDGET_VERSIONS GL_BUDGET_VERSION — filters/links budget journals via BUDGET_VERSION_ID and provides BUDGET_NAME.
• GL_JE_BATCHES JOURNAL_BATCH — batch name for JE_BATCH_ID.
• GL_JE_CATEGORIES and GL_JE_SOURCES — user-defined category and source names.
• GL_ACCESS_SETS, GL_ACCESS_SET_LEDGERS, and (in the EXISTS clause) GL_JE_SEGMENT_VALUES plus GL_ACCESS_SET_ASSIGNMENTS — enforce data access set security.

The WHERE clause ties rows to the caller's login access set through GL_SECURITY_PKG.LOGIN_ACCESS_ID, and permits a row only when the access set is at full ledger level (SECURITY_SEGMENT_CODE = 'F' or ACCESS_PRIVILEGE_CODE = 'F') or when a matching segment value assignment exists.

Key Columns

• JE_HEADER_ID, NAME, JE_BATCH_ID — journal identity and batch linkage.
• LEDGER_ID, LEDGER.NAME — owning ledger and its descriptive name.
• BUDGET_VERSION_ID, BUDGET_NAME — the budget version the entry belongs to; critical for distinguishing budget journals from actuals.
• PERIOD_NAME, CURRENCY_CODE, DEFAULT_EFFECTIVE_DATE, REFERENCE_DATE — accounting period, currency, and date context.
• USER_JE_CATEGORY_NAME, USER_JE_SOURCE_NAME — user-facing category and source.
• EXTERNAL_REFERENCE — the free-text key used to cross-reference the budget journal to an external or legacy system; this is the column most often searched by users.
• DESCRIPTION, CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR — narrative and control/balance amounts.
• ACCRUAL_REV_* and the two lookups — accrual reversal status and reversal option, rendered through GL_LOOKUPS.
• DOC_SEQUENCE_VALUE, POSTING_ACCT_SEQ_VALUE, CLOSE_ACCT_SEQ_VALUE — document sequencing values.
• REVERSED_JE_HEADER_ID and the joined JOURNAL_ENTRY3.NAME — identifies the entry this journal reverses.

Common Use Cases and Queries

The most frequent scenario is tracing a budget journal by its external reference. A typical query is:

• SELECT je_header_id, name, ledger_id, budget_name, period_name, external_reference, control_total FROM glfv_budget_journal_entries WHERE external_reference = 'PO-2024-00417';
• Reconciling budget journals to a feeder system by listing all entries for a source and period: filter on USER_JE_SOURCE_NAME and PERIOD_NAME.
• Auditing budget-to-actual comparisons by joining this view to GL_BALANCES on LEDGER_ID, PERIOD_NAME, and CURRENCY_CODE.
• Detecting reversal activity via REVERSED_JE_HEADER_ID and the accrual reversal lookup columns.

Because access set security is embedded in the view, results automatically respect the responsibility's data access set, which makes it safe for end-user reporting without additional security predicates.