Search Results igs_tr_item_all




Overview
Explore in AI Chat

Overview

The IGS_TR_ITEM_ALL table is a core data structure within the Oracle E-Business Suite Student System (IGS) for releases 12.1.1 and 12.2.2. It serves as the master transactional table for recording and managing individual tracking items. Each row in this table represents a single, concrete instance of a defined tracking process that has been initiated for a specific student. A tracking process is a workflow mechanism used to monitor and manage student-related activities, such as application reviews, admission requirements, academic progress milestones, or disciplinary actions. The table's role is to persist the lifecycle state of each tracking item, link it to the relevant student and process definition, and provide a central point of reference for all related actions and data.

Key Information Stored

The table's primary key is the TRACKING_ID, a unique identifier for each tracking item instance. Two critical foreign keys define the tracking item's context: TRACKING_TYPE, which references IGS_TR_TYPE_ALL to identify the category or template of the tracking process, and TRACKING_STATUS, which references IGS_TR_STATUS to denote the item's current state (e.g., Open, In Progress, Closed, Cancelled). The table links to the person/party model via SOURCE_PERSON_ID and ORIGINATOR_PERSON_ID, connecting the tracking item to the student being tracked and the individual who initiated it, respectively. Additional columns typically store creation dates, last update dates, and other attributes that describe the specific occurrence of the tracking item for audit and management purposes.

Common Use Cases and Queries

A primary use case is generating reports on open tracking items for students within a specific program or of a certain type, such as all pending admission requirement verifications. Administrators may query the table to monitor workload or identify bottlenecks. Common SQL patterns involve joining to person (HZ_PARTIES) and tracking type tables. For example, to find all active tracking items for a student:

  • SELECT ti.tracking_id, tt.name type_name, ts.status FROM igs_tr_item_all ti, igs_tr_type_all tt, igs_tr_status ts WHERE ti.tracking_type = tt.tracking_type AND ti.tracking_status = ts.tracking_status AND ti.source_person_id = <STUDENT_PERSON_ID>;

Another key use case is integration, where downstream processes, like updating an application instance or a thesis examination record, consume or update the TRACKING_ID to reflect progress.

Related Objects

IGS_TR_ITEM_ALL has extensive relationships within the Student System. It is the parent table for several key transactional entities, including IGS_TR_ITEM_NOTE (for notes), IGS_TR_STEP (for process steps), and IGS_TR_GROUP_MEMBER (for grouping items). Crucially, it is referenced by major application tables, demonstrating its central role: IGS_AD_APLINS_ADMREQ (Admission Requirements), IGS_AD_PS_APPL_INST_ALL (Application Instances), IGS_AS_SU_ATMPT_ITM (Assessment Items), and IGS_RE_THESIS_EXAM (Thesis Examinations). Its definitions are governed by IGS_TR_TYPE_ALL and IGS_TR_STATUS, and it links to the Trading Community Architecture via HZ_PARTIES for person data.