Search Results igi_cbr_journal_sources

Overview

APPS.IGI_CBR_GL_JOURNAL_SOURCES_V is a lightweight union view owned by the APPS schema that exposes a consolidated, user-facing list of General Ledger journal sources. It presents two columns — USER_JE_SOURCE_NAME and JE_SOURCE_NAME — derived from two distinct underlying sources. The view is primarily used by the Oracle Grants/IGI Cash Basis Reporting (CBR) functionality, where a journal source must be selected or validated against both the standard General Ledger journal source list and an IGI-specific lookup set.

The object is relevant in Oracle EBS 12.1.1 and 12.2.2. Because it is defined as a simple UNION of translated GL source names and IGI lookup values, it functions as a read-only reporting and integration helper rather than a transactional entity. Developers and report authors searching for "user_je_source_name" typically reach this view when building LOVs, validation queries, or extracts that must include the CBR journal source lookup alongside native GL journal sources.

Underlying Base Objects

The documented base objects referenced by the view are:

• GL_JE_SOURCES_TL (SYNONYM) — the translated (language) table of General Ledger journal sources. This is the standard EBS table storing journal source names and descriptions by language.
• IGI_LOOKUPS (VIEW) — the IGI lookup view that surfaces lookup codes and descriptions for IGI-specific lookup types, including the type IGI_CBR_JOURNAL_SOURCES.

The view definition is:

SELECT USER_JE_SOURCE_NAME, JE_SOURCE_NAME FROM GL_JE_SOURCES_TL UNION SELECT DESCRIPTION USER_JE_SOURCE_NAME, LOOKUP_CODE JE_SOURCE_NAME FROM IGI_LOOKUPS WHERE LOOKUP_TYPE = 'IGI_CBR_JOURNAL_SOURCES'

Thus the first branch of the union reads user-facing and internal source names directly from the GL translated source table, while the second branch reads IGI CBR journal source lookup entries, mapping the lookup description into the USER_JE_SOURCE_NAME column and the lookup code into the JE_SOURCE_NAME column. The UNION implicitly removes duplicate rows.

Key Columns

• USER_JE_SOURCE_NAME — the display or user-facing name of the journal source. For GL entries this is the translated user source name; for IGI CBR entries this is populated from the lookup DESCRIPTION.
• JE_SOURCE_NAME — the internal journal source identifier or code. For GL entries this is the base JE_SOURCE_NAME; for IGI CBR entries this is the lookup CODE.

Because both branches align on these two columns, consumers can treat the result set as a single, uniform list of journal source names and codes, regardless of whether the row originates in GL or IGI lookups.

Common Use Cases and Queries

Typical scenarios include populating selection lists for CBR journal source parameters, validating a source name supplied by a user, and joining the view to reporting queries that need a combined GL and CBR source list.

Sample query returning all sources:

SELECT user_je_source_name, je_source_name FROM apps.igi_cbr_gl_journal_sources_v ORDER BY user_je_source_name;

Lookup by user-facing name:

SELECT je_source_name FROM apps.igi_cbr_gl_journal_sources_v WHERE user_je_source_name = :p_source;

Because the view incorporates the IGI_CBR_JOURNAL_SOURCES lookup type, it is the appropriate object when a report must honor CBR-specific source definitions in addition to standard GL sources. Note that, being a union view with no filters at the outer level, it returns the complete combined set; callers should apply their own WHERE and ORDER BY clauses.