Search Results stop_conc_debug




Overview
Explore in AI Chat

Overview

XTR_RISK_DEBUG_PKG is a diagnostic utility package owned by the APPS schema within the Oracle E-Business Suite financials family, specifically the Treasury (XTR) module. Its principal business function is to provide a controlled instrumentation and tracing framework for the risk management processing logic executed by Treasury components. Rather than a functional API that alters business data, this package serves as a debugging harness that permits developers and support analysts to capture execution flow, timing information, and call stack detail while risk-related batch and concurrent processing runs.

The package is classified as OTHER in the ETRM metadata, indicating that it is not a published integration API but an internal support object. It is referenced by eighteen other packages within the application, which confirms its role as a shared diagnostic layer used across the Treasury codebase. The declared types within the package — including DebugLevels_table_type, TimeType_rec_type, TimeStack_table_type, and CallStack_table_type — support the collection of per-marker timing, invocation counts, and cumulative elapsed time across nested calls. Global state variables, such as the time stack, call stack, debug level table, and the boolean debug flags, persist for the duration of a session or concurrent request.

Key Procedures and Functions

The package exposes eleven procedures and functions. The documented entry points include:

  • START_DEBUG — Initializes a debug session, optionally accepting a path and file name to direct trace output to a file via the package file handle.
  • STOP_DEBUG — Closes the active debug session and releases associated resources.
  • START_CONC_PROG — Signals to the debug package that a concurrent program has begun, enabling concurrent-aware tracing.
  • STOP_CONC_DEBUG — Terminates concurrent program debug tracing, corresponding to the search term "stop_conc_debug" and pairing with the start of concurrent program instrumentation.
  • SET_FILEHANDLE — Assigns or manages the UTL_FILE handle used to write trace output.
  • DLOG — Writes a diagnostic log entry, the primary mechanism by which callers emit trace messages.
  • DPUSH — Pushes a named call onto the internal call stack, optionally tagged with a module and log level.
  • DPOP — Pops a call from the call stack, optionally accepting context, module, and log level arguments.

These procedures are not parameterized here beyond their documented signatures; developers must consult the package specification for exact argument lists.

Tables Accessed

The package accesses several underlying objects through APPS synonyms. UTL_FILE is used to read and write operating system files for trace output. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES are queried to determine profile-driven debug settings and logging thresholds. DBMS_UTILITY provides utility functions, commonly for stack and call information. PLITBLM is referenced for PL/SQL internal table support.

Usage Notes

This package is typically invoked from PL/SQL code within Treasury risk processing, from concurrent programs that require trace capture, and from support diagnostics performed by developers. It is not intended for end-user forms directly. When diagnosing risk batch failures during a 12.1.1 or 12.2.2 implementation, developers enable START_DEBUG or START_CONC_PROG, allow the process to execute, then call STOP_CONC_DEBUG or STOP_DEBUG to close the trace and release the UTL_FILE handle.