Search Results igs_co_itm_all




Overview
Explore in AI Chat

Overview

The IGS_CO_ITM_ALL table is a core data object within the now-obsolete Oracle Student System (IGS) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. As indicated by its description, it serves as the master repository for describing correspondence items sent to students. This table is designed to store a comprehensive record of all formal communications, such as letters, emails, or notifications, issued by the institution. Its "ALL" suffix signifies that it is a multi-organization table, capable of storing data partitioned by operating unit, which is a standard architectural pattern in EBS for supporting complex enterprise structures. The metadata explicitly states this table is "Not implemented in this database," which typically indicates it was part of a product footprint that was not installed or enabled in the specific referenced instance.

Key Information Stored

The table's structure is designed to link a correspondence item to key entities within the student lifecycle. Based on the primary and foreign key definitions, the critical columns include a composite primary key consisting of CORRESPONDENCE_TYPE and REFERENCE_NUMBER, which uniquely identifies each correspondence record. Essential foreign key columns establish relationships to other master tables, thereby storing contextual data such as: the academic calendar instance (CAL_TYPE, CI_SEQUENCE_NUMBER); the type of correspondence (CORRESPONDENCE_TYPE); the student's course and version (COURSE_CD, CV_VERSION_NUMBER); specific units (UNIT_CD, UV_VERSION_NUMBER); and the originator of the correspondence (ORIGINATOR_PERSON_ID linked to HZ_PARTIES). This design ensures each correspondence item is precisely associated with the relevant student, program, academic period, and administrative contact.

Common Use Cases and Queries

In a functional Student System, this table would be central to tracking and auditing all student communications. Common operational and reporting use cases would include generating histories of correspondence sent to a specific student, auditing communications related to a particular course or academic period, and verifying the issuance of official documents. A typical query might join to person and course tables to produce a student correspondence log. For example:
SELECT c.refERENCE_NUMBER, c.correspondence_type, hz.party_name, c.creation_date
FROM igs_co_itm_all c, hz_parties hz
WHERE c.originator_person_id = hz.party_id
AND c.course_cd = :p_course_code;
However, given the module's obsolete status and the "not implemented" note, direct operational use in active EBS instances is unlikely. Its primary relevance is for historical data analysis, custom data migration projects, or supporting legacy integrations that may still reference this schema.

Related Objects

The foreign key constraints detailed in the metadata clearly define this table's relationships within the obsolete IGS schema. Key related objects include:

  • IGS_CO_TYPE: The master table for valid correspondence types.
  • IGS_CA_INST_ALL: The academic calendar instance to which the correspondence is tied.
  • IGS_PS_VER_ALL and IGS_PS_UNIT_VER_ALL: The course and unit version master tables, linking correspondence to a specific program of study.
  • HZ_PARTIES: The Trading Community Architecture (TCA) table storing information about the person (staff) who originated the correspondence.
  • IGS_CO_OU_CO_ALL: A related correspondence table that holds a foreign key reference back to IGS_CO_ITM_ALL.
These relationships underscore the table's role as a central hub connecting communications to the core entities of the student information system.