Search Results append_other_dbg_file




Overview
Explore in AI Chat

Overview

WSH_DEBUG_SV is a server-side PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite, residing in the shipping execution product family (WSH prefix). The package provides the shared debugging and diagnostic tracing infrastructure used across Oracle Shipping Execution and its integration points. Its principal role is to centralize the creation, control, and output of debug log files so that developers, support analysts, and implementers can capture runtime trace information for shipping transactions, interface processing, and downstream integrations without embedding ad hoc logging code in every module.

The package is classified as OTHER under its API classification and holds a VALID status in the ETRM metadata for both 12.1.1 and 12.2.2. Notably, it is referenced by 239 other database objects, confirming its role as a foundational utility rather than an application-facing business API. The dependency list shows reliance on standard EBS technology stacks including FND_API, FND_FILE, FND_GLOBAL, FND_LOOKUPS, FND_LOOKUP_VALUES_VL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, INV_DEBUG_INTERFACE, OE_DEBUG_PUB, WSH_DEBUG_INTERFACE, WSH_UTIL_CORE, DBMS_UTILITY, UTL_FILE, and PLITBLM.

Key Procedures and Functions

The ETRM metadata documents approximately 50 procedures and functions within this package body. The most prominent documented entries include:

  • NAME — A function or procedure that returns or manages the identifying name of the debug session or debug area, used to distinguish logging contexts across concurrently executing processes.
  • PUSH — Writes or flushes buffered debug messages to the active debug output target, ensuring that trace information generated earlier in the call stack is persisted to the log file.
  • START_OTHER_APP_DEBUG — Initializes debugging for a non-Shipping application context, allowing cross-product diagnostics to funnel through the shared WSH debug infrastructure.
  • STOP_OTHER_APP_DEBUG — Terminates the external application debugging session, releasing resources and closing log handles opened by START_OTHER_APP_DEBUG.
  • APPEND_OTHER_DBG_FILE — Appends content from another application's debug file into the current Shipping debug output, enabling consolidated diagnostic reports.
  • SET_DEBUG_COUNT — Establishes or adjusts the debug verbosity counter that governs how much trace detail is written, typically controlled by FND_PROFILE values.

Additional helper routines within the 50-member package support message formatting, profile lookup evaluation, and interface-level debug interaction.

Tables Accessed

The package does not directly manipulate business application tables. The documented references are to underlying technology objects accessed via APPS synonyms: UTL_FILE (for reading and writing operating-system log files), DBMS_UTILITY (for call stack and error diagnostics), ALL_SOURCE (for inspecting PL/SQL source during trace operations), and PLITBLM (a predefined PL/SQL table type used for in-memory collections). Lookup and profile data are obtained through FND_LOOKUPS, FND_LOOKUP_VALUES_VL, and FND_PROFILE rather than through direct DML on transactional tables.

Usage Notes

WSH_DEBUG_SV is invoked primarily from within other Shipping Execution packages, concurrent programs, and interface processors that require conditional trace output. Because it is referenced by 239 dependent objects, it is effectively a shared service layer. Developers typically enable debugging by setting the relevant FND profile option, after which Shipping forms and concurrent programs call START-style routines to open a log, PUSH or append routines during execution, and STOP routines on completion. The UTL_FILE dependency implies that the database server must have a valid directory object and file system access configured for the debug output path. The package is not intended for end-user direct invocation; it is a developer and support diagnostic utility best used under guidance from Oracle Support or during controlled troubleshooting exercises.