Search Results igs_en_intrmn_s

Overview

IGS_EN_WORKFLOW is an Oracle E-Business Suite package body owned by the APPS schema and classified under the OTHER API category. It belongs to the Student System (IGS) product family, specifically the Enrollment (IGS_EN) module, and provides the workflow notification and event-raising infrastructure used throughout the student enrollment lifecycle. In Oracle EBS 12.1.1 and 12.2.2, this package serves as the bridge between enrollment business transactions and the Oracle Workflow engine (WF_ENGINE, WF_EVENT, WF_DIRECTORY). When significant enrollment events occur — a status change, an intermission request, a program transfer, a program discontinuation, a change to a program offering option, or a student placement — the package composes the appropriate message payload, resolves recipients from person and user-role data, and dispatches the workflow event or notification. It also supports the student-initiated petition flows, informing students of instructional actions and informing instructors of student petitions.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions, organized around three functional areas:

• Event raisers: INTERMISSION_EVENT, PROGDISCONT_EVENT, PROGTRANS_EVENT, PROGOFROPT_EVENT, STUDENT_PLACEMENT_EVENT, RAISE_WITHDRAW_PERM_EVT and RAISE_SPI_RCOND_EVENT each raise a workflow event corresponding to a specific enrollment transaction (intermission, program discontinuation, program transfer, program offering option change, student placement, withdrawal permission, and SPI reconciliation condition respectively).
• Notification dispatchers: INTERMISSION_NOT, PROGTRANS_NOT, PROGOFROPT_NOT, PROGDISCONT_NOT and ENR_NOTIFICATION generate and send the notification messages tied to the above events, resolving recipients and assembling message content.
• Interaction procedures: SUA_STATUS_CHANGE_MAIL, INFORM_STDNT_INSTRUCT_ACTION and INFORM_INSTRUCT_STDNT_PETITION handle status-change mailings and the bidirectional communication between students and instructors regarding instructional actions and petitions.

Tables Accessed

The package reads and writes enrollment and reference data required to build notification content and identify recipients. The core transactional tables are IGS_EN_INTRMN_S (intermission records), IGS_EN_PRGTRN_S (program transfers), IGS_EN_PRGDSC_S (program discontinuations), IGS_EN_PROFOP_S (program offering option changes), IGS_EN_STUDENT_PLACEMENT_S (student placements), IGS_EN_WITHDRAW_PERM_S (withdrawal permissions), IGS_EN_STUD_SPLPERM_REQ_S (student special permission requests), IGS_EN_INTM_RCOND_S (intermission reconciliation conditions), IGS_EN_INST_ACTION_S (instructional actions), and IGS_EN_STATUS_MAIL_REQ_S (status mail requests). Reference and type lookups include IGS_EN_INTM_TYPES, IGS_CA_TYPE, IGS_EN_DCNT_REASONCD, IGS_PS_VER, IGS_PS_UNIT_OFR_OPT_ALL, and IGS_PS_USEC_TCH_RESP. Person and party data is resolved through IGS_PE_PERSON, IGS_PE_PERSON_BASE_V, HZ_PARTIES, FND_USER, and WF_LOCAL_USER_ROLES, while IGS_RE_CANDIDATURE, IGS_RE_SPRVSR, and IGS_RE_THESIS support research candidature notifications. Integration staging uses IGS_AS_ORD_ITM_INT and the load view IGS_CA_TEACH_TO_LOAD_V.

Usage Notes

IGS_EN_WORKFLOW is not referenced by any database object directly, but is referenced by seven other packages, indicating it functions as a utility layer invoked by higher-level enrollment APIs and concurrent programs rather than by forms triggers. Typical invocation occurs when an enrollment business process completes and a notification obligation exists: the calling package raises the relevant *_EVENT procedure, which in turn prepares and submits the workflow notification. The package depends on FND_API, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, FND_LOOKUPS and IGS_GE_MSG_STACK for error handling, message stacking, and profile resolution, and on WF_ENGINE, WF_EVENT, WF_DIRECTORY, WF_PARAMETER_LIST_T and WF_EVENT_T for workflow dispatch. Customizations should avoid modifying this package body; instead, extensions should subscribe to the raised workflow events. All database access is through APPS synonyms, so the package must be executed under a responsibility whose FND profile options resolve the correct enrollment and workflow configuration.