Search Results delete_msg

Overview

IGS_GE_MSG_STACK is a general-purpose utility package in the APPS schema belonging to the Oracle Student System (formerly Oracle iLearning / Student Information) family of products. Its name reflects its core responsibility: maintaining a message stack used during PL/SQL program execution. Rather than allowing message state to be lost when a cursor or procedure exits, IGS_GE_MSG_STACK provides a centralized in-memory repository to append, accumulate, and later retrieve diagnostic and validation messages. The package is classified under ETRM as an "OTHER" API, indicating it is a supporting infrastructure component rather than a business rule engine. It is heavily reused — the ETRM documentation records that 1,772 other packages reference it — making it one of the most foundational service packages in the IGS schema. Its dependency list confirms this role: it relies on FND_MESSAGE, FND_MSG_PUB, FND_FILE, and FND_PROFILE, meaning it integrates directly with the Oracle E-Business Suite message dictionary and the Applications message retrieval framework.

Key Procedures and Functions

Six documented program units comprise the public interface:

• INITIALIZE — Clears or resets the internal message stack, preparing it for a new unit of work. Typically called at the start of a business process or concurrent program.
• COUNT_MSG — Returns the number of messages currently held on the stack, allowing callers to branch on whether warnings or errors have accumulated.
• ADD — Pushes a new message onto the stack, accepting message text or a message name for dictionary lookup.
• DELETE_MSG — Removes a specific message (or messages) from the stack, useful for filtering warnings before logging.
• GET — Retrieves messages from the stack for display, logging, or propagation to the calling application.
• CONC_EXCEPTION_HNDL — A concurrent-program exception handler that flushes stack contents to the concurrent manager log or output file via FND_FILE, ensuring errors are visible in the request log.

Tables Accessed

The package is not documented as reading or writing any application tables directly. Its state is held in memory, and its integration points are the FND message dictionary APIs (FND_MESSAGE, FND_MSG_PUB) and the profile options facility (FND_PROFILE). Message output during concurrent execution is directed to the log and output files through FND_FILE rather than to a permanent table.

Usage Notes

IGS_GE_MSG_STACK is invoked almost exclusively from within other PL/SQL packages and concurrent program logic. A calling program typically calls INITIALIZE at entry, ADDs messages as validation or processing steps execute, checks COUNT_MSG to decide whether to proceed, and finally calls GET or CONC_EXCEPTION_HNDL to surface results. Because it is referenced by over 1,700 packages, modifications to its interface carry wide-reaching impact and should be treated as a shared infrastructure change subject to full regression testing across the Student System modules in EBS 12.1.1 and 12.2.2.