Search Results tracking_step




Overview

IGS_TR_GEN_002 is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Student System / Academic Tracker (IGS) product family and provides the low-level programmatic infrastructure for maintaining tracking items, tracking steps, tracking groups, and the status records associated with them. The package is classified under the generic API category "OTHER" in the ETRM metadata, meaning it is an internally consumed utility rather than a formally published open interface.

The header comment records the package as Oracle IDC work, with a modification dated 27 August 2001 (Bug 1956374) that repointed the genp_al_prsn_id reference to igs_co_val_oc. This indicates the package has been in production since the earliest releases of the Student System tracking subsystem and has been maintained through the 12.1.1 and 12.2.2 code lines.

The primary documented entry point is trkp_del_tri, whose stated purpose is the deletion of tracking step notes, tracking steps within tracking items, tracking group members for IGS_TR_ITEMS, tracking item notes, and finally the IGS_TR_ITEMS row itself. This cascading delete capability makes the package the transactional heart of tracking-item maintenance. The internal helper trkpl_del_tsn illustrates the pattern: it opens an explicit cursor over IGS_TR_STEP_NOTE with FOR UPDATE OF tracking_id NOWAIT, handles the e_resource_busy condition (Oracle error -54) raised when a row is locked by another session, and delegates physical deletion to the generated table handler igs_tr_step_note_pkg.delete_row.

Key Procedures and Functions

Tables Accessed

Usage Notes

The package is invoked from the tracking forms, most directly IGSTR007.fmb for tracking-item deletion, and is referenced by eight other packages within the IGS schema. It is not a concurrent-program entry point and carries no concurrent-program registration. Customisations should call the documented procedures rather than deleting tracking rows directly, because the delete routine enforces cursor-level locking, raises the busy-resource exception, and propagates note deletions to IGS_GE_NOTE.