Results for “igs_tr_item_all”

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

Overview

IGS_TR_ITEM_ALL is a transactional table within the Oracle EBS IGS — Student System product family, a module now classified as obsolete in the EBS 12.1.1 and 12.2.2 documentation sets. The table records each discrete occurrence of a tracking process applied to a particular student. In the higher-education data model, a tracking item represents an actionable workflow instance — an admissions checklist entry, a document requirement, a thesis milestone, or an advising task — progressing through defined statuses. Each row therefore embodies one live or historical tracking event tied to a party, an application, and a tracking type definition.

From a Data Vault modeling perspective, the metadata heuristically classifies this object as hub-leaning. The single-column primary key TRACKING_ID, referenced by a wide fan of dependent tables, reinforces its role as a central business entity rather than a pure intersection or descriptive satellite. Analysts should treat IGS_TR_ITEM_ALL as the spine around which tracking steps, notes, and group assignments accumulate.

Key Information Stored

The table exposes 23 documented columns. The most consequential are:

• TRACKING_ID — surrogate primary key defined by IGS_TR_ITEM_ALL_PK and reinforced by unique index IGS_TR_ITEM_ALL_U1. This value is the join key propagated to all dependent child tables.
• TRACKING_STATUS — foreign key to IGS_TR_STATUS, identifying the current state of the tracking process (for example, pending, complete, or waived).
• TRACKING_TYPE — foreign key to IGS_TR_TYPE_ALL, classifying the item against a configurable tracking template.
• SOURCE_PERSON_ID and ORIGINATOR_PERSON_ID — both foreign keys to HZ_PARTIES, distinguishing the subject of the tracking item from the person or system that raised it.
• START_DT — the date the tracking process was initiated.
• TARGET_DAYS, BUSINESS_DAYS_IND, and OVERRIDE_OFFSET_CLC_IND — control due-date calculation, indicating whether elapsed days are calendar or business days and whether standard offset logic is overridden.
• COMPLETION_DUE_DT — the calculated deadline for the tracking item.
• SEQUENCE_IND and PUBLISH_IND — govern ordering and visibility of the item to end users.
• S_CREATED_IND — flags records originating from a student self-service channel.
• ORG_ID — the multi-org operating unit context, essential for any RLS-aware query.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent request attributes (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) provide auditability and batch-load traceability.

Common Use Cases and Queries

The dominant reporting pattern is a status-and-due-date workload report for admissions or registry staff. A minimal query joining the header to its status and type lookups might read:

SELECT t.TRACKING_ID, t.TRACKING_STATUS, s.DESCRIPTION, t.COMPLETION_DUE_DT FROM IGS_TR_ITEM_ALL t, IGS_TR_STATUS s WHERE t.TRACKING_STATUS = s.TRACKING_STATUS AND t.ORG_ID = :org_id AND t.COMPLETION_DUE_DT < SYSDATE;

Other frequent scenarios include auditing overdue business-day items using BUSINESS_DAYS_IND, back-tracing a tracking ID to its originating application through IGS_AD_PS_APPL_INST_ALL, and reconciling self-service submissions via S_CREATED_IND. Because many institutions refer to this structure informally as a "master tracker," searches under that phrase typically resolve to this table and its surrounding tracking hierarchy.

Related Objects

• IGS_TR_STEP — child steps belonging to each tracking item (TRACKING_ID).
• IGS_TR_ITEM_NOTE — free-text annotations attached to a tracking item.
• IGS_TR_GROUP_MEMBER — associates tracking items with tracking groups.
• IGS_TR_STATUS and IGS_TR_TYPE_ALL — status and type lookup parents.
• HZ_PARTIES — party registry for both SOURCE_PERSON_ID and ORIGINATOR_PERSON_ID.
• IGS_AD_PS_APPL_INST_ALL — application instance links via ASS_TRACKING_ID and DEFERRED_TRACKING_ID.
• IGS_AD_APLINS_ADMREQ — admissions requirements referencing TRACKING_ID.

Because the module is documented as obsolete and not implemented in current databases, teams should confirm physical presence before building production queries.