Search Results igs_tr_type_step_all




Overview
Explore in AI Chat

Overview

The table IGS_TR_TYPE_STEP_ALL is a core data entity within the Oracle E-Business Suite's Student System (IGS), specifically designed to manage tracking workflows. Its primary function is to define the default sequence of steps or actions associated with a specific tracking type. A tracking type typically represents a category of administrative or academic process, such as a disciplinary procedure or an application review. This table establishes the standard template of steps for each type, which can then be instantiated for individual cases. It is important to note that the IGS module is marked as "Obsolete" in the provided ETRM documentation, indicating it is a legacy component. Furthermore, the metadata explicitly states it was "Not implemented in this database," suggesting potential variability in its deployment across EBS instances.

Key Information Stored

The table stores configuration data that links a tracking type to its constituent workflow steps. The primary key is a composite of TRACKING_TYPE and TRACKING_TYPE_STEP_ID, ensuring uniqueness of each step within a type. Key columns include TRACKING_TYPE, which references the parent tracking type definition in IGS_TR_TYPE_ALL. The TRACKING_TYPE_STEP_ID uniquely identifies a step within that type's sequence. The STEP_CATALOG_CD column is a foreign key to IGS_TR_STEP_CTLG_ALL, linking to a catalog that describes the step's generic attributes and behavior. The RECIPIENT_ID column, a foreign key to HZ_PARTIES, is critical for workflow routing, as it likely defines the default party (e.g., a role, person, or organization) responsible for executing or overseeing this step.

Common Use Cases and Queries

This table is central to setting up and querying the standard workflow for any administrative tracking process. A common use case is generating a report of all default steps for a given tracking type to audit or modify process templates. For example, an administrator might need to see the full sequence of steps for the 'Academic Probation' tracking type. Sample SQL to retrieve this information, including the step description from the catalog and the default recipient, would be:

  • SELECT tt.tracking_type, ts.tracking_type_step_id, sc.step_name, hp.party_name AS default_recipient FROM igs_tr_type_step_all ts JOIN igs_tr_step_ctlg_all sc ON ts.step_catalog_cd = sc.step_catalog_cd LEFT JOIN hz_parties hp ON ts.recipient_id = hp.party_id WHERE ts.tracking_type = '&TRACKING_TYPE_CODE' ORDER BY ts.tracking_type_step_id;

Another key use case is during the creation of a new tracking instance, where the system queries this table to copy the default step template into the instance-specific tracking tables.

Related Objects

IGS_TR_TYPE_STEP_ALL sits at the center of a defined relational structure within the tracking module. Its documented relationships are as follows:

  • Parent References (Foreign Keys From): The table draws its core definitions from three master tables.
    • IGS_TR_TYPE_ALL via the TRACKING_TYPE column.
    • IGS_TR_STEP_CTLG_ALL via the STEP_CATALOG_CD column.
    • HZ_PARTIES via the RECIPIENT_ID column.
  • Child Reference (Foreign Key To): The table is referenced as a parent by one other entity.
    • IGS_TR_TYP_STEP_NOTE, via the composite foreign key on (TRACKING_TYPE, TRACKING_TYPE_STEP_ID). This table likely stores notes or additional instructions specific to each step type.