Search Results file_debug

Overview

WMS_UTILITY_PVT is a private PL/SQL package owned by APPS in the Oracle E-Business Suite Warehouse Management (WMS) module. It operates as an internal utility layer supporting the warehouse execution APIs, providing two distinct categories of functionality: file-based diagnostic logging built on the UTL_FILE package, and transaction identifier resolution for inventory material transactions. Because the package is classified as PVT (private), it is not exposed as a public integration surface; it is consumed internally by other WMS program units and by Oracle's own diagnostic tooling. The package header carries the version identifier 120.1.12010000.1, dated 2008/07/28, indicating that the code has remained stable across the 12.1.1 and 12.2.2 release streams with no functional change recorded in the shipped header comment.

Key Procedures and Functions

The package exposes six documented program units, four of which implement the logging subsystem and two of which resolve transaction identifiers.

• GET_LOG_DIR — Reads the directory path configured through the database initialization parameter utl_file_dir and returns it to the caller through an output parameter. This establishes the server-side directory context in which log files are subsequently opened.
• ENABLE_FILE_DEBUG — Opens a log file for writing, given a path name and file name supplied by the caller. It returns the standard EBS concurrent-style return status, message count, and message data triplet so that failures to open the file can be surfaced and handled by the calling program.
• FILE_DEBUG — Writes a single line of diagnostic text to the log file that has been opened by ENABLE_FILE_DEBUG. This is the procedure most commonly associated with the search term "file_debug" and is the workhorse of the diagnostic tracing mechanism.
• DISABLE_FILE_DEBUG — Closes the currently open log file, flushing the write buffer and releasing the file handle. The header comment misspells the procedure name as disabel_file_debug, but the deployed name is DISABLE_FILE_DEBUG.
• GET_CREATE_TRX_ID — Returns an approximate transaction identifier for a specified item, revision, and lot number combination. The return value approximates the transaction that originally created the item/lot/revision record within an LPN context.
• GET_UPDATE_TRX_ID — Returns the corresponding approximate transaction identifier for the most recent update affecting the same item, revision, and lot combination.

Tables Accessed

The transaction-resolution functions query inventory transaction data through APPS synonyms. MTL_MATERIAL_TRANSACTIONS supplies the material transaction records against which creation and update transaction identifiers are derived. MTL_TRANSACTION_LOT_NUMBERS provides the lot number association for each transaction, allowing the functions to correlate a specific item, revision, and lot with the originating transaction. The logging procedures depend on UTL_FILE for all file input and output, and on V$PARAMETER to read the value of utl_file_dir when resolving the log directory. No insert, update, or delete activity is performed against the material transaction tables by this package; access is read-only.

Usage Notes

WMS_UTILITY_PVT is invoked from within WMS server-side code and is not intended for direct customer invocation. Custom developers typically encounter it in two situations. First, when diagnosing unexpected behavior in warehouse execution flows, developers enable file debugging by calling ENABLE_FILE_DEBUG with a valid directory and file name, invoke the failing operation, and then inspect the file populated by FILE_DEBUG calls embedded in the WMS code path before calling DISABLE_FILE_DEBUG. Second, Oracle Support uses the transaction identifier functions to reconstruct the provenance of a lot or revision when investigating inventory discrepancies. Because the package is classified as private, Oracle reserves the right to alter its signature or behavior without notice, and any custom code that references it directly carries upgrade risk between 12.1.1 and 12.2.2. The ETRM metadata records zero dependent packages, confirming that WMS_UTILITY_PVT is a leaf-level utility rather than a shared public API.