Search Results igs_pr_ms_stat_all
Overview
The IGS_PR_MS_STAT_ALL table is a foundational data structure within the Oracle E-Business Suite (EBS) Student System module, specifically designed for managing academic progress. Its primary role is to serve as a reference table for milestone statuses. It enables institutions to define their own custom status codes (e.g., "Pending Review," "Completed," "On Hold") that map to a set of underlying system-defined values, providing flexibility in tracking the lifecycle of academic milestones. This table is critical for enforcing data integrity, as it is referenced by core transactional tables. Notably, the provided ETRM metadata explicitly states this table is part of the "Obsolete" Student System and was "Not implemented in this database," indicating it may represent a legacy data model from an earlier version or a specific implementation footprint.
Key Information Stored
The table's central purpose is to define valid milestone status codes and their mappings. While the full column list is not detailed in the provided excerpt, the documented primary key confirms the existence of a MILESTONE_STATUS column. This column stores the unique user-defined status code. Based on its description, the table likely contains additional columns to describe the status (e.g., a DESCRIPTION field) and to manage the mapping to the internal system status, controlling workflow behavior and reporting logic. The '_ALL' suffix in the table name is a standard EBS convention indicating the table supports multi-organization data access (MOAC) through a column such as ORG_ID.
Common Use Cases and Queries
The primary use case is the maintenance and validation of milestone statuses within academic progress tracking. Administrators would use this table to configure the set of allowable statuses. Common operational and reporting queries would involve joining this table to transactional data to translate status codes into meaningful descriptions. A fundamental query pattern is retrieving all defined statuses or validating a status code before creating a new milestone record.
- Listing all active user-defined milestone statuses:
SELECT milestone_status, description FROM igs_pr_ms_stat_all WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate); - Joining to retrieve milestone data with descriptive status:
SELECT m.milestone_code, s.description AS status_desc FROM igs_pr_milestone_all m, igs_pr_ms_stat_all s WHERE m.milestone_status = s.milestone_status;
Related Objects
The table maintains a direct foreign key relationship with a core transactional table, as documented in the ETRM metadata. This relationship is essential for ensuring that only valid, predefined statuses are applied to student milestones.
- IGS_PR_MILESTONE_ALL: This is the primary table that references IGS_PR_MS_STAT_ALL. The foreign key is defined on the column IGS_PR_MILESTONE_ALL.MILESTONE_STATUS, which references IGS_PR_MS_STAT_ALL.MILESTONE_STATUS. This enforces referential integrity, meaning every status recorded on a milestone must exist in the status reference table.
-
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_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 ,
-
View: IGS_PR_MS_STAT
12.2.2
product: IGS - Student System (Obsolete) , implementation_dba_data: Not implemented in this database ,