Search Results ntfctn_imminent_days

Overview

IGS.IGS_PR_MILESTONE_TYP is a validation and configuration table within the Oracle EBS Student Systems / Research Tracking (IGS) product family. It defines the set of institution-specific milestone types that may be recorded against a research candidate, such as a postgraduate research student or a thesis-track candidate. Each row establishes a milestone type, its descriptive text, and the notification-timing thresholds that the application uses to drive alerts, reminders, and repeat-reminder notices.

Functionally, the table acts as a reference/lookup, supplying the permissible values that other research-tracking records consume when milestones are assigned to candidates. Because the table carries configurable business rules in the form of notification interval columns, it is more than a static code list; changes to a row alter the automated notification behavior for every milestone of that type.

The documented Data Vault classification for this object is standalone (mined from its foreign-key structure). Under a Data Vault modeling suggestion, this would be treated as a reference hub or small reference satellite: MILESTONE_TYPE serves as the business key, and the descriptive and notification-timing attributes behave as dependent satellite data. The absence of outbound foreign keys reinforces its role as an independent reference entity.

Key Information Stored

The table comprises 11 documented columns. The most significant are:

• MILESTONE_TYPE (VARCHAR2(10)) — the primary key and the business-key candidate, uniquely enforced by the unique index IGS_PR_MILESTONE_TYP_U1. It holds the institution-defined short code for the milestone category.
• DESCRIPTION (VARCHAR2(60)) — the plain-language explanation of the milestone type, used for display in forms and reports.
• NTFCTN_IMMINENT_DAYS (NUMBER) — the number of days prior to a milestone due date of this type that triggers an imminent-milestone notification. This is the column associated with the user search term.
• NTFCTN_REMINDER_DAYS (NUMBER) — the number of days after the due date that triggers a reminder notification.
• NTFCTN_RE_REMINDER_DAYS (NUMBER) — the interval, after a prior reminder, at which a further reminder is issued.
• CLOSED_IND (VARCHAR2) — open/closed flag; when set to closed, the milestone type is barred from being applied to new or modified records elsewhere in the system.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who audit columns that record row provenance and change history.

The single-column primary key (IGS_PR_MILESTONE_TYP_PK) coincides with the unique index, so no separate surrogate sequence key is documented. The table resides in the APPS_TS_TX_DATA tablespace with the unique index in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical scenarios include: reviewing active milestone types and their notification windows; auditing which types have been retired via CLOSED_IND; and profiling notification timing policy across the institution.

A standard lookup query:

SELECT MILESTONE_TYPE, DESCRIPTION,
       NTFCTN_IMMINENT_DAYS, NTFCTN_REMINDER_DAYS,
       NTFCTN_RE_REMINDER_DAYS, CLOSED_IND
FROM   IGS.IGS_PR_MILESTONE_TYP
WHERE  CLOSED_IND = 'N'
ORDER BY MILESTONE_TYPE;

To target the searched attribute specifically — the advance-notice window — a reporting query such as SELECT DESCRIPTION, NTFCTN_IMMINENT_DAYS FROM IGS.IGS_PR_MILESTONE_TYP WHERE NTFCTN_IMMINENT_DAYS IS NOT NULL isolates types that generate imminent notifications. Because the notification columns are nullable NUMBERs, queries should account for types without timing configured. The table is read-mostly; maintenance is performed through the standard Oracle Forms-based setup UI rather than direct DML.

Related Objects

The documented relationship data classifies the table as standalone, meaning no foreign keys are mined from it. Its principal dependencies are therefore inbound: other IGS research-tracking entities reference MILESTONE_TYPE as a parent key.

• IGS_PR_MILESTONES (or the equivalent candidate-milestone assignment entity) — references MILESTONE_TYPE; the primary consumer of this reference data.
• IGS_PR_CANDIDATE_MILESTONES — likely join between research candidates and milestone types, joined on MILESTONE_TYPE.
• IGS_PR_MILESTONE_TYPES_VL / _V — views exposing the base table for form and report use.
• IGS_PR_MILESTONE_TYP_U1 — the unique index enforcing the business key MILESTONE_TYPE.
• IGS_PR_MILESTONE_TYP_PK — the primary key constraint on MILESTONE_TYPE.
• FND_LOOKUPS / IGS lookup registration — optional code registration supporting the milestone-type value set.
• Notification/workflow objects (e.g., IGS research notification workflows) — consumed when NTFCTN_IMMINENT_DAYS, NTFCTN_REMINDER_DAYS, and NTFCTN_RE_REMINDER_DAYS drive scheduled alerts.

Joins should be performed on the MILESTONE_TYPE column, the sole documented key relationship, as no other FK-bearing columns are defined in the ETRM metadata.