Search Results trk_note_type




Overview
Explore in AI Chat

Overview

The IGS_TR_GROUP_NOTE table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Global Systems (IGS) modules. It functions as a junction or association table within the tracking facility. Its primary role is to maintain relationships between tracking groups and the system notes attached to them. By storing these references, it enables the categorization and management of textual information (notes) against defined tracking groups, which are used to monitor specific entities or processes within the institution.

Key Information Stored

The table's structure is designed to link three key entities: a tracking group, a note, and a note type. The TRACKING_GROUP_ID column is a foreign key that uniquely identifies the associated tracking group. The REFERENCE_NUMBER column is a foreign key that uniquely identifies the specific note text stored elsewhere in the system. The most critical column for categorization is TRK_NOTE_TYPE, a VARCHAR2(10) field that holds the institution-defined name for the type of note (e.g., 'LOG', 'WARNING', 'REVIEW'). This type is used to classify the purpose of the note within the tracking context. The table also includes standard Oracle EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing. The primary key is a composite of TRACKING_GROUP_ID and REFERENCE_NUMBER, ensuring a note can be linked to a specific group only once.

Common Use Cases and Queries

A primary use case is retrieving all notes of a specific type for a set of tracking groups, which is essential for reporting and audit trails. For instance, an institution may need to extract all 'WARNING' type notes associated with active student tracking groups. The column TRK_NOTE_TYPE is frequently used in WHERE clauses for such filtering. Common SQL patterns include joining this table to the note detail and tracking group tables to create meaningful reports.

  • Sample Query to Fetch Notes by Type and Group:
    SELECT gtn.TRACKING_GROUP_ID, gtn.TRK_NOTE_TYPE, gn.note_text
    FROM IGS_TR_GROUP_NOTE gtn,
        IGS_GE_NOTE gn,
        IGS_TR_GROUP_ALL tg
    WHERE gtn.REFERENCE_NUMBER = gn.REFERENCE_NUMBER
    AND gtn.TRACKING_GROUP_ID = tg.TRACKING_GROUP_ID
    AND gtn.TRK_NOTE_TYPE = 'WARNING'
    AND tg.STATUS = 'ACTIVE';
  • Use Case: Data integrity checks to find tracking groups that have no associated notes or to validate that all notes have a valid TRK_NOTE_TYPE defined in the reference table.

Related Objects

The IGS_TR_GROUP_NOTE table sits at the intersection of three key reference tables, as defined by its foreign key constraints:

  • IGS_TR_GROUP_ALL: References via TRACKING_GROUP_ID. This is the master table for tracking groups.
  • IGS_GE_NOTE: References via REFERENCE_NUMBER. This is the generic notes table where the actual note text is stored.
  • IGS_TR_NOTE_TYPE: References via TRK_NOTE_TYPE. This lookup table validates and defines the allowable note type codes used for categorization within the tracking facility.

The table is also referenced by an APPS synonym (IGS_TR_GROUP_NOTE), which is the standard access point for all application code within Oracle EBS, abstracting the underlying schema (IGS).