Search Results job_request_id




Overview
Explore in AI Chat

Overview

The APPS.IGS_CO_ITM view is a critical data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Global Systems (IGS) Correspondence module. It serves as a security-filtered presentation layer built on the underlying table IGS_CO_ITM_ALL. Its primary role is to provide a multi-organization (Multi-Org) aware interface to correspondence item data, ensuring users and concurrent programs only access records pertinent to their operating unit. This is enforced by the WHERE clause predicate on the ORG_ID column, which filters data based on the user's session client information. The view centralizes key transactional and process control information related to correspondence generation and job execution.

Key Information Stored

The view consolidates columns that describe the correspondence item, its context, and its processing lifecycle. Key columns include:

Common Use Cases and Queries

This view is essential for troubleshooting, auditing, and reporting on correspondence generation processes. A primary use case is investigating the status and details of correspondence produced by a specific concurrent request, which is directly supported by the user's search for "job_request_id". For example, to find all correspondence items generated by a particular job request, one would query: SELECT * FROM apps.igs_co_itm WHERE job_request_id = :req_id;. Another common scenario is generating a report of correspondence for a specific academic course or unit within an operating unit, joining on the contextual academic keys. The view is also frequently queried to monitor correspondence output by joining with FND_CONCURRENT_REQUESTS on REQUEST_ID or JOB_REQUEST_ID for enhanced job status details.

Related Objects

The APPS.IGS_CO_ITM view has a direct and singular relationship with its base table. The view's source is a SELECT statement from IGS_CO_ITM_ALL, with a security predicate applied. All columns in the view map directly to columns in this underlying table. While the provided metadata does not list explicit foreign key relationships from other objects to this view, the presence of keys like JOB_REQUEST_ID, REQUEST_ID, and academic identifiers (CAL_TYPE, COURSE_CD, etc.) strongly implies logical relationships. In practice, this view is referenced by custom reports, interfaces, and potentially by other IGS module components to query correspondence data within a secure Multi-Org context. The JOB_REQUEST_ID column specifically creates a functional link to the FND_CONCURRENT_REQUESTS table, which stores the master record for the concurrent job.