Search Results gl_je_sources_vl




Overview
Explore in AI Chat

Overview

GL_JE_SOURCES_VL is a seeded, read-only multilingual (ML) view owned by the APPS schema in Oracle E-Business Suite General Ledger. It exposes the translated journal entry source definitions maintained in the Journal Sources setup, which designate the operational origin of every journal entry processed by the application (for example, Payables, Receivables, Purchasing, or user-defined manual sources). The "_VL" suffix identifies this object as a language-specific view: it filters its underlying translation table to the language of the current runtime session, returning the descriptive name and description in the user's language while retaining the language-independent attributes of each source.

In both Release 12.1.1 and 12.2.2 the object is documented in ETRM with owner APPS, object type VIEW, and status VALID. It is not a transactional or reporting fact object; rather it is a setup/reference view that supplies decode values for journal source columns throughout General Ledger and the subledger accounting architecture. Reporting utilities, concurrent programs, and interface clients join to it whenever a journal source code must be presented as a meaningful, translated name rather than the internal key. Its role in integration is equally important, since interface tables such as GL_INTERFACE carry a JE_SOURCE_NAME that must resolve to a valid, enabled source maintained through this view's underlying table.

Underlying Base Objects

The view is defined over a single documented base object, GL_JE_SOURCES_TL, referenced through a synonym. GL_JE_SOURCES_TL is the translation (TL) table of the Journal Sources entity. It stores one row per source per installed language, carrying the translated JE_SOURCE_NAME, USER_JE_SOURCE_NAME, and DESCRIPTION alongside the language-independent flags and attributes inherited from the base table.

The view definition confirms this relationship explicitly: the SELECT projects from GL_JE_SOURCES_TL with the predicate WHERE LANGUAGE = USERENV('LANG'). This restriction is what makes the object a "_VL" view, guaranteeing that a session sees only the row matching its language environment. In practice GL_JE_SOURCES_TL is seeded for every installed language, so the view behaves transparently across NLS configurations. Because the view is read-only and exposes no DML path, source maintenance must be performed through the Journal Sources setup form, which writes to the base and translation tables.

Key Columns

  • ROW_ID – The ROWID of the underlying translation row, exposed as a unique identifier.
  • JE_SOURCE_NAME – The internal (untranslated) journal source identifier, used as the code value in joins and interface processing.
  • USER_JE_SOURCE_NAME – The user-defined display name for the source, the value typically shown in reports and lists of values.
  • JE_SOURCE_KEY – The import key used when journal entries are loaded through the Journal Import interface.
  • LANGUAGE, SOURCE_LANG – The language of the retrieved row and the source language of the record.
  • OVERRIDE_EDITS_FLAG – Indicates whether Journal Import may post entries from this source despite edit failures.
  • JOURNAL_REFERENCE_FLAG – Controls whether a reference number is required for journals from the source.
  • JOURNAL_APPROVAL_FLAG – Indicates whether journals from the source require approval.
  • IMPORT_USING_KEY_FLAG – Determines whether import resolves the source by key rather than name.
  • EFFECTIVE_DATE_RULE_CODE – The rule governing effective date derivation for imported journals.
  • DESCRIPTION, ATTRIBUTE1–ATTRIBUTE5, CONTEXT – Descriptive text and the standard descriptive flexfield columns.
  • Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is most frequently joined to GL_JE_HEADERS and GL_JE_BATCHES to label journal activity by source, or used to validate and decode source codes in reconciliation and audit reports. It also serves as the reference for users authoring Journal Import data, since the JE_SOURCE_KEY and user name must match a defined source. A typical query listing active sources in the session language is:

SELECT je_source_name, user_je_source_name, journal_approval_flag, override_edits_flag FROM gl_je_sources_vl ORDER BY user_je_source_name;

Joining to headers produces source-level journal analysis:

SELECT h.je_source, s.user_je_source_name, COUNT(*) journals FROM gl_je_headers h, gl_je_sources_vl s WHERE h.je_source = s.je_source_name GROUP BY h.je_source, s.user_je_source_name;

Because the view is filtered by USERENV('LANG'), it should be queried directly rather than emulated; querying GL_JE_SOURCES_TL without the language predicate would return duplicate rows and inflate aggregate results.