Search Results igs_tr_gen_001




Overview
Explore in AI Chat

Overview

IGS_TR_ITEM_V is a reporting view belonging to the IGS (Student System) product family within Oracle E-Business Suite. The IGS module is documented in ETRM as obsolete, and the view carries the annotation "Not implemented in this database," indicating that it is not present in every EBS instance and should be treated with caution when referenced in custom code or reports. The view exposes tracking item records — rows describing individual tracking assignments generated against a tracking type — together with derived columns that surface computed target dates, completion dates, and overdue durations. Its principal design purpose is to encapsulate the business logic of the tracking engine (packaged in IGS_TR_GEN_001) so that forms, concurrent programs, and custom reports can retrieve fully calculated tracking status information from a single SELECT statement rather than re-implementing the date arithmetic themselves.

Underlying Base Objects

Although the ETRM metadata entry lists no referenced base objects, the view text documents the actual sources. The primary table is IGS_TR_ITEM (aliased TRI), which stores the tracking item rows themselves, including tracking status, tracking type, target days, and audit columns. It is joined to IGS_TR_TYPE (TRT) on TRACKING_TYPE to supply the descriptive text for the type. Two outer-joined lookups against IGS_PE_PERSON_BASE_V (aliased PE1 for the source person and PE2 for the originator) resolve person identifiers into person numbers and preferred display names; the (+) notation confirms these joins are outer joins, so tracking items persist even when a person record is missing. A defining characteristic of the view is its repeated invocation of the IGS_TR_GEN_001 package functions — TRKP_CLC_DT_OFFSET, TRKP_CLC_TRI_CMP_DT, and TRKP_CLC_DAYS_OVRDUE — which calculate the target date, the completion date, and the number of overdue days respectively. This coupling means view performance is sensitive to the cost of those PL/SQL calls per row.

Key Columns

Common Use Cases and Queries

The view is typically queried for tracking dashboards, overdue tracking-item reports, and integration extracts that feed downstream workflow or notification processes. A representative query for outstanding overdue items:

  • SELECT tracking_id, tracking_type, description, source_person_number, dsp_preferred_name2, start_dt, target_dt, completion_due_dt, overdue_days FROM igs_tr_item_v WHERE tracking_status = 'INCOMPLETE' AND overdue_days > 0 ORDER BY overdue_days DESC;
  • SELECT tracking_type, COUNT(*) total_items, SUM(NVL(overdue_days,0)) total_overdue FROM igs_tr_item_v WHERE org_id = :p_org_id GROUP BY tracking_type;
  • SELECT tracking_id, originator_person_number, start_dt, target_days, business_days_ind, target_dt FROM igs_tr_item_v WHERE publish_ind = 'Y';

Because the view embeds package function calls, large-volume extracts should be filtered before aggregation, and any site where the "not implemented" annotation applies will receive an ORA-00942 error, so existence should be verified in ALL_VIEWS before deployment.