Results for “other_reference”

37 results




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

Overview

IGS_CO_OU_CO_REF_ALL is a transactional table within the Oracle E-Business Suite IGS (Student System) module, which is documented as obsolete in release 12.1.1 and 12.2.2. The table stores specific person references that are associated with an outgoing correspondence item generated by the institution. In practice, an outgoing correspondence record (such as an admissions decision letter, an enrollment notification, or a fee reminder) can be addressed to or reference multiple individuals; IGS_CO_OU_CO_REF_ALL captures those individual reference entries and links each one to the parent correspondence and, where applicable, to the academic context in which the correspondence was issued.

The ETRM metadata classifies this object heuristically as a link table within a Data Vault modeling suggestion. This is consistent with its structure: the table carries no descriptive attributes of its own beyond control columns, and its composition is dominated by foreign key references to the parent outgoing correspondence record and to academic instance, course version, and unit version entities. It therefore acts as an associative entity resolving relationships between people and correspondence items.

Key Information Stored

The primary key IGS_CO_OU_CO_REF_PK is a composite business key rather than a surrogate identifier. It is composed of PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, ISSUE_DT, and SEQUENCE_NUMBER. A unique index, IGS_CO_OU_CO_REF_U1, mirrors the same five columns, confirming that this combination uniquely identifies each reference row.

The remaining columns are standard Oracle EBS WHO/audit and concurrent program control attributes (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical reporting scenarios involve tracing which persons were referenced on a given outgoing correspondence, or which correspondence items reference a particular course, unit, or calendar instance.

  • List references for a person: SELECT correspondence_type, reference_number, issue_dt FROM igs_co_ou_co_ref_all WHERE person_id = :p_person_id;
  • References tied to a course version: join COURSE_CD and CV_VERSION_NUMBER to IGS_PS_VER_ALL to report correspondence linked to a curriculum.
  • Unit-level reconciliation: join UNIT_CD and UV_VERSION_NUMBER to IGS_PS_UNIT_VER_ALL.
  • Calendar context: join CAL_TYPE and CI_SEQUENCE_NUMBER to IGS_CA_INST_ALL to attribute references to academic periods.
  • Operational audits: filter on CREATION_DATE or PROGRAM_ID to review batch-generated correspondence references.

Because the module is obsolete and the table is documented as not implemented in the current database, queries should be validated against the actual installation before use.

Related Objects

  • IGS_CO_OU_CO_ALL – parent outgoing correspondence table; joined on PERSON_ID, CORRESPONDENCE_TYPE, REFERENCE_NUMBER, and ISSUE_DT.
  • IGS_CA_INST_ALL – calendar instance; joined on CAL_TYPE and CI_SEQUENCE_NUMBER.
  • IGS_PS_VER_ALL – course version; joined on COURSE_CD and CV_VERSION_NUMBER.
  • IGS_PS_UNIT_VER_ALL – unit version; joined on UNIT_CD and UV_VERSION_NUMBER.
  • IGS_CO_OU_CO_REF_PK / IGS_CO_OU_CO_REF_U1 – primary key constraint and unique index enforcing the composite business key.