Search Results sync_trk_type_grplmt

Overview

IGS_TR_GEN_002 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM API classification of OTHER. It is a supporting component of the Oracle Grants / Contracts Tracking module (IGS_TR) and consolidates the programmatic logic used to maintain tracking items, tracking steps, tracking step notes, and tracking group memberships. Its declared purpose, as documented in the package header, is the deletion of tracking step notes, deletion of tracking steps for tracking items, deletion of tracking group members for IGS_TR_ITEMS, deletion of tracking item notes for IGS_TR_ITEMS, and deletion of IGS_TR_ITEMS records themselves. In addition, the package exposes utility routines that determine the status of a tracking group or tracking item, insert default tracking statuses and tracking items, update tracking statuses, validate completion status, synchronize tracking type and item group limits, and confirm whether a previous step has completed. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema rather than the definer, and its original header indicates it was created by Oracle IDC with a shipping revision history dating from 2002.

Key Procedures and Functions

Ten documented program units are exposed by this package:

• TRKP_DEL_TRI — Deletes a tracking item (and its dependent notes, steps, and group memberships) identified by a tracking identifier, returning a Boolean result and an outgoing message name. This is the entry point referenced by the search term trkp_del_tri.
• TRKP_GET_GROUP_STS — Returns the current status of a tracking group as a VARCHAR2 value. It carries a PRAGMA RESTRICT_REFERENCES declaration for WNDS (Write No Database State), confirming it is a read-only query function.
• TRKP_GET_ITEM_STATUS — Returns the current status of a specific tracking item.
• TRKP_INS_DFLT_TRST — Inserts default tracking status rows for a tracking entity.
• TRKP_INS_TRK_ITEM — Creates a new tracking item record.
• TRKP_UPD_TRST — Updates an existing tracking status record.
• SYNC_TRK_TYPE_GRPLMT — Synchronizes tracking type group limit definitions.
• SYNC_TRK_ITEM_GRPLMT — Synchronizes tracking item group limit definitions, propagating group limit rules to individual items.
• VALIDATE_COMPLETION_STATUS — Validates whether a tracking entity may be marked as complete, enforcing business rules around completion.
• TRKP_PREV_STEP_CMPLT — Determines whether the preceding step in a tracking sequence has completed, supporting step-sequencing logic.

Tables Accessed

The package operates against several IGS_TR and IGS_GE tables through APPS synonyms. Tracking item and step data are read and written in IGS_TR_STEP, IGS_TR_STEP_NOTE, IGS_TR_STEP_GRP_LMT, IGS_TR_ITEM_NOTE, IGS_TR_STATUS, and IGS_TR_TSTP_GRP_LMT, which support deletion, insertion, status update, and group-limit synchronization. IGS_TR_GROUP_MEMBER stores the group membership rows removed when a tracking item is deleted. IGS_TR_TYP_STEP_NOTE and IGS_TR_STEP_GRP_LMT hold type-level and step-level note and limit definitions consulted during synchronization and validation. Notes are stored in IGS_GE_NOTE, with sequence numbers drawn from IGS_GE_NOTE_RF_NUM_S and tracking item transaction identifiers from IGS_TR_ITEM_TR_ID_S. DUAL and PLITBLM are used for scalar evaluation and PL/SQL table operations respectively.

Usage Notes

IGS_TR_GEN_002 is invoked primarily from the tracking forms, notably IGSTR007.fmb, and is referenced by eight other packages within the EBS codebase. It is not intended as a standalone concurrent program; rather, it is a subordinate API layer called by form-level triggers and by sibling packages that require tracking item maintenance, status resolution, or group-limit synchronization. Customizations extending tracking behavior should call these routines rather than issuing direct DML against the underlying IGS_TR tables, because the deletion routines cascade across step notes, item notes, and group members in a controlled sequence. The AUTHID CURRENT_USER declaration means executing sessions must hold the necessary object privileges themselves, a consideration when invoking the package from restricted or report-only responsibility contexts.