Results for “je_source_name”

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

Overview

The GL_SRS_DEL_JI_GROUPS_V view is a General Ledger (GL) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated list of Journal Import groups that are eligible for review or deletion, resolving the interface group identifier, the concurrent request that loaded the data, the target ledger, and the journal source name in a single denormalized result set. The view is used primarily by the Journal Import maintenance and purge programs, and it supports diagnostic reporting by exposing the relationship between staging rows in GL_INTERFACE and their control records.

The view is particularly significant because it exposes the JE_SOURCE_NAME column, which is frequently referenced when users search for journal source information during Journal Import reconciliation. By resolving the source name from the interface staging data and the General Ledger source definition, the view allows source-level filtering of grouped interface data without requiring manual joins across multiple tables.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

• GL_INTERFACE — the Journal Import staging table holding unposted journal lines and their associated group, request, and source context.
• GL_INTERFACE_CONTROL — the control table that tracks each Journal Import group and its interface table name.
• GL_JE_SOURCES — the journal source definition table, providing the import key logic and the displayed journal source name.
• GL_LEDGERS — the ledger definition table, used to resolve the target ledger identifier.

The view text is a UNION of two branches. The first branch joins GL_INTERFACE to GL_JE_SOURCES and GL_LEDGERS, matching USER_JE_SOURCE_NAME against either JE_SOURCE_KEY or USER_JE_SOURCE_NAME depending on the IMPORT_USING_KEY_FLAG setting, and handling ledger resolution through both SET_OF_BOOKS_ID and LEDGER_ID. The second branch selects from GL_INTERFACE_CONTROL for groups whose INTERFACE_TABLE_NAME is not the default GL_INTERFACE. Both branches require GROUP_ID IS NOT NULL and aggregate by group, request, ledger, and journal source.

Key Columns

• GROUP_ID — the Journal Import group identifier that uniquely ties a set of interface rows to a single import run.
• REQUEST_ID — the concurrent request identifier of the program that created or processed the group, enabling traceability to the Concurrent Manager.
• LEDGER_ID — the ledger (or set of books) to which the grouped interface data applies.
• JE_SOURCE_NAME — the journal source name associated with the group, derived from GL_JE_SOURCES or from the interface control record. This column is the primary filter target for source-specific analysis.

Common Use Cases and Queries

Typical scenarios include identifying all unposted Journal Import groups for a given source, reviewing which concurrent request loaded a group, and determining the ledger context prior to purge. Example queries:

• SELECT group_id, request_id, ledger_id, je_source_name FROM gl_srs_del_ji_groups_v WHERE je_source_name = 'Payables';
• SELECT group_id, request_id, ledger_id FROM gl_srs_del_ji_groups_v WHERE ledger_id = :ledger_id;
• SELECT je_source_name, COUNT(*) FROM gl_srs_del_ji_groups_v GROUP BY je_source_name;

Because the view aggregates by group, request, ledger, and source, it is well suited to summary reporting and to supplying selection criteria for Journal Import deletion or review routines.