Results for “igs_tr_step”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_TR_STEP is a transaction and reference table within the IGS (Student System) product module of Oracle E-Business Suite, owned by the IGS schema. Per the ETRM documentation, this entity describes a particular step of a tracking item. Steps may represent the default steps established for each tracking type, or they may be additional or alternate steps defined by an end user. In practice, the table functions as the operational backbone for the tracking workflow used across student records administration, admissions, recruitment, and academic progress monitoring, where individual tracking items must be decomposed into discrete, sequenced actions with defined completion criteria.

The table carries a documented physical schema of 22 columns in ETRM 12.1.1. Based on the foreign key structure — with references outward to IGS_TR_ITEM_ALL, IGS_TR_STEP_CTLG_ALL, and HZ_PARTIES, and an inbound reference from IGS_TR_STEP_NOTE — the heuristic Data Vault classification is satellite-leaning. This suggests that, for modeling purposes, IGS_TR_STEP is best treated as a descriptive satellite attached to the tracking item hub (IGS_TR_ITEM_ALL), capturing the changing attributes of each step over time. Both Oracle EBS 12.1.1 and 12.2.2 expose this object through the same IGS schema, with the ETRM metadata confirming VALID status.

Key Information Stored

The primary key is defined by the unique index IGS_TR_STEP_PK, formed by the composite of TRACKING_ID and TRACKING_STEP_ID. A second unique index, IGS_TR_STEP_U1 (TRACKING_ID, TRACKING_STEP_ID), serves as the documented business-key candidate. The most significant columns include:

  • TRACKING_ID — identifier of the parent tracking item; part of the composite primary key.
  • TRACKING_STEP_ID — identifier of the individual step; completes the composite primary key.
  • TRACKING_STEP_NUMBER — ordinal position of the step within the tracking sequence.
  • DESCRIPTION — human-readable label for the step.
  • S_TRACKING_STEP_TYPE — system-level code classifying the step type.
  • STEP_CATALOG_CD — catalog code referencing IGS_TR_STEP_CTLG_ALL, defining reusable step definitions.
  • COMPLETION_DT — date the step was completed.
  • ACTION_DAYS — number of days allowed or taken to perform the step action.
  • STEP_COMPLETION_IND — flag indicating whether the step is complete.
  • BY_PASS_IND — flag indicating whether the step was bypassed.
  • RECIPIENT_ID — party responsible for or associated with the step, referencing HZ_PARTIES.
  • STEP_GROUP_ID — grouping identifier for related steps.
  • PUBLISH_IND — flag controlling publication or visibility of the step.
  • LAST_UPDATE_DATE / CREATION_DATE — standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include tracking outstanding steps for a cohort of students, calculating aging on incomplete actions via ACTION_DAYS and COMPLETION_DT, and auditing bypassed steps. A representative query for incomplete steps per tracking item follows:

  • SELECT tracking_id, tracking_step_id, description, completion_dt, action_days FROM igs_tr_step WHERE step_completion_ind = 'N' AND by_pass_ind = 'N' AND tracking_id = :p_tracking_id ORDER BY tracking_step_number;
  • Aging analysis: SELECT tracking_id, tracking_step_id, SYSDATE - completion_dt elapsed_days FROM igs_tr_step WHERE step_completion_ind = 'N';
  • Catalog usage: join to IGS_TR_STEP_CTLG_ALL on STEP_CATALOG_CD to reconcile user-defined steps against catalog defaults.

Related Objects

  • IGS_TR_ITEM_ALL — parent tracking item; joined on IGS_TR_STEP.TRACKING_ID.
  • IGS_TR_STEP_CTLG_ALL — step catalog; joined on STEP_CATALOG_CD.
  • HZ_PARTIES — recipient party; joined on RECIPIENT_ID.
  • IGS_TR_STEP_NOTE — child notes; joined on TRACKING_ID and TRACKING_STEP_ID.