Results for “igi_cbr_gl_journal_sources_v”

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

Overview

The view APPS.IGI_CBR_GL_JOURNAL_SOURCES_V is a documented database object within the IGI – Public Sector Financials International product family in Oracle EBS 12.1.1 and 12.2.2. Its stated purpose is to retrieve the journal source name from GL_JE_SOURCES_TL and link it with the ALL option from IGI_LOOKUPS for the lookup type IGI_CBR_JOURNAL_SOURCES. The view presents a unified, two-column list of journal sources that can be used for reporting, validation, and value-set-style population of LOVs within the IGI budgeting and commitment control functionality.

The object is owned by the APPS schema and is documented as VALID, confirming that it compiles successfully against its referenced base objects in the supported releases. Because the view is a UNION query, it does not represent a single underlying entity but rather a de-duplicated combination of a translated GL source list and a lookup-driven extension list.

Underlying Base Objects

The documented base objects referenced by this view are:

• GL_JE_SOURCES_TL (referenced via SYNONYM) — the translated journal source table in General Ledger, which supplies the source name and the user-facing name.
• IGI_LOOKUPS (a VIEW) — the lookup definitions used by the IGI product, filtered here on LOOKUP_TYPE = 'IGI_CBR_JOURNAL_SOURCES'.

The view text combines these two sources with a UNION:

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'

The UNION (rather than UNION ALL) removes duplicate rows, so any source appearing in both GL_JE_SOURCES_TL and the IGI lookup is presented once. This design allows the IGI module to expose additional journal sources defined administratively through lookups alongside the standard GL definition.

Key Columns

The view exposes exactly two columns, both aliased in the UNION so the shape is consistent:

• USER_JE_SOURCE_NAME — the user-facing, descriptive source name. In the first branch this comes from GL_JE_SOURCES_TL.USER_JE_SOURCE_NAME; in the second branch it is drawn from IGI_LOOKUPS.DESCRIPTION.
• JE_SOURCE_NAME — the internal, language-independent source identifier. In the first branch this is GL_JE_SOURCES_TL.JE_SOURCE_NAME; in the second branch it is IGI_LOOKUPS.LOOKUP_CODE. This is the value typically stored on transactions and used in joins.

The pairing mirrors the standard GL pattern, where JE_SOURCE_NAME acts as the primary key and USER_JE_SOURCE_NAME provides the display value.

Common Use Cases and Queries

The view is most commonly used to populate source LOVs and to resolve a stored JE_SOURCE_NAME to its display name in IGI reports. A basic listing query is:

SELECT JE_SOURCE_NAME, USER_JE_SOURCE_NAME
FROM   APPS.IGI_CBR_GL_JOURNAL_SOURCES_V
ORDER BY USER_JE_SOURCE_NAME;

To resolve a specific source for reporting:

SELECT USER_JE_SOURCE_NAME
FROM   APPS.IGI_CBR_GL_JOURNAL_SOURCES_V
WHERE  JE_SOURCE_NAME = :source_name;

Because the documented description explicitly references the "ALL" option from IGI_LOOKUPS, the view is frequently used where a catch-all or user-extensible source value must be available in addition to standard GL sources. In integration and validation logic, the view can serve as the authoritative list against which an incoming JE_SOURCE_NAME is verified. Note that any query relying on the lookup branch is sensitive to the row content of IGI_LOOKUPS for lookup type IGI_CBR_JOURNAL_SOURCES; the GL branch depends on GL_JE_SOURCES_TL and therefore reflects only installed and translated GL sources.