Results for “gl_all_je_source_name_view”

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

Overview

The GL_ALL_JE_SOURCE_NAME_VIEW is a documented Oracle E-Business Suite view owned by the APPS schema and classified under the General Ledger (GL) product module. Its functional purpose is to present a consolidated list of journal entry sources, allowing users and concurrent programs to review all journal entry sources available in the ledger environment. Journal entry sources are the coded identifiers that describe how a particular journal entry originated within EBS, such as Payables, Receivables, Purchasing, Inventory, or manual entry. The view provides both a technical source name and a user-facing description for each source.

This object is exposed for reporting and integration rather than transactional data entry. Because it is flagged as VALID in the ETRM metadata, it can be safely referenced by custom reports, Discoverer workbooks, BI Publisher data templates, and external integration routines that need to enumerate valid journal entry sources without querying the base source table directly. The design intentionally includes a synthetic "ALL" entry so that downstream consumers can offer an option meaning "all sources" alongside individual enumerated sources.

Underlying Base Objects

The view is defined as a UNION of two queries. The first branch selects from GL_JE_SOURCES, which in the APPS schema is exposed as a SYNONYM per the documented metadata. GL_JE_SOURCES is the fundamental General Ledger table that stores the set of journal entry sources, including the JE_SOURCE_NAME and USER_JE_SOURCE_NAME attributes. The second branch selects from GL_LOOKUPS, documented as a VIEW, filtered to the lookup type 'LITERAL' where LOOKUP_CODE equals 'ALL'. This second branch contributes a single synthetic row that supplies a generic "ALL" source with its associated meaning, effectively broadening the result set beyond the physical rows stored in GL_JE_SOURCES.

The structure therefore relates to two layers: the persistent source definitions held in GL_JE_SOURCES, and the flexfield/lookup framework represented by GL_LOOKUPS. Because both referenced objects are already abstracted (a synonym and a view), the GL_ALL_JE_SOURCE_NAME_VIEW adds no new persistent storage; it is a pure read-only projection.

Key Columns

• JE_SOURCE_NAME — The coded, technical identifier of the journal entry source. For rows from GL_JE_SOURCES this is the source name key; for the lookup branch it resolves to the lookup code 'ALL'.
• DESCRIPTION — The descriptive, user-facing label. In the GL_JE_SOURCES branch this maps to USER_JE_SOURCE_NAME, while in the lookup branch it maps to the MEANING column, producing a readable label for the "ALL" entry.

Both columns are aliased from their underlying counterparts, so consumers see a uniform two-column interface regardless of which branch produced each row.

Common Use Cases and Queries

Typical usage includes populating parameter lists of concurrent programs and value sets that must offer a complete list of journal sources, validating imported journal data against recognized sources, and generating reference reports for auditors and functional analysts. The inclusion of the 'ALL' lookup row supports reconciliation and "select all" style reporting semantics.

A straightforward listing of every available source is:

• SELECT JE_SOURCE_NAME, DESCRIPTION FROM APPS.GL_ALL_JE_SOURCE_NAME_VIEW ORDER BY JE_SOURCE_NAME;

To locate a specific source by its friendly description:

• SELECT JE_SOURCE_NAME FROM APPS.GL_ALL_JE_SOURCE_NAME_VIEW WHERE DESCRIPTION = :p_description;

To drive a value set or LOV, developers query only JE_SOURCE_NAME and DESCRIPTION, relying on the view to merge physical sources with the synthetic ALL entry. Because the object is read-only and validated, it is a dependable foundation for GL reporting and integration.