Search Results igs_re_thesis_s

Overview

IGS_RE_WORKFLOW is an Oracle EBS Student Systems (formerly Oracle Student System / iGS) package that provides the workflow notification and event-raising layer for research and thesis administration. It resides in the APPS schema and is documented as VALID in both 12.1.1 and 12.2.2 environments. The package name combines the "IGS_RE" (Research) product prefix with "WORKFLOW," signalling its role as the integration point between research records — candidatures, theses, thesis panels, supervision, milestones and results — and the Oracle Workflow engine (WF_ENGINE, WF_EVENT, WF_NOTIFICATION). Its responsibility is to detect business events on research entities, resolve the correct recipients and notification content through FND messaging and lookup services, and dispatch the appropriate templated notifications or workflow events. The object is therefore best understood as a research-domain event publisher rather than a transactional DML API; it consumes data maintained by other research packages and converts it into workflow activity.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, which fall into three functional families:

• Event raisers: RETOPIC_EVENT, RETHESIS_EVENT, SUPERVISION_EVENT, OVERDUESUB_EVENT, MILESTONE_EVENT, THESIS_EXAM_EVENT, THESIS_RESULT_EVENT and CONFIRM_REG_EVENT. Each raises a workflow or business event corresponding to a research lifecycle occurrence — a topic change on a research topic, a thesis submission or amendment, a change to supervision arrangements, an overdue submission, a milestone attainment, thesis examination progress, thesis results, and research registration confirmation.
• Notification senders: RETOPIC_NOT, THESIS_NOT, SUPERVISION_NOT, OVERDUESUB_NOT, CONFIRM_REG_NOT and MILSTN_NOTIFY_NOT. These complements to the event raisers perform the actual notification dispatch, assembling message content and recipient lists before calling Workflow notification APIs.
• Supporting utilities: MILSTN_NOTIFY_PRCS, the milestone notification driver that coordinates milestone-related notification processing, and CREATE_ADHOC_ROLE, which creates an ad hoc workflow role for notification routing where a persistent role is not already defined.

Tables Accessed

Table access is primarily read-oriented, drawing on the research entity tables and Oracle Workflow/FND infrastructure:

• IGS_RE_CANDIDATURE, IGS_RE_THESIS_S, IGS_RE_THS_PNL_MBR, IGS_RE_SPRVSR, IGS_RE_EXMSUB_S and IGS_RE_RETOPC_S supply thesis, panel membership, supervisor, examination submission and research topic data.
• IGS_RE_MILSTN_S, IGS_PR_MILESTONE, IGS_PR_MILESTONE_TYP and IGS_RE_DFLT_MS_SET resolve milestone instances, their types and default milestone sets for a candidate.
• IGS_RE_MILNOT_S, IGS_RE_RESUPD_S, IGS_RE_REGCFM_S and IGS_RE_SPRVSN_S hold milestone notification, result update, registration confirmation and supervision status rows used to determine whether a notification is due.
• IGS_EN_OVRSUB_S, IGS_EN_STDNT_PS_ATT, IGS_PE_PERSON, IGS_PE_PERSON_BASE_V, IGS_PS_VER and IGS_AS_ORD_ITM_INT provide enrolment, person, programme version and order-item context.
• FND_USER, FND_NEW_MESSAGES, FND_LOOKUPS, FND_MESSAGE, FND_PROFILE and FND_GLOBAL supply recipient identity, message text, lookup values, profile option settings and session context.
• Workflow infrastructure tables and APIs — WF_ENGINE, WF_DIRECTORY, WF_EVENT, WF_EVENT_T, WF_LOCAL_USER_ROLES and WF_PARAMETER_LIST_T — are used to raise events and build notification routing.

Usage Notes

IGS_RE_WORKFLOW is not referenced by any database object, meaning it is invoked from outside the PL/SQL dependency chain — typically from concurrent programs, forms-based actions, or database triggers in the research module that call the event-raisers when a research record changes. Several of its procedures are designed to be run by scheduled concurrent requests (particularly the milestone notification processing and overdue-submission notifications) so that time-based notifications are generated without user intervention. The package is referenced by seven other packages, indicating that other research components consume its create-ad-hoc-role and notification helpers. Because it depends on Oracle Workflow and FND messaging, the Workflow background engine must be running and notification mailers configured for messages to be delivered. Customisations should avoid modifying the package directly; instead, site-specific notification routing is normally achieved through Workflow notification definitions and attribute settings. Note that the term "igs_re_thesis_s" associated with the search corresponds to the IGS_RE_THESIS_S table dependency rather than to any procedure within this package.