Search Results igs_co_ou_co_pk

Overview

The IGS_CO_OU_CO_ALL table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS). It functions as a junction or linking table that establishes and manages the relationship between a person (student or other party) and a specific correspondence item generated by the system. Its primary role is to track which correspondence documents have been issued to which individuals, serving as a critical audit and history table for student communications. As a multi-organization table (indicated by the "_ALL" suffix), it stores data across multiple operating units, adhering to the standard EBS security model. The table's existence is fundamental to the Correspondence module, enabling the system to query and report on the complete correspondence history for any person.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies a single person-correspondence link. The key columns are PERSON_ID (linking to HZ_PARTIES to identify the individual), CORRESPONDENCE_TYPE, REFERENCE_NUMBER, and ISSUE_DT (collectively identifying the specific correspondence item from IGS_CO_ITM_ALL). Beyond these identifiers, the table includes foreign key columns that link to other related entities. The SPL_SEQUENCE_NUMBER column, in conjunction with CORRESPONDENCE_TYPE, links to the IGS_CO_S_LTR table for standard letter definitions. The TRACKING_ID column links to the IGS_TR_ITEM_ALL table, connecting the correspondence to a tracking item, likely for workflow or delivery status. The table also maintains a recursive relationship with IGS_CO_OU_CO_REF_ALL for tracking referenced or related correspondence links.

Common Use Cases and Queries

A primary use case is generating a complete history of all correspondence sent to a specific student, which is essential for student services and compliance reporting. Another common scenario involves identifying all recipients of a particular batch of letters (e.g., a specific financial aid notification) for follow-up or reporting purposes. Development and reporting often require joining this table to person and correspondence detail tables. A typical query pattern would be:

• SELECT hzp.party_name, icoa.* FROM igs_co_ou_co_all icoa JOIN hz_parties hzp ON icoa.person_id = hzp.party_id JOIN igs_co_itm_all icia ON icoa.correspondence_type = icia.correspondence_type AND icoa.reference_number = icia.reference_number WHERE icoa.person_id = :student_id ORDER BY icoa.issue_dt DESC;

This table is also central to any custom logic or interface that needs to programmatically associate a newly generated correspondence item with its intended recipient(s).

Related Objects

The IGS_CO_OU_CO_ALL table sits at the center of a network of foreign key relationships within the Student System. Its documented dependencies are:

• IGS_CO_ITM_ALL: Joined via CORRESPONDENCE_TYPE and REFERENCE_NUMBER. This is the primary relationship to the correspondence item header/details.
• HZ_PARTIES: Joined via PERSON_ID. This links the record to the Trading Community Architecture (TCA) to identify the person/student.
• IGS_CO_S_LTR: Joined via CORRESPONDENCE_TYPE and SPL_SEQUENCE_NUMBER. This links to the standard letter template used.
• IGS_TR_ITEM_ALL: Joined via TRACKING_ID. This connects the correspondence to a tracking record.
• IGS_CO_OU_CO_REF_ALL: This table references IGS_CO_OU_CO_ALL via its full primary key (PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, ISSUE_DT), establishing a parent-child relationship for tracking referenced correspondence links.

The primary key constraint IGS_CO_OU_CO_PK enforces uniqueness on the combination of these four key columns.