Search Results start_debug

Overview

XTR_RISK_DEBUG_PKG is a diagnostic utility package in the Oracle E-Business Suite Treasury (ETRM) module, owned by the APPS schema. Its role is to provide a structured debugging and instrumentation framework for the risk management components of ETRM, particularly the exposure, limit, and market risk calculation engines that operate under the XTR schema family. Rather than a business-facing API, this package functions as a developer and support tool: it allows PL/SQL code throughout the risk subsystem to emit trace messages, manage debug session state, and route diagnostic output to files or the concurrent program log without contaminating production data.

The package body is documented as VALID in both 12.1.1 and 12.2.2 and is classified as OTHER in the ETRM API taxonomy, confirming it is not a public integration interface but an internal instrumentation layer. It is referenced by approximately eighteen other database objects, indicating that the risk calculation packages call into it to record execution flow and diagnostic detail.

Key Procedures and Functions

• START_DEBUG — Initialises a debugging session, establishing the context and enabling subsequent trace output.
• STOP_DEBUG — Terminates the current debugging session and releases associated session state.
• DPUSH — Pushes a new debug scope or nesting level onto the internal debug stack, allowing hierarchical tracing of nested procedure calls.
• DPOP — Pops the most recent debug scope from the stack, restoring the previous level of trace context.
• START_CONC_PROG — Begins a debug session specifically for a concurrent program execution, aligning trace output with the concurrent manager environment.
• STOP_CONC_DEBUG — Ends the concurrent-program debug session and flushes any buffered diagnostic output.
• SET_FILEHANDLE — Registers the UTL_FILE handle used to write debug output, allowing the trace destination to be controlled by the caller.
• DLOG — Writes a formatted diagnostic message to the active debug target.

Additional internal helpers are present within the eleven documented units, but the procedures above form the public surface used by calling packages.

Tables Accessed

The package does not read or write transactional ETRM tables. Its documented references are to infrastructure objects: UTL_FILE for file-based output, DBMS_UTILITY and PLITBLM for stack and utility operations, and the FND profile tables FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES, which are queried to determine whether debugging is enabled and at what level for the current user or application context. It also references FND_GLOBAL, FND_LOG, and STANDARD, which supply session identifiers, the Fusion logging framework, and base PL/SQL definitions respectively.

Usage Notes

XTR_RISK_DEBUG_PKG is typically invoked indirectly. Risk calculation packages call START_DEBUG and DLOG to emit trace information during exposure and limit processing, while the concurrent-program entry points are used when running risk batch processes through the concurrent manager. Developers enable output by setting the relevant debug profile option, which the package reads at runtime through the FND profile views; trace data is then written via UTL_FILE or redirected into the concurrent program log through FND_LOG. In 12.2.2 the object remains unchanged in status, and because it is not referenced by any database object outside its callers, it can be regarded as a stable internal utility. It should not be treated as a supported public API, and any custom code depending on it does so at its own risk.