Search Results glbv_journal_entries




Overview
Explore in AI Chat

Overview

GLBV_JOURNAL_ENTRIES is a General Ledger (GL) security-enabled view in Oracle E-Business Suite that presents journal entry header information filtered through the user's access set and ledger privileges. The "BV" designation typically indicates a "Business View" or secured view variant used in Oracle EBS reporting and integration contexts, where row-level data access is enforced by the GL Security package. In release 12.1.1 and 12.2.2, this view serves as a critical integration point for tools such as Oracle Business Intelligence Applications (OBIA), Enterprise Performance Management (EPM) integrations, and custom reporting solutions that must respect GL access set security.

The view is central to scenarios where journal entries must be presented to users or processes with enforced ledger and balancing segment value (BSV) / management segment value (MSV) security. It exposes journal header details alongside resolved lookup meanings for attributes such as actual flag, tax status, reversal status, and reversal option.

Underlying Base Objects

The ETRM documentation for this object lists no explicitly documented base objects, but the view text reveals that it is defined over the following GL tables:

The WHERE clause ties the journal entry's ledger to the login user's access set, and permits rows when the access set security segment code is 'F' (full access), the ledger access privilege code is 'F', or an explicit BSV/MSV assignment exists for the journal.

Key Columns

Common Use Cases and Queries

The most frequent use cases involve secured reporting of journal entries by source, category, or period, and integration extracts that must not expose data outside the user's access set. A typical query filtering by journal source might be:

  • SELECT je_header_id, name, user_je_source_name, period_name, control_total FROM glbv_journal_entries WHERE user_je_source_name = 'Payables';
  • SELECT user_je_source_name, COUNT(*), SUM(control_total) FROM glbv_journal_entries WHERE period_name = 'JAN-22' GROUP BY user_je_source_name;
  • SELECT je_header_id, name, currency_code, running_total_accounted_dr, running_total_accounted_cr FROM glbv_journal_entries WHERE actual_flag = 'A' AND status IS NOT NULL;

Because the view embeds GL_SECURITY_PKG.LOGIN_ACCESS_ID, results automatically reflect the connecting user's data access privileges, making it unsuitable for cross-ledger administrative extracts unless a privileged access set is used.