Search Results igs_pr_milestone_all
Overview
The IGS_PR_MILESTONE_ALL table is a core data object within the Oracle E-Business Suite Student System (IGS), specifically supporting the management of research student candidature. It stores the structured progression requirements, or milestones, that a research student must complete throughout their candidature. This table is fundamental for tracking a student's progress against a defined research program plan, enabling academic administration and compliance monitoring. As an ALL table, it is designed to support the Multi-Org architecture, meaning it can store data partitioned by operating unit, a critical feature for institutions with multiple campuses or administrative divisions in releases 12.1.1 and 12.2.2.
Key Information Stored
The table's primary key uniquely identifies each milestone record for a student's candidature, comprising PERSON_ID, CA_SEQUENCE_NUMBER, and SEQUENCE_NUMBER. Key columns include PERSON_ID (the student), CA_SEQUENCE_NUMBER (a unique identifier for the specific candidature instance of that student), and SEQUENCE_NUMBER (the order of the milestone). The MILESTONE_STATUS column holds a code indicating the current state (e.g., Planned, Completed, Deferred), which is validated against the IGS_PR_MS_STAT_ALL lookup table. The PRECED_SEQUENCE_NUMBER column is significant as it establishes prerequisite relationships between milestones, allowing for complex, dependent milestone paths within a single candidature.
Common Use Cases and Queries
Primary use cases include generating student progress reports, triggering notifications for upcoming or overdue milestones, and auditing candidature timelines. A common reporting query involves joining to the candidature and person tables to list milestones with their statuses for a cohort. For example:
- Tracking overdue milestones:
SELECT person_id, sequence_number, milestone_status, due_date FROM igs_pr_milestone_all WHERE milestone_status NOT IN ('COMPLETED','WAIVED') AND due_date < SYSDATE; - Listing a student's milestone plan with status descriptions:
SELECT m.*, s.description FROM igs_pr_milestone_all m, igs_pr_ms_stat_all s WHERE m.milestone_status = s.milestone_status AND m.person_id = :p_person_id AND m.ca_sequence_number = :p_ca_seq_num ORDER BY m.sequence_number;
Related Objects
The table maintains integral relationships with other entities in the Research Candidature model. Its documented foreign key relationships are as follows:
- IGS_RE_CANDIDATURE_ALL: A milestone is defined for a specific student candidature. Joined via PERSON_ID and CA_SEQUENCE_NUMBER.
- IGS_PR_MS_STAT_ALL: Provides valid values for the MILESTONE_STATUS column.
- Self-Referential Relationship: The table references itself (IGS_PR_MILESTONE_ALL) via PERSON_ID, CA_SEQUENCE_NUMBER, and PRECED_SEQUENCE_NUMBER to define prerequisite milestone dependencies within the same candidature.
This structure ensures data integrity and supports the complex, sequential nature of research degree milestones.
-
Table: IGS_PR_MILESTONE_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: This entity describes the milestones that a research student must complete during the duration of their candidature. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_PR_MS_STAT_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: This table describes the user-defined milestone statuses, which map onto one of the set of system defined values. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_RE_CANDIDATURE_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: This entity describes the candidature details of a research student. , implementation_dba_data: Not implemented in this database ,
-
View: IGS_PR_MILESTONE
12.2.2
product: IGS - Student System (Obsolete) , implementation_dba_data: Not implemented in this database ,