Results for “igs_tr_group_note”

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

Overview

IGS_TR_GROUP_NOTE is a transactional table within the IGS (Student System) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. As stated in the ETRM repository documentation, the table "will store references to notes held against a tracking group." In practical terms, it functions as an association table that links a student tracking group — the grouping mechanism used by institutions to monitor cohorts, admissions cycles, or academic-progress milestones — to individual note records maintained in the general notes repository.

The object carries the Data Vault classification of link, derived heuristically from its foreign key structure. This is a modeling suggestion rather than a mandated design: the table's purpose is to resolve a many-to-many-style association between tracking groups and notes, which is the characteristic role of a link entity. The ETRM record indicates that the table is not implemented in the current database, and the IGS product line is flagged as obsolete. Consequently, the table should be regarded as a legacy schema artifact that may surface during upgrades, custom reporting, or data-migration analysis of older Student System installations.

Key Information Stored

The documented physical schema comprises eight columns, of which the following are the most significant:

• TRACKING_GROUP_ID — Identifier of the tracking group to which the note reference belongs. This column also participates in the primary key and in a foreign key to IGS_TR_GROUP_ALL.
• REFERENCE_NUMBER — Identifier of the note record. It forms the second component of the compound primary key and carries a foreign key to IGS_GE_NOTE.
• TRK_NOTE_TYPE — Classifies the note within the tracking-group context; constrained by a foreign key to IGS_TR_NOTE_TYPE.
• CREATED_BY, CREATION_DATE — Standard EBS WHO-column audit attributes capturing the creating user and timestamp.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit attributes recording the most recent modification and the login session responsible for it.

The surrogate primary key is defined by the constraint IGS_TR_GROUP_NOTE_PK over the composite of TRACKING_GROUP_ID and REFERENCE_NUMBER. The unique index IGS_TR_GROUP_NOTE_U1 covers the same two columns, confirming that this pair is the business-key candidate: a given note may be associated with a given tracking group only once. There is no single-column surrogate; identity is expressed entirely through the composite key.

Common Use Cases and Queries

The principal reporting scenario is enumerating the notes attached to a tracking group, optionally filtered by note type:

• Notes for a group: SELECT n.reference_number, n.trk_note_type FROM igs_tr_group_note n WHERE n.tracking_group_id = :group_id;
• Group membership for a note: SELECT g.tracking_group_id FROM igs_tr_group_note g WHERE g.reference_number = :note_id;
• Notes by type: a join to IGS_TR_NOTE_TYPE resolves TRK_NOTE_TYPE into a descriptive value for reporting.
• Audit and reconciliation: querying CREATION_DATE and LAST_UPDATE_DATE to identify recently assigned notes or orphaned references.

Because the table is a pure link with no descriptive payload beyond the note-type discriminator and audit columns, substantive note text must be retrieved by joining to IGS_GE_NOTE via REFERENCE_NUMBER.

Related Objects

• IGS_TR_GROUP_ALL — parent tracking-group definition; joined on TRACKING_GROUP_ID.
• IGS_GE_NOTE — general note repository holding note content; joined on REFERENCE_NUMBER.
• IGS_TR_NOTE_TYPE — note-type lookup; joined on TRK_NOTE_TYPE.
• IGS_TR_GROUP_NOTE_PK / IGS_TR_GROUP_NOTE_U1 — the primary-key constraint and unique index enforcing uniqueness of the group-to-note pairing.

Given its obsolete status, any integration or extension work should first verify the object's physical presence, as the ETRM metadata records it as not implemented in the reference database.