Search Results tracking_step_id




Overview
Explore in AI Chat

Overview

The IGS_TR_STEP_NOTE table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Oracle Student Management) product family. It functions as a junction table that establishes and stores the relationship between tracking steps and the notes associated with them. Its primary role is to enable the attachment of categorized, institution-defined notes to specific steps in a tracking workflow, thereby providing contextual documentation and audit history for actions taken during a process. The table is essential for maintaining a complete record of communications and remarks tied to each procedural step within the tracking facility.

Key Information Stored

The table's structure is designed to link three key identifiers and categorize the note. The mandatory columns TRACKING_ID and TRACKING_STEP_ID together uniquely identify the specific step within a tracking item. The REFERENCE_NUMBER column holds a foreign key to the actual note text stored in a generic notes table (e.g., IGS_GE_NOTE). The TRK_NOTE_TYPE column allows for categorization of the note based on institution-defined types, which are managed via the IGS_TR_NOTE_TYPE lookup. Standard "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide essential audit information for each record. The primary key is a composite of TRACKING_ID, TRACKING_STEP_ID, and REFERENCE_NUMBER, ensuring a note can be linked to a step only once.

Common Use Cases and Queries

A primary use case is retrieving all notes attached to a particular tracking step for review or reporting, often in support or audit scenarios. Developers and report writers commonly query this table to join note text with tracking step details. A sample query to fetch all notes for a specific tracking step, including the note type description, would be:

  • SELECT itsn.*, ign.note_text, itnt.description FROM igs_tr_step_note itsn, igs_ge_note ign, igs_tr_note_type itnt WHERE itsn.tracking_id = :p_tracking_id AND itsn.tracking_step_id = :p_tracking_step_id AND itsn.reference_number = ign.reference_number AND itsn.trk_note_type = itnt.trk_note_type ORDER BY itsn.creation_date;

Another common pattern is data validation or cleanup scripts that identify steps with notes of a specific type or orphaned note references.

Related Objects

The IGS_TR_STEP_NOTE table is central to the tracking notes model and has defined foreign key relationships with several key tables:

  • IGS_TR_STEP: The relationship IGS_TR_STEP_NOTE.TRACKING_ID → IGS_TR_STEP ensures a note is associated with a valid tracking step. The join typically uses TRACKING_ID and TRACKING_STEP_ID.
  • IGS_GE_NOTE: The relationship IGS_TR_STEP_NOTE.REFERENCE_NUMBER → IGS_GE_NOTE links the reference to the actual note text stored in a generic notes table.
  • IGS_TR_NOTE_TYPE: The relationship IGS_TR_STEP_NOTE.TRK_NOTE_TYPE → IGS_TR_NOTE_TYPE validates the note type against the institution-defined lookup values.

Within the APPS schema, a synonym named IGS_TR_STEP_NOTE exists, providing public access to this table for authorized EBS modules and custom code.