Search Results request_job_run_id




Overview
Explore in AI Chat

Overview

The IGS_CO_ITM view is a critical data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically for versions 12.1.1 and 12.2.2. It provides a comprehensive, organization-secured view of all correspondence items sent to students. The view abstracts the underlying table IGS_CO_ITM_ALL, applying a Multi-Org Security (VPD) filter based on the ORG_ID context from the user session (USERENV('CLIENT_INFO')). This ensures users only see correspondence data relevant to their operating unit. The view's primary role is to serve as the standard, secure interface for querying registered correspondence, which can include both system-generated documents and manually registered items, forming a central audit trail of student communications.

Key Information Stored

The view consolidates key identifiers, descriptive data, and system audit columns for each correspondence item. Essential columns include CORRESPONDENCE_TYPE and REFERENCE_NUMBER, which classify and uniquely identify the correspondence. The view links correspondence to specific academic entities via columns like CAL_TYPE, CI_SEQUENCE_NUMBER (for academic periods), COURSE_CD, and UNIT_CD. A critical column for integration and tracking is REQUEST_NUM, which often holds the identifier from a concurrent request that generated the correspondence. Other significant columns include REQUEST_ID (the concurrent request ID), ORIGINATOR_PERSON_ID (who initiated it), S_JOB_NAME, and JOB_REQUEST_ID for process tracking, alongside standard WHO columns (CREATED_BY, CREATION_DATE) and the security key ORG_ID.

Common Use Cases and Queries

A primary use case is auditing and reporting on correspondence sent to a specific student or for a particular academic program. For instance, support staff often query by REQUEST_NUM to trace a specific document generated by a concurrent job. Common reporting needs include listing all system-generated correspondence for a course or identifying correspondence initiated by a specific person. Sample SQL patterns include:

  • Finding correspondence by a specific concurrent request number: SELECT * FROM apps.igs_co_itm WHERE request_num = '&request_number';
  • Listing correspondence for a student (via originator): SELECT correspondence_type, reference_number, create_dt, comments FROM apps.igs_co_itm WHERE originator_person_id = &person_id ORDER BY create_dt DESC;
  • Identifying correspondence related to a specific course and academic period: SELECT * FROM apps.igs_co_itm WHERE course_cd = '&course_code' AND cal_type = '&calendar_type' AND ci_sequence_number = &sequence_num;

Related Objects

The view's data is sourced directly from the underlying table IGS_CO_ITM_ALL. It is intrinsically related to the core correspondence functionality within the IGS module. The presence of REQUEST_ID and PROGRAM_ID columns indicates integration with the standard EBS Concurrent Processing framework (FND_CONCURRENT_REQUESTS). The ORIGINATOR_PERSON_ID column links to person data, typically in PER_ALL_PEOPLE_F or IGS_PE_PERSON. Given its academic context, the view is also logically related to tables defining the academic structures referenced, such as IGS_CA_INST (for CAL_TYPE, CI_SEQUENCE_NUMBER) and IGS_PS_COURSE. The view itself is a key reference point for custom reports and integrations needing a secure list of student correspondence.