Results for “request_id”

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

Overview

The APPS.GL_SRS_JI_REQUESTS_V view is a General Ledger reporting object that exposes the set of concurrent request identifiers associated with journal import processing, together with the journal source name applied to each request. It is a UNION-based view, meaning it consolidates two logically distinct populations of data into a single result set: journal import rows residing in the GL_INTERFACE table, and journal import control rows residing in GL_INTERFACE_CONTROL.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a supporting lookup for reports and forms that must identify which Journal Import run is associated with which source. Because the view is defined with DISTINCT and filters on REQUEST_ID IS NOT NULL, it returns a de-duplicated list of populated import requests. The name prefix "SRS" reflects the Oracle EBS concurrent program (Standard Request Submission) framework, while "JI" denotes Journal Import. The view does not itself import journals; it exposes metadata about import requests.

Underlying Base Objects

The view is defined in the APPS schema over three documented base objects, each referenced through a SYNONYM:

• GL_INTERFACE (SYNONYM) — the staging table that holds unposted journal lines awaiting Journal Import. The view reads its REQUEST_ID and USER_JE_SOURCE_NAME columns.
• GL_JE_SOURCES_TL (SYNONYM) — the translated journal source definitions. Aliased as SRC, it supplies JE_SOURCE_NAME and JE_SOURCE_KEY and is joined to GL_INTERFACE using a DECODE on IMPORT_USING_KEY_FLAG, with a LANGUAGE filter against USERENV('LANG').
• GL_INTERFACE_CONTROL (SYNONYM) — the control table governing Journal Import run behavior. The second UNION branch draws REQUEST_ID and JE_SOURCE_NAME from it, excluding rows where STATUS = 'S' and excluding rows whose INTERFACE_TABLE_NAME is null or resolves to GL_INTERFACE.

Key Columns

• REQUEST_ID — the concurrent request identifier for the Journal Import run. This is the primary correlation key linking the view to the concurrent request tables (e.g., FND_CONCURRENT_REQUESTS).
• SOURCE_NAME — the journal source name. For the GL_INTERFACE branch this is drawn from JE_SOURCE_NAME in the translated source table; for the GL_INTERFACE_CONTROL branch it is the JE_SOURCE_NAME stored directly on the control row.

Common Use Cases and Queries

A typical use case is identifying all pending or historical Journal Import requests, and confirming which source each was submitted against. Because the view isolates the control-table branch for non-GL_INTERFACE staging tables, it is also useful when import processes target alternate interface tables.

Sample query listing distinct requests and sources:

• SELECT request_id, source_name FROM apps.gl_srs_ji_requests_v ORDER BY request_id;
• SELECT request_id, source_name FROM apps.gl_srs_ji_requests_v WHERE source_name = 'Payables';
• SELECT r.request_id, r.source_name FROM apps.gl_srs_ji_requests_v r, fnd_concurrent_requests c WHERE r.request_id = c.request_id;

These queries allow subledger and GL analysts to trace imported journal batches back to the originating import request and source, and to reconcile GL_INTERFACE contents with the controlling import run.