Search Results igs_tr_item_note
Overview
The IGS_TR_ITEM_NOTE table is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, which is documented as obsolete. This table serves as a junction or association table designed to link tracking items with their corresponding notes. Its primary role is to store references that connect a specific tracking item, managed within the student tracking functionality, to one or more notes stored in the system's generic notes repository. This structure allows for a normalized data model where notes can be centrally managed and reused while being contextually linked to specific tracking items.
Key Information Stored
The table's structure is defined by its composite primary key and foreign key relationships. The two columns forming the primary key are TRACKING_ID and REFERENCE_NUMBER. The TRACKING_ID column uniquely identifies the associated tracking item from the IGS_TR_ITEM_ALL table. The REFERENCE_NUMBER column is a foreign key that points to the specific note's identifier in the IGS_GE_NOTE (Generic Notes) table. An additional key column, TRK_NOTE_TYPE, references the IGS_TR_NOTE_TYPE table, presumably to categorize the note (e.g., internal comment, external communication, system-generated log). This design ensures that each note reference is uniquely tied to a single tracking item.
Common Use Cases and Queries
A primary use case is retrieving all notes attached to a particular student tracking item for review by an advisor or administrator. This supports audit trails, communication history, and decision-logging within student service processes. A typical query would join IGS_TR_ITEM_NOTE with IGS_GE_NOTE to fetch the note text and details. For example:
- SELECT n.note_text, itin.trk_note_type FROM igs_tr_item_note itin JOIN igs_ge_note n ON itin.reference_number = n.reference_number WHERE itin.tracking_id = :tracking_id ORDER BY n.creation_date;
Another common scenario is reporting, such as generating a list of all tracking items that have a specific type of note attached. It is critical to note that, according to the provided metadata, this table was "Not implemented in this database," indicating it may exist only in the data model documentation and not in active deployments, which would limit practical queries.
Related Objects
The table has defined foreign key relationships with three core tables in the IGS module:
- IGS_TR_ITEM_ALL: The relationship is via the TRACKING_ID column. This is the parent table for tracking items.
- IGS_GE_NOTE: The relationship is via the REFERENCE_NUMBER column. This table stores the actual note text and metadata.
- IGS_TR_NOTE_TYPE: The relationship is via the TRK_NOTE_TYPE column. This lookup table defines the valid types or categories for a tracking note.
The table's primary key constraint is named IGS_TR_ITEM_NOTE_PK. Its existence is wholly dependent on these related objects, functioning as a relational bridge between the tracking item entity and the generic notes subsystem.
-
Table: IGS_TR_ITEM_NOTE
12.2.2
product: IGS - Student System (Obsolete) , description: This table will store references to notes held against a tracking item. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_TR_NOTE_TYPE
12.2.2
product: IGS - Student System (Obsolete) , description: This table describes the user-defined note types for the Tracking Facility , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_TR_ITEM_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: Describes each occurrence of a tracking process for a particular student. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_GE_NOTE
12.2.2
product: IGS - Student System (Obsolete) , description: This table is used to store notes that may be recorded against many major entities for example courses, units, persons. The note may be an OLE object like word document, excel spreadsheet, and so on. , implementation_dba_data: Not implemented in this database ,