Search Results debug_unexpected_msg

Overview

IGI_IAC_DEBUG_PKG is a diagnostic and FND logging utility package owned by APPS within the Oracle E-Business Suite environment. It belongs to the IGI (Internal Controls Manager / IAC) product family and is classified as an API of type OTHER. Its principal business function is to provide a centralized, reusable mechanism for tracing program execution and recording runtime diagnostics from within PL/SQL code across the EBS instance. The package supports two distinct logging channels: a legacy, file-oriented debug facility that writes to a temporary file, log file, or output file, and the Oracle Application Object Library FND_LOG framework, which writes structured log entries to the standard EBS logging repository.

The source header (igiiades.pls 120.3.12000000.1 2007/08/01) indicates the package has been stable for an extended period, and the documented dependency footprint — 64 other packages referencing it — confirms its role as a shared infrastructure component rather than an application-specific routine. The documented metadata classifies the package under ETRM 12.2.2, and the code is equally applicable to EBS 12.1.1.

Key Procedures and Functions

The package exposes six documented procedures, summarized below by purpose.

• DEBUG_ON — Enables the custom debug facility for a specified calling function, activating tracing for the supplied entry point.
• DEBUG_OFF — Disables the debug facility, terminating the custom trace.
• DEBUG — Writes a debug message; the procedure accepts a debug type indicator and a debug message, and directs output to the temporary, log, or output file as configured.
• DEBUG_UNEXPECTED_MSG — FND logging procedure invoked from the WHEN OTHERS THEN (Unexpected) exception section. It logs the seeded message IGI_LOGGING_UNEXP_ERROR when no specific message is available, ensuring that an unexpected exception is never silently discarded.
• DEBUG_OTHER_MSG — FND logging procedure used to log messages in all cases other than the unexpected-exception scenario. It accepts a level and a fully qualified path, and supports removal of stack frames from the reported context.
• DEBUG_OTHER_STRING — FND logging procedure for writing hard-coded literal string messages to the log.

No parameter lists are reproduced here beyond those documented in the source metadata.

Tables Accessed

The only documented database reference is the APPS synonym for V$PARAMETER. This dynamic performance view exposes current initialization parameter values and is typically consulted to determine whether the database environment is configured to support the debug or logging operations the package performs. The package does not write to any application data table; diagnostics are directed to the file system or to the FND log repository rather than to permanent schema objects.

Usage Notes

IGI_IAC_DEBUG_PKG is designed to be called from within other PL/SQL packages and program units rather than directly by end users. The most common invocation pattern is a call to DEBUG_UNEXPECTED_MSG from a WHEN OTHERS handler, and DEBUG_OTHER_MSG or DEBUG_OTHER_STRING from ordinary processing branches where trace information is required. Callers that use the legacy facility must first invoke DEBUG_ON to activate tracing and DEBUG_OFF to stop it; FND_LOG calls rely on the standard profile options (FND: Debug Log Enabled and related settings) to determine whether output is actually written.

Because 64 packages reference this utility, enabling debug mode can generate substantial log volume and impose measurable overhead; the facility should therefore be activated only during focused troubleshooting or diagnostics, and disabled immediately afterward. The package is not exposed through a form or concurrent program interface — it functions purely as a developer-facing logging aid for the IGI/IAC application code base.