Results for “igs_co_type”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_CO_TYPE is a system-defined reference table in the IGS (Student System) product of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2 releases. The table describes the available system-defined correspondence types used throughout the Student System correspondence framework. It is owned by the IGS schema and holds a VALID status within the ETRM repository.

Functionally, IGS_CO_TYPE acts as a lookup and control entity: each row defines one correspondence type that other IGS correspondence objects reference. The documented physical schema lists eleven columns, and the primary key is enforced by the constraint IGS_CO_TYPE_PK on the CORRESPONDENCE_TYPE column. A unique index, IGS_CO_TYPE_U1, also exists on CORRESPONDENCE_TYPE, confirming that the column carries business-key significance rather than being a meaningless surrogate identifier. Because correspondence types are system-defined, the table is populated during implementation rather than maintained as free-form user entry data.

From a Data Vault modeling perspective, the mined FK structure suggests a hub-leaning classification. IGS_CO_TYPE is referenced by seven dependent tables and references none itself, which is characteristic of a hub entity holding a durable business key (CORRESPONDENCE_TYPE) surrounded by descriptive attributes. Downstream tables that reference it behave as satellites or link participants.

Key Information Stored

The most significant columns documented in the ETRM schema are:

  • CORRESPONDENCE_TYPE — the business key and primary key column; the unique index IGS_CO_TYPE_U1 confirms its uniqueness. Every dependent table joins on this column.
  • DESCRIPTION — the human-readable label presented to users when selecting or reporting on a correspondence type.
  • SYS_GENERATED_IND — indicates whether the correspondence type was seeded by the system rather than created by an administrator.
  • CLOSED_IND — flags a correspondence type as inactive or closed, preventing new correspondence from being created against it while preserving historical rows.
  • JOB_APPLICATION_ID and JOB_PROGRAM_ID — reference the concurrent program or application context associated with processing or generating the correspondence type, supporting automated correspondence runs.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS who-columns providing audit lineage for each row.

The primary key (CORRESPONDENCE_TYPE) is effectively the same column as the unique business key, so no separate synthetic surrogate is documented. Administrators and developers should treat CORRESPONDENCE_TYPE as the stable identifier when joining to child correspondence tables.

Common Use Cases and Queries

Typical usage falls into three areas: resolving correspondence type descriptions on reports, validating referential integrity across correspondence objects, and filtering out closed or non-system types during setup reviews. A representative query joining the type to one of its child tables follows:

  • SELECT ct.correspondence_type, ct.description, ci.correspondence_item FROM igs_co_type ct, igs_co_itm ci WHERE ct.correspondence_type = ci.correspondence_type AND NVL(ct.closed_ind,'N') = 'N';
  • Setup auditing: SELECT correspondence_type, description, sys_generated_ind FROM igs_co_type WHERE sys_generated_ind = 'Y';
  • Concurrent program tracing: SELECT correspondence_type, job_application_id, job_program_id FROM igs_co_type;

Reporting extracts commonly use this table as a decode source so that correspondence identifiers appear as meaningful labels in student communication reports. Because the table is small and static, it is a safe candidate for caching in PL/SQL lookup logic or in custom reporting views.

Related Objects

The ETRM metadata documents seven tables that reference IGS_CO_TYPE through the CORRESPONDENCE_TYPE foreign key column. The most significant are:

Because no outbound foreign keys are documented, IGS_CO_TYPE is a pure parent entity; integrity flows downward from it into the correspondence catalog, letter, and restriction tables listed above.