Search Results g_log_error

Overview

GMD_DEBUG is the Process Manufacturing (OPM) diagnostic and logging utility package owned by APPS in the Oracle E-Business Suite. It is a development and support infrastructure package rather than an application-facing business API: its purpose is to provide a standardized, configurable logging facility that Oracle Process Manufacturing modules and customer extensions can call to write trace, event, and error information during execution of concurrent programs and PL/SQL routines. The package is declared with AUTHID CURRENT_USER and carries the source header identifier GMDUDBGS.pls (revision 115.1, dated 2002/11/08), attributing original authorship to OPM Development. In the ETRM 12.2.2 registry it is classified as API classification OTHER, reflecting its role as a utility library rather than a documented integration interface.

Key Procedures and Functions

The documented interface exposes three procedures:

• LOG_INITIALIZE — Initializes the logging facility. Per the source commentary, it is intended to be called from the top-level procedure of each concurrent program so that log destination, user context, and logging mode are established before any messages are written. It accepts an optional file name argument with a default, allowing callers to override the default log file name (DEBUGLOG).
• PUT_LINE — Adds a single entry to the log. The message is qualified by a severity level drawn from the package constants: G_LOG_ERROR (5), G_LOG_EXCEPTION (4), G_LOG_EVENT (3), G_LOG_PROCEDURE (2), and G_LOG_STATEMENT (1). This is the routine of primary interest to callers searching on g_log_exception, which is the constant used to tag messages emitted when exception handlers are trapped and logged.
• DISPLAY_MESSAGES — Retrieves and presents accumulated log messages, supporting the diagnostic review of a completed or in-flight program run.

Tables Accessed

GMD_DEBUG references no application tables. Via APPS synonyms it depends on UTL_FILE, the Oracle-supplied PL/SQL file I/O package used to write log output to the filesystem location governed by the G_LOG_LOCATION package variable (default '.'), and V$PARAMETER, the dynamic performance view read to determine database initialization parameters relevant to the logging environment. Because the package is AUTHID CURRENT_USER, filesystem access is resolved against the privileges of the invoking schema, and the UTL_FILE directory or server-side path must be accessible to that session.

Usage Notes

GMD_DEBUG is a shared dependency rather than a standalone program: ETRM documentation records that it is referenced by 64 other packages, indicating broad internal use across OPM logic. The package-level state variables (G_LOG_LEVEL, G_LOG_ENABLED defaulting to 'N', G_LOG_MODE defaulting to 'OFF' with possible values OFF, SQL, and SRS, and G_LOG_USERNAME) show that logging is disabled by default and is enabled explicitly at runtime; G_LOG_MODE determines whether output is directed to the SQL*Plus session or to the concurrent manager log. Typical invocation patterns are: calling LOG_INITIALIZE once at the start of a custom or seeded concurrent program, calling PUT_LINE throughout processing with an appropriate level constant—most commonly G_LOG_EXCEPTION inside WHEN OTHERS handlers—and calling DISPLAY_MESSAGES to surface the collected output. Custom code that depends on GMD_DEBUG should treat the package as an unsupported internal utility: Oracle does not guarantee its signature across releases, and the same diagnostic outcome can generally be achieved using FND_LOG and FND_FILE in the standard EBS logging framework.