Search Results debug_level_none

Overview

EAM_DEBUG is the diagnostic and error-handling utility package for the Oracle Enterprise Asset Management (EAM) product family in Oracle E-Business Suite. It is owned by APPS and classified as an "OTHER" API. Rather than performing a business transaction itself, the package supplies a common instrumentation layer that other EAM packages call to emit debug messages, record error context, manage user locks, and write diagnostic output to concurrent manager log and output files.

The package defines a small numeric hierarchy of debug levels that govern how much information is captured at run time. The level constants include DEBUG_LEVEL_EXCEPTION (a constant used for reporting very important messages), DEBUG_LEVEL_NONE, DEBUG_LEVEL_BASIC, and DEBUG_LEVEL_TIMING. A module-level variable named debug_level holds the current threshold, while debug_flag, number_of_debug_messages, and an associative array of message strings, debug_message, retain state for the duration of a session. The header also initializes standard WHO columns (last updated by, created by, login, concurrent request, program application, and program identifiers) from FND_GLOBAL at package instantiation, so any logging automatically carries session context. A separate G_Err_Stack variable and its table counterpart provide a structured error stack for capturing and re-raising failures.

Key Procedures and Functions

• INITIALIZE — establishes package state at the start of a run.
• ENABLE_DEBUG / DISABLE_DEBUG — turn debug collection on or off.
• SET_DEBUG_LEVEL — sets the threshold that determines which messages are retained; this is the routine most relevant to the DEBUG_LEVEL_EXCEPTION constant.
• DEBUG — the primary instrumentation call, emitting a message at a specified level.
• GET_MESSAGE and NO_OF_DEBUG_MESSAGES — retrieve a buffered message and report how many messages were captured.
• SET_USER_LOCK_MODE, ACQUIRE_USER_LOCK, RELEASE_USER_LOCK — control and apply user-level locking.
• SET_PROCESS — identifies the calling process so output is routed correctly.
• WRITE_FILE and WRITE_LOG — write diagnostic or log content to the output destination.
• INIT_ERR_STACK, SET_ERR_STACK, RESET_ERR_STACK — manage the error stack.
• RAISE_ERROR — surface a captured error.
• LOG_MESSAGE — record a message in the log.
• SET_CURR_FUNCTION / RESET_CURR_FUNCTION — bracket the currently executing routine for contextual logging.

Tables Accessed

No application data tables are referenced. The package operates against four underlying objects exposed through APPS synonyms: DBMS_LOCK for user lock acquisition and release, DUAL for simple value selection, PLITBLM for binary-integer-indexed associative array support, and UTL_FILE for writing to the file system.

Usage Notes

EAM_DEBUG is invoked from EAM forms, concurrent programs, and custom code, and is referenced by four other packages. The G_Process default of 'IGNORE' and related comments indicate that many forms call WRITE_FILE indirectly through other APIs without invoking SET_PROCESS first, so the default behavior was deliberately relaxed rather than modifying every calling form. Developers debugging EAM processes typically call ENABLE_DEBUG and SET_DEBUG_LEVEL, run the transaction, then inspect output written through FND_FILE.LOG or UTL_FILE. Because the package is AUTHID CURRENT_USER and depends on the APPS synonym layer, it is available to any EAM module running under APPS.