Search Results gl_je_sources_v

Overview

GL_JE_SOURCES_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents journal entry source definitions maintained in the General Ledger application. Journal sources classify the origin of every journal entry posted in Oracle EBS, such as Payables, Receivables, Inventory, Payroll, or manual entry. The view exposes both the internal source identifier and the user-facing display name, making it a primary reference for reporting, validation, and integration logic that must translate a stored source code into a readable label.

The view is registered as VALID in the ETRM metadata and carries the object type VIEW under the GL - General Ledger product. Because it is a simple projection over the underlying source table rather than a complex join, it preserves the natural key structure of the source definition and supports direct querying without performance overhead typically associated with multi-table views. It is commonly consumed by concurrent programs, BI Publisher reports, Oracle Reports, Oracle Forms LOVs, and custom PL/SQL validation routines that resolve a journal source to its descriptive name. The column specifically surfaced to end users, USER_JE_SOURCE_NAME, is the attribute most frequently searched for by developers and functional analysts, since it supplies the translated, display-ready name shown on EBS forms and reports.

Underlying Base Objects

According to the documented view text, GL_JE_SOURCES_V is defined as a SELECT from GL_JE_SOURCES, referenced through a synonym in the APPS schema. Every column in the view maps one-to-one to a column in that base table, with the exception of the ROWID, which is aliased as ROW_ID for use as a surrogate row identifier. No joins, unions, or filter predicates are applied, so the view returns rows exactly as they exist in GL_JE_SOURCES.

The inclusion of ROW_ID derived from the physical ROWID is significant for EBS tooling. Oracle Forms and certain report definitions require a unique row identifier for block-based data handling, and exposing ROWID under the name ROW_ID satisfies that requirement. Because the view is read-only in practical terms, transactions against journal sources must be performed against GL_JE_SOURCES or through the standard General Ledger setup forms. The synonym APPS.GL_JE_SOURCES points to the base table, and the view itself is compiled in the APPS schema, so calling applications resolve it as APPS.GL_JE_SOURCES_V.

Key Columns

• ROW_ID — The physical ROWID of the corresponding row in GL_JE_SOURCES, exposed for unique row identification.
• JE_SOURCE_NAME — The internal, untranslated name of the journal source; the primary key value used throughout the GL data model.
• USER_JE_SOURCE_NAME — The user-facing name displayed in forms, reports, and lists of values; the column most commonly searched for by users.
• DESCRIPTION — Free-text description describing the purpose of the journal source.
• OVERRIDE_EDITS_FLAG — Indicates whether journal entry edit checks may be overridden for this source.
• JOURNAL_REFERENCE_FLAG — Controls whether a journal reference is required for entries from this source.
• JOURNAL_APPROVAL_FLAG — Indicates whether journals from this source require approval.
• EFFECTIVE_DATE_RULE_CODE — Defines the accounting date rule applied to journals originating from this source.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit and WHO columns.
• ATTRIBUTE1 through ATTRIBUTE5, CONTEXT — Descriptive flexfield segments and the context value supporting the source setup.

Common Use Cases and Queries

The view supports several recurring development patterns. It is used to populate value lists for journal source selection, to translate stored source names into display names in custom reports, and to audit source configuration flags such as approval and reference requirements. A typical query resolving the display name for a known source is:

SELECT je_source_name, user_je_source_name
FROM apps.gl_je_sources_v
WHERE je_source_name = 'Payables';

To list all sources requiring journal approval, a developer might run:

SELECT je_source_name, user_je_source_name, description
FROM apps.gl_je_sources_v
WHERE journal_approval_flag = 'Y';

A search-by-display-name lookup, reflecting the common "user_je_source_name" query pattern, uses:

SELECT je_source_name
FROM apps.gl_je_sources_v
WHERE user_je_source_name LIKE '%Manual%';

Because the view is a direct projection with no filters, results are deterministic and reflect current source setup. Integration and interface programs frequently join it to GL_JE_HEADERS or GL_JE_LINES on je_source_name to annotate journal data with the user-facing source label.