Results for “gl_je_source_names_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_JE_SOURCE_NAMES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger. It exposes journal entry source definitions maintained in the GL_JE_SOURCES base table, presenting the source name, the user-facing source name, and the associated description. The object carries a VALID status in the ETRM repository and is identified with the notation "10SC ONLY," which indicates that the view is scoped to a specific localization or configuration context rather than being a general-purpose global object. In Oracle EBS 12.1.1 and 12.2.2, the view functions as a lightweight, denormalized access point for consumers that need journal source reference data without querying the underlying table directly. Its role in reporting and integration is primarily as a lookup view: it supplies the enumerated values used when populating journal entry source fields, driving list-of-values behavior, and supporting ad hoc reporting on General Ledger journal activity by source. Because it is defined only over the source definition table and not over the journal header or line tables, it does not contain transactional journal data; it provides the descriptive reference layer that joins to those tables.

Underlying Base Objects

The view is defined over a single base object, GL_JE_SOURCES, which is accessed through a synonym in the documented metadata. The view text is a direct projection from that table, aliased as JES:

• SELECT JES.USER_JE_SOURCE_NAME USER_JE_SOURCE_NAME, JES.JE_SOURCE_NAME JE_SOURCE_NAME, JES.DESCRIPTION DESCRIPTION FROM GL_JE_SOURCES JES

There is no join, filter, or aggregation in the definition. This means the view is a one-to-one pass-through of the source rows, with no transformation applied beyond column naming. Any change made to a row in GL_JE_SOURCES is immediately reflected in the view. Because GL_JE_SOURCES is an application reference table, the view inherits its seeded source values (for example, Payables, Receivables, Purchasing, Inventory, and Manual) along with any custom sources defined by the installation.

Key Columns

The view exposes three columns, all mapped directly from the base table:

• JE_SOURCE_NAME — The internal, system-recognized key for the journal source. This value is used in programmatic contexts and is stored on journal entry records to identify the originating subsystem or entry method.
• USER_JE_SOURCE_NAME — The user-facing display name for the source. This is the value typically shown in forms, list of values, and reports, and it may differ from the internal key to accommodate localization or naming conventions.
• DESCRIPTION — A free-text explanation of the source, used to document the purpose or origin of the journal entry source.

Common Use Cases and Queries

The view is most commonly used to resolve source names for reporting, to drive selection lists, and to reconcile journal activity by source. A typical query lists all defined sources:

• SELECT user_je_source_name, je_source_name, description FROM apps.gl_je_source_names_v ORDER BY user_je_source_name;

To join source descriptions to journal headers for reporting, the view is linked on the source name:

• SELECT h.je_header_id, v.user_je_source_name, h.name, h.period_name FROM apps.gl_je_headers h, apps.gl_je_source_names_v v WHERE h.je_source = v.je_source_name;

Because the view contains no journal amounts or lines, aggregation of balances by source requires joining to GL_JE_HEADERS and GL_JE_LINES. The view remains the authoritative reference for presenting the descriptive form of the source while the transactional tables retain the internal key.