Search Results igs_pr_milestone_type

Overview

IGS_RE_VAL_MTY is a validation package in the Oracle E-Business Suite student systems family. Its business function is narrow and well defined by the header comment embedded in the source: it validates the milestone type notification days stored against the IGS_PR_MILESTONE_TYPE entity. This entity belongs to the Oracle Student System recruiting and admissions milestone model, where milestone types describe notable enrollment or prospecting events (such as application receipt, offer issuance, or deposit payment) and carry attributes governing how reminders about those events are scheduled.

The package exposes a single validation routine that enforces a logical dependency across three notification timing columns on a milestone type record: ntfctn_imminent_days, ntfctn_reminder_days, and ntfctn_re_reminder_days. The rule implemented is directional: a re-reminder interval cannot be populated unless the primary reminder interval has already been supplied. This prevents an inconsistent configuration in which the system would attempt to send a follow-up reminder when no first reminder is scheduled to precede it.

Key Procedures and Functions

The ETRM 12.1.1 metadata documents exactly one program unit in this package body:

• RESP_VAL_MTY_DAYS — The sole documented function. It accepts incoming reminder-day values together with an outgoing message name parameter and returns a Boolean validation result. Its purpose is to check the relationship between the reminder days and the re-reminder days supplied for a milestone type. When the primary reminder days value is null while the re-reminder days value is populated, the function returns FALSE and sets the outgoing message name to the seeded message token IGS_RE_CANT_SET_REMINDER_DAYS, allowing the calling form or API to present a meaningful error to the user. In all other combinations the function returns TRUE and clears the message name to null, indicating the values are acceptable.

The function wraps its internal block in an exception handler that delegates to the standard Oracle toolset error mechanism: it calls FND_MESSAGE.SET_NAME with the application short name IGS and the generic message IGS_GE_UNHANDLED_EXCEPTION, adds the context to the message stack via IGS_GE_MSG_STACK.ADD, and then re-raises through APP_EXCEPTION.RAISE_EXCEPTION. This pattern is characteristic of the Oracle Student System validation packages and ensures unexpected failures surface with a consistent, translatable message rather than a raw PL/SQL error.

Tables Accessed

The ETRM metadata for this package records no directly referenced tables through APPS synonyms. This is consistent with the source, which performs no SQL at all: the function operates purely on the scalar parameters passed to it. The columns named in the header comment — the imminent, reminder, and re-reminder notification day columns of IGS_PR_MILESTONE_TYPE — are read by the caller and supplied to this function as arguments, not queried here. Consequently the package is a pure business-rule checker with no database dependency of its own, which also means it can be invoked safely inside a form's validation trigger before any DML is issued against the milestone type record.

Usage Notes

The signature and the seeded error-message convention indicate that IGS_RE_VAL_MTY_DAYS is intended to be called from the Oracle Forms-based maintenance screens for milestone types, most plausibly from a WHEN-VALIDATE-ITEM or pre-insert/pre-update trigger on the reminder day fields. The caller passes the current field values, inspects the returned Boolean, and raises the form error using the message name returned in the output parameter when validation fails.

The ETRM metadata notes that this package is referenced by one other package. That reverse dependency typically represents a milestone type validation or maintenance API within the IGS_RE module that delegates its timing checks to this routine, allowing the same rule to be reused by non-form entry points such as batch loading of milestone type setup data. Because the package is owned by APPS and classified as OTHER rather than as a public API, customizations should avoid calling it directly where a supported milestone type API exists; where direct invocation is unavoidable, callers must supply the message name output parameter and be prepared to handle the Boolean FALSE result themselves, since the function does not raise the validation exception — it reports it. Under Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and requires no editioning-specific handling beyond standard APPS synonym resolution.