Search Results g_debug_count

Overview

ASO_DEBUG_PUB is a public PL/SQL package in the APPS schema that provides a shared debugging and tracing facility for the Oracle E-Business Suite Order Capture / Sales Order (ASO) modules and adjacent Order Entry (OE) code. Its central role is to let developers and support engineers switch diagnostic logging on or off at runtime without modifying or recompiling the calling code, and to capture that output either to a server-side file or to an in-memory buffer for later dump. In EBS 12.1.1 and 12.2.2 the package is classified as a PUB (public) API, meaning its interface is intended to be callable from other application code rather than being a private implementation detail. This is reinforced by the metadata showing the package is referenced by 95 other packages, making it one of the more widely reused diagnostic utilities in the ASO/OE stack. Its header comment indicates a long-lived lineage, with the current file revision dated 2009, and it wraps much of its file and buffer behavior around the parallel OE_DEBUG_PUB package, mirroring state such as G_DEBUG_MODE, G_FILE, G_FILE_PTR, and the debug buffer table between the two packages.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. SET_DEBUG_MODE is the primary entry point and the term most frequently searched by developers; it accepts a mode indicator (for example a value of FILE) and configures the package's global debug state accordingly, returning a value that identifies the active output target such as the generated debug file path. When file mode is selected and no file is yet open it allocates a name from the debug file sequence, opens the file through UTL_FILE, and propagates the handle and mode to OE_DEBUG_PUB. INITIALIZE resets the in-memory debug buffer, counters, and index values in both ASO_DEBUG_PUB and OE_DEBUG_PUB and synchronizes the directory and file globals. DEBUG_ON and DEBUG_OFF toggle the global debug flags, with DEBUG_ON also forcing the OE_DEBUG_PUB flag on to keep the two packages consistent. ISDEBUGON and ISDEBUGON-style checks return the current debug state, while SETDEBUGLEVEL sets the verbosity threshold.

• SET_DEBUG_MODE — selects and configures the debug output mode and returns the active target.
• INITIALIZE — clears and resets debug buffers, counters, and indices.
• DEBUG_ON / DEBUG_OFF — enable or disable debug capture globally.
• ISDEBUGON — reports whether debugging is currently active.
• SETDEBUGLEVEL — adjusts the debug verbosity level.
• ADD — appends a message to the in-memory debug buffer.
• COUNTDEBUG — returns the number of buffered debug entries.
• GETFIRST / GETNEXT / GETNEXTBUFFER — iterate through buffered messages.
• RESETINDEX — resets the read cursor for buffer traversal.
• DUMPDEBUG — writes buffered messages to the configured output.

Tables Accessed

The package relies on the sequence ASO_DEBUG_FILE_S to allocate a unique debug file number, querying it through DUAL when a new file name is needed. Output is written to the server file system via the UTL_FILE built-in package, using a directory and file name recorded in the G_DIR and G_FILE globals. PLITBLM appears in the referenced objects, reflecting the use of an associative array / index-by table type (commonly PL/SQL table of VARCHAR2 index by BINARY_INTEGER) for the in-memory debug buffer used by ADD, GETFIRST, GETNEXT, GETNEXTBUFFER, COUNTDEBUG, and RESETINDEX.

Usage Notes

ASO_DEBUG_PUB is typically invoked from within ASO and OE PL/SQL APIs, concurrent programs, and forms-based code when targeted diagnostics are required. Because it is a public package referenced by many dependents, SET_DEBUG_MODE is generally called at the start of a debugging session to establish the output destination and level, and DEBUG_OFF or RESETINDEX are used to conclude or restart a trace. Its tight coupling with OE_DEBUG_PUB means callers should expect debug state to be shared across both packages.