Search Results debug_begin

Overview

PO_WF_DEBUG_PKG is an Oracle E-Business Suite diagnostics package owned by APPS that provides a structured tracing facility for Oracle Purchasing workflow activity. Its stated purpose, per the package header, is to track the progress of all functions in the workflow as they are invoked by the workflow process. Specifically, it captures the process name, the unique item key identifying the workflow item as it moves through the process, the package.procedure name currently executing, and the progress point reached within that package.procedure. The package is declared AUTHID CURRENT_USER, so all unqualified object references resolve in the schema of the calling session rather than in APPS. The header comment dates the base version to 2007, with an incremental revision identified as 120.1.12000000.1.

Key Procedures and Functions

Nine documented procedures make up the public surface of the package. Their purposes are as follows.

• INSERT_DEBUG — Records a debug entry keyed by workflow item type and item key, together with a progress string. This is the core workflow-progress writer used by Purchasing workflow functions.
• DEBUG_STMT — Writes a single log statement consisting of a log header, a token, and a message. It was added in support of PO/OTM integration to permit BPEL debug output, because standard FND logging cannot write entries when no APPS session context exists.
• DEBUG_BEGIN — Marks the entry point of a logged block of work, taking a log header that groups subsequent statements.
• DEBUG_END — Marks the closing boundary of a logged block previously opened with DEBUG_BEGIN under the same log header.
• DEBUG_VAR — Writes the name and value of a variable at a given progress point. The procedure is overloaded four times to accept VARCHAR2, NUMBER, DATE, and BOOLEAN values, so callers can log typed variables without explicit conversion.
• DEBUG_UNEXP — Records an unexpected condition at a given progress point, with an optional message supplied through a defaulted parameter.

Tables Accessed

The package reads and writes two underlying objects, exposed to APPS through synonyms: PO_WF_DEBUG and PO_WF_DEBUG_S. PO_WF_DEBUG holds the header-level debug records, keyed by process or log header, while PO_WF_DEBUG_S is associated with detailed, statement-level lines generated by the DEBUG_* calls. Both are diagnostic, non-transactional tables intended for temporary or controlled retention rather than permanent business data.

Usage Notes

PO_WF_DEBUG_PKG is a developer and support instrument rather than an end-user feature. It is invoked from within Purchasing workflow function code to leave an execution trail that administrators can inspect when diagnosing workflow failures, stuck items, or unexpected branching. Because the package is referenced by 58 other packages, its calls are widely distributed across Purchasing workflow logic and should be treated as a stable internal dependency. The DEBUG_STMT, DEBUG_BEGIN, DEBUG_END, and DEBUG_VAR procedures are also callable from BPEL processes and from custom PL/SQL that runs without an APPS session, using the log header convention to correlate related output. Typical use is to enable tracing around a suspected problem, reproduce the workflow event, read the rows in PO_WF_DEBUG and PO_WF_DEBUG_S, and then disable or truncate the logging to avoid unnecessary table growth in production.