Search Results g_log_username

Overview

GMD_DEBUG is a diagnostic and logging utility package in the Oracle E-Business Suite Process Manufacturing (GMD) schema, owned by APPS and validated in both release 12.1.1 and 12.2.2. Its business function is to provide Process Manufacturing modules with a centralized mechanism for initializing a debug session, writing trace and diagnostic output to log destinations, and surfacing accumulated error or informational messages to the end user. Rather than each GMD program implementing its own ad hoc logging, GMD_DEBUG consolidates this behavior and delegates the underlying mechanics to the Oracle Application Object Library (FND) logging, file, message, and profile infrastructure. The package body is classified as OTHER in the ETRM API classification, indicating that it is an internal utility rather than a public integration API, although it is heavily consumed across the GMD codebase.

Key Procedures and Functions

The documented package body exposes three procedures:

• LOG_INITIALIZE — Establishes the debug session. It prepares the logging context, typically reading FND profile options and environment settings through FND_PROFILE and V$PARAMETER to determine whether debugging is enabled and where output should be directed. Downstream calls to the remaining routines depend on this initialization having run.
• PUT_LINE — Writes a line of diagnostic text to the active log destination. This is the workhorse routine invoked throughout Process Manufacturing programs to emit trace messages during execution, allowing developers and support analysts to follow program flow and capture variable state.
• DISPLAY_MESSAGES — Retrieves and presents messages accumulated in the FND message stack, using FND_MSG_PUB semantics, so that errors and warnings raised during processing are shown to the user rather than being silently discarded.

Because the ETRM metadata does not publish parameter signatures, callers should reference the deployed package specification for exact argument lists.

Tables Accessed

The package does not read or write application business tables. Its documented table references via APPS synonyms are UTL_FILE and V$PARAMETER. V$PARAMETER is queried to inspect database initialization parameters, commonly the user-dump or background-dump destination directories, so that file-based log output is written to a valid location resolvable by the database server. UTL_FILE, the PL/SQL file I/O package, is used to open, write, and close the physical log files themselves. Message text is handled through FND_MSG_PUB rather than a persistent table, and output may alternatively be routed to FND_FILE, which is the standard concurrent program log and output file mechanism.

Usage Notes

GMD_DEBUG is an internal dependency rather than a standalone executable. It is not referenced by any database object in the reverse direction, but it is referenced by 64 other packages, confirming its role as a shared service consumed by the broader Process Manufacturing suite. Typical invocation patterns include:

• Concurrent programs and PL/SQL batch routines in GMD that call LOG_INITIALIZE at the start of processing, PUT_LINE at checkpoints, and DISPLAY_MESSAGES before completion.
• Oracle Forms-based Process Manufacturing windows that require user-visible error feedback through the FND message stack.
• Custom extensions and diagnostics that piggyback on the package to obtain consistent logging behavior aligned with FND_LOG and FND_PROFILE settings.

Because logging is profile-driven, output is produced only when the relevant FND debug and logging profiles are enabled; otherwise the routines execute with minimal overhead. Developers integrating with GMD_DEBUG should avoid altering its behavior, as changes cascade to all 64 dependent packages.