Search Results igs_pr_milestone_typ

Overview

IGS_PR_MILESTONE_TYP is a reference (lookup) table in the IGS — Student System product of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It describes the types of milestones that can be recorded against a research candidate, such as supervisory meetings, progress reviews, annual reports, or thesis submission checkpoints. Rather than storing milestone events themselves, the table defines the catalogue of milestone types available to the institution and the notification behavior associated with each type.

The table is owned by the IGS schema and carries 11 documented columns in the 12.1.1 physical schema. Its primary key constraint, IGS_PR_MILESTONE_TYP_PK, is defined on the single column MILESTONE_TYPE. A unique index, IGS_PR_MILESTONE_TYP_U1, is also defined on MILESTONE_TYPE, which means the business key and the primary key are coincident and no separate surrogate key is documented. Under the heuristic Data Vault classification mined from the FK structure, this object is assessed as standalone; in Data Vault modeling terms it is best treated as a hub-style reference set (a hub on MILESTONE_TYPE) with no documented dependent link relationships.

Key Information Stored

The most significant columns documented for this table are:

• MILESTONE_TYPE — the primary key and unique business key; a short code or identifier uniquely naming each milestone category.
• DESCRIPTION — the descriptive label for the milestone type as presented to users and on reports.
• NTFCTN_IMMINENT_DAYS — the number of days before a milestone due date at which an imminent-due notification is triggered.
• NTFCTN_REMINDER_DAYS — the offset in days used for the standard reminder notification.
• NTFCTN_RE_REMINDER_DAYS — the offset used for a repeat or follow-up reminder when the milestone remains outstanding.
• CLOSED_IND — an indicator showing whether the milestone type is closed to new usage; a closed type remains queryable for historical milestones but should not be selected for new records.
• CREATED_BY, CREATION_DATE — standard Oracle EBS audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent change, its timestamp, and the login session of the updating user.

The notification columns are the functionally distinctive element of this reference table: they allow per-type scheduling of reminders without embedding timing logic in application code. The four WHO columns follow the standard Oracle Applications audit convention and should be excluded from most reporting projections.

Common Use Cases and Queries

Typical usage includes validating a milestone type before recording a research candidate milestone, populating a milestone type list of values, driving reminder notifications in a scheduled concurrent program, identifying inactive types, and producing reference reports.

• List all active milestone types: SELECT milestone_type, description FROM igs_pr_milestone_typ WHERE closed_ind = 'N';
• Resolve a description: SELECT description FROM igs_pr_milestone_typ WHERE milestone_type = :p_type;
• Notification scheduling review: SELECT milestone_type, ntfctn_imminent_days, ntfctn_reminder_days, ntfctn_re_reminder_days FROM igs_pr_milestone_typ;
• Audit recent maintenance: SELECT milestone_type, last_updated_by, last_update_date FROM igs_pr_milestone_typ WHERE last_update_date >= :since;

The table is small and highly cached; joins against milestone transaction tables are inexpensive and best performed on the MILESTONE_TYPE column.

Related Objects

The documented relationship data classifies this object as standalone, meaning no foreign key dependencies were mined from the schema itself. It nevertheless participates as the referenced parent of the milestone definition and milestone event tables in the research candidate area of the IGS product, which join on MILESTONE_TYPE. Reports and list-of-values definitions in the Student System research pages read from this table to present and validate milestone types, and the notification concurrent processes consume the three NTFCTN_* columns. The primary key constraint IGS_PR_MILESTONE_TYP_PK and unique index IGS_PR_MILESTONE_TYP_U1 together enforce uniqueness of MILESTONE_TYPE across both the 12.1.1 and 12.2.2 schemas. Any custom extension should preserve these constraints, because dependent milestone records will be orphaned if a type is deleted while still in use; the CLOSED_IND column exists to retire a type without breaking referential history.