Results for “igs_co_interac_hist”

35 results




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

Overview

IGS_CO_INTERAC_HIST is a table within the IGS–Student System product family in Oracle E-Business Suite, described in the ETRM metadata as "Interaction History." It is documented as obsolete in both the 12.1.1 and 12.2.2 releases. The ETRM record explicitly states "Not implemented in this database," meaning the object is retained in the data dictionary documentation for backward compatibility and historical reference but is not physically created or populated in a standard installation. Any query against it in a live environment will typically fail unless a legacy or customized schema has preserved the structure.

The table's purpose, as its name implies, was to record interactions associated with students in the Oracle Student System, such as correspondence, communications, or administrative transactions linked to a student record and a requesting process. The Data Vault classification heuristic mined from the foreign key structure labels this object as satellite-leaning. In Data Vault modeling terms, a satellite captures descriptive attributes and history tied to a parent hub or link. That classification suggests a modeling recommendation: treat IGS_CO_INTERAC_HIST as a historical, descriptive store dependent on business keys managed elsewhere, rather than as an independent hub of business identity.

Key Information Stored

The documented physical schema for the 12.1.1 release lists an owner of IGS with 20 columns. The primary key is defined by IGS_CO_INTERAC_HIST_PK on REQUEST_ID, and a unique index IGS_CO_INTERAC_HIST_U1 also covers REQUEST_ID. Notably, REQUEST_ID serves simultaneously as the surrogate primary key and as the sole documented unique business-key candidate, which is unusual in that it does not, by itself, carry obvious business meaning.

The most significant columns include:

Common Use Cases and Queries

Because the table is obsolete and not implemented, production use cases are largely historical. Potential queries would join to HZ_PARTIES on STUDENT_ID and to VEA_VERSIONS on VERSION_ID to reconstruct interaction timelines per student or per versioned entity.

  • A representative join: SELECT i.request_id, i.student_id, i.document_type, i.date_sent FROM igs_co_interac_hist i, hz_parties hp WHERE i.student_id = hp.party_id;
  • Reporting on correspondence volume by DELIVERY_TYPE or COMP_STATUS for a given REQUESTED_DATE range.
  • Auditing interaction sequences using CI_SEQUENCE_NUMBER and SEQUENCE_NUMBER to trace a student's document history.
  • Cross-referencing VERSION_ID against VEA_VERSIONS to determine which version of a student record was active when an interaction occurred.

Related Objects

The documented foreign key relationships identify the primary related objects:

  • HZ_PARTIES — referenced by IGS_CO_INTERAC_HIST.STUDENT_ID; the master party record for the student.
  • VEA_VERSIONS — referenced by IGS_CO_INTERAC_HIST.VERSION_ID; provides version context.

Additional IGS Student System objects commonly associated with interaction and correspondence processing—such as document and letter definition tables—may exist in legacy installations but are not enumerated in the provided metadata. Migration or conversion efforts involving the IGS module should treat this table as documentation-only unless a custom schema confirms its presence. Oracle's legal notices mark the underlying documentation as proprietary and confidential.