Search Results igs_co_dtl

Overview

The IGS_CO_DTL table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically designed for managing student correspondence. Its primary role is to store detailed textual information and descriptive data for individual correspondence items, such as letters, emails, or notifications generated by the institution. This table functions as a child entity, holding the substantive content linked to a correspondence header record. It is critical to note that the IGS module is marked as obsolete in the provided ETRM metadata for EBS versions 12.1.1 and 12.2.2, indicating that while the table structure exists, its associated application functionality may be deprecated, unsupported, or superseded by other solutions.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each detail record by linking it to a specific correspondence item. The key columns and their purposes are:

• CORRESPONDENCE_TYPE: A foreign key column that, in conjunction with REFERENCE_NUMBER, links the detail record to its parent correspondence item in the IGS_CO_ITM table. It classifies the type of correspondence.
• REFERENCE_NUMBER: The second part of the foreign key and primary key. This value, tied to a CORRESPONDENCE_TYPE, uniquely identifies the specific correspondence instance to which this detail text belongs.

While the specific content columns are not detailed in the excerpt, the table's description confirms it holds the descriptive text and details for the correspondence item. This typically includes fields for lengthy formatted or unformatted text, notes, or specific message bodies that comprise the correspondence content.

Common Use Cases and Queries

In an operational IGS environment, this table would be central to retrieving the full content of any sent or generated communication. A primary use case is the on-demand display of a correspondence item's complete details within the application's user interface. For reporting and data extraction, queries would join IGS_CO_DTL to the header table to produce comprehensive communication histories. A fundamental SQL pattern would be:

SELECT itm.*, dtl.*
FROM igs_co_itm itm,
     igs_co_dtl dtl
WHERE itm.correspondence_type = dtl.correspondence_type
AND itm.reference_number = dtl.reference_number
AND itm.person_id = :student_id;

Given the module's obsolete status, common use cases in later EBS versions would primarily involve historical data migration, archival reporting, or support for legacy data integrity during system upgrades.

Related Objects

The IGS_CO_DTL table exists within a defined relationship hierarchy, as evidenced by its foreign key constraints.

• IGS_CO_ITM: This is the primary parent table. The foreign key from IGS_CO_DTL (CORRESPONDENCE_TYPE, REFERENCE_NUMBER) references IGS_CO_ITM, establishing that every detail record must be associated with a valid correspondence item header.
• IGS_CO_DTL_OLE: This table holds a foreign key relationship referencing IGS_CO_DTL, indicating it is a child table that stores additional, likely Object Linking and Embedding (OLE) related, data for a correspondence detail record. This suggests the system supported embedded attachments or compound documents within correspondence.

The existence of these relationships underscores that IGS_CO_DTL was a central component in a normalized data model for managing complex, multi-part correspondence within the obsolete Student System.