ShowDoc

Page 1 of 3

My Oracle Support (the new MetaLink) Bookmarks Admin Profile Feedback Sign Out Help

Headlines Knowledge Browser Advanced Search

Knowledge

Service Request

Collector

Patches & Updates

Community

Certify

Bug Search Go Advanced Saved Searches

Quick Find Knowledge Base

Did this article help solve your problem? Select

Would you recommend this document to others? Select

Submit

TIP: Click help for a detailed explanation of this page.

Subject: How to Create a Debug File in Shipping Execution Doc ID: 290432.1 Modified Date : 09-JUL-2009 In this Document Goal Solution Type: HOWTO Status: PUBLISHED

Bookmark

Go to End

Applies to:
Oracle Shipping Execution - Version: 11.5.2 to 12.1 Information in this document applies to any platform. Oracle Shipping Delivery Based - Version: 11.5.2 to 12.1

Goal
Generate debug files to be used to analyze code and assist Support and Development in resolving Shipping application issues.

General Instructions
A. For 11.5.10 (Family pack J) only: To further enhance debugging information, please insure Patch 5636116 (containing WSHDEBGB.pls - 115.17.11510.2) has been applied. B. To improve performance and reduce the number and size of log files. Set all profile options at the User level except for the log file locations (see C below). After successfully generating the required files, reset the following profile options: OM: Debug Level - set to 0 WSH: Debug Enabled - set to No INV: Debug Trace - set to No FND: Debug Log Enabled - set to No C. The log file location profile options are: WSH: Debug Log Directory FND: Debug Log File for Middle-Tier INV: Debug file These profile options may be set at the Site level to any valid directory path. A valid path is any directory that can be written to by the database. To find available paths, run the following SQL statement:
Code:

select value from v$parameter where name = 'utl_file_dir' If the profile options are also set to the same path as OM: Debug Log Directory profile option, files may be retrieved using the Order Management concurrent request Diagnostic: OM Debug File Retrieval (Order Management responsibility, Reports,Requests > Request > Single Request). INV: Debug file and FND: Debug Log File for Middle-Tier must also include the name of the file to be generated. For example: /<a utl_file_dir value>/inv<SR number>.dbg /<a utl_file_dir value>/wms<SR number>.dbg

Version Based Instructions

For version based instructions, please select the appropriate version. Versions 11.5.9 and higher Versions prior to 11.5.9

https://metalink2.oracle.com/metalink/plsql/f?p=130:14:3113608827649782142::::p1... 08-09-2009

ShowDoc

Page 2 of 3

Versions 11.5.9 to 12.1.x Listed are several methods for generating the log file, please click on the appropriate process. A. B. C. D. Shipping Transaction or Quick Ship forms Pick Release Interface Trip Stop - SRS API

A. To generate a debug file from the Shipping Transaction or Quick Ship forms: 1. Set the following profile options: OM: Debug Level - set to 5 WSH: Debug Enabled - set to Yes WSH: Debug Level - set to Statement WSH: Debug Log Directory - refer to General Instructions C above 2. In the Shipping form go to Tools and check the Debug box. Please make a note of the file name displayed for later retrieval. 3. Perform the action you wish to debug. 4. Go to Tools and uncheck Debug. 5. Provide the debug file from the directory specified in step 2. 6. Reset profile options as described in General Instructions B above. B. To generate debug information for Pick Release: 1. Set the following profile options: OM: Debug Level - set to 5 WSH: Debug Enabled - set to Yes WSH: Debug Level - set to Statement INV: Debug Trace - set to Yes INV: Debug Level - set to 11 INV: Debug file - refer to General Instructions C above 2. ONLY IF using Warehouse Management (WMS), set the following profile options: FND: Debug Log Enabled - set to Yes FND: Debug Log Level - set to Statement FND: Debug Log Module - set to wms.plsql.% FND: Debug Log Filename for Middle-Tier - refer to General Instructions C above 3. In the Release Sales Order for Picking form go to Tools and check the Debug box. Please make a note of the file name displayed for later retrieval. 4. Submit the pick release. 5. Provide the Pick Selection List Generation log file (View > Requests > Find > click on View Log... for the appropriate file), the file displayed in Step 3, the INV: Debug file (if generated) and if using WMS, the FND: Debug Log Filename for Middle-Tier. 6. Reset profile options as described in General Instructions B above. C. To generate debug information for Interface Trip Stop - SRS: 1. Set the following profile options: OM: Debug Level - set to 5 INV: Debug Level - set to 10 WSH: Debug Enabled - set to Yes WSH: Debug Level - set to Statement 2. Set the Debug Level parameter to 1 (Debugging ON) . 3. Submit the job. 4. Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file). 5. Reset profile options as described in General Instructions B above. D. To generate debug information for an APIs: 1. Set the following profile options: OM: Debug Level - set to 5 INV: Debug Level - set to 10 WSH: Debug Enabled - set to Yes WSH: Debug Level - set to Statement WSH: Debug Log Directory - refer to General Instructions C above 2. Add the following line of code in the wrapper script which calls the API:
Code:

DECLARE l_file_name VARCHAR2(32767); l_return_status VARCHAR2(32767); l_msg_data VARCHAR2(32767); l_msg_count NUMBER; BEGIN fnd_profile.put('WSH_DEBUG_MODULE','%'); fnd_profile.put('WSH_DEBUG_LEVEL',WSH_DEBUG_SV.C_STMT_LEVEL); wsh_debug_sv.start_debugger(l_file_name,l_return_status,l_msg_data,l_msg_count); 3. Submit the job. 4. Provide the log file. 5. Reset profile options as described in General Instructions B above.

https://metalink2.oracle.com/metalink/plsql/f?p=130:14:3113608827649782142::::p1... 08-09-2009

ShowDoc

Page 3 of 3

Versions 11.5.2 to 11.5.8 Listed are several methods for generating the log file, please click on the appropriate process. A. Pick Release B. Interface Trip Stop - SRS C. APIs A. To generate debug information for Pick Release: 1. Set the following profile options: OM: Debug Level - set to 5 INV: Debug Level - set to 10 2. In the Release Sales Order for Picking form go to Tools and check the Debug box. 3. Submit the pick release. 4. Provide the Pick Selection List Generation log file. 5. Reset profile options as described in General Instructions B above. B. To generate debug information for Interface Trip Stop - SRS: 1. Set the following profile options: OM: Debug Level - set to 5 INV: Debug Level - set to 10 2. Set the Log Level parameter to 1 (Debugging ON) . 3. Submit the job. 4. Provide the log file. 5. Reset profile options as described in General Instructions B above. C. To generate debug information for an API: 1. Set the following profile options: OM: Debug Level - set to 5 INV: Debug Level - set to 10 2. Add the following lines of code in the wrapper script which calls the API:
Code:

oe_debug_pub.initialize; oe_debug_pub.SetDebugLevel(5); DBMS_OUTPUT.PUT_LINE('Debug File = ' ||OE_DEBUG_PUB.G_DIR||'/'||OE_DEBUG_PUB.G_FILE); 3. Submit the job. 4. Provide the log file. 5. Reset profile options as described in General Instructions B above.

Keywords
WSH_DEBUG_MODULE ; WSH_DEBUG_LEVEL ; Help us improve our service. Please email us your comments for this document. .
My Oracle Support (the new MetaLink) Bookmarks Admin Profile Feedback Sign Out Help
Copyright 2006, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

https://metalink2.oracle.com/metalink/plsql/f?p=130:14:3113608827649782142::::p1... 08-09-2009