To generate a debug file from the Shipping Transaction or Quick Ship forms:
Note: if executing Pick Release from this form, please refer to B. Pick Release below for additional settings and log file.
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - This profile option 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:
select value from v$parameter where name = 'utl_file_dir'
**If the profile option is set to the same path as OM: Debug Log Directory profile option, the file may be retrieved using the Order Management concurrent request Diagnostic: OM Debug File Retrieval (Order Management responsibility, Reports,Requests > Request > Single Request). .
3. In the Shipping form, go to Tools and check the Debug box. Please make a note of the file name displayed for later retrieval.
4. Perform the action you wish to debug.
5. Go to Tools and uncheck Debug.
6. Provide the debug file from the directory specified in step 3. If the profile options WSH: Debug Log Directory and OM: Debug Log Directory are set to the same value, use the concurrent request Diagnostic: OM Debug File Retrieval (Order Management > Run Requests > Single Request) to retrieve the file. To view the debug and save ( View > Requests > Relevent Request_id (button). Click View Output > Save file as "filename.txt". Provide the "filename.txt" file to Support.
7. Reset profile options in Step 1.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358154.1: Diagnostics: WSH Shipping Forms Debugging.
B. To generate a debug for Pick Release:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11 >
3. 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.%
4. In the Release Sales Order for Picking form go to Tools and check the Debug box.
5. Submit the pick release.
6. 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.
7. Reset profile options in Step 1 and if using WMS, Step 3.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358164.1: Diagnostics: WSH Pick Release Debug.
C. To generate a debug for Interface Trip Stop - SRS:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5 WSH: Debug Enabled - set to Yes INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement INV: Debug Level - set to 11
3. Set the Debug Level parameter to 1 (Debugging ON)
4. Submit the job.
5. Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
6. Reset profile options in Step 1.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358156.1: Diagnostics: WSH Interface Trip Stops Debug.
D. To generate a debug for an API:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
WSH: Debug Log Directory - This profile option 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:
select value from v$parameter where name = 'utl_file_dir'
**If the profile option is set to the same path as OM: Debug Log Directory profile option, the file may be retrieved using the Order Management concurrent request Diagnostic: OM Debug File Retrieval (Order Management responsibility, Reports,Requests > Request > Single Request). .
3. Add the following line of code in the wrapper script which calls the API:
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);
4. Submit the job.
5. Provide the log file.
6. Reset profile options in Step 1.
Versions 11.5.2 to 11.5.8
E. To generate a debug for Pick Release:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
3. In the Release Sales Order for Picking form go to Tools and check the Debug box.
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.
6. Reset profile options in Step 1.
F. To generate a debug for Interface Trip Stop - SRS:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
3. Set the Log Level parameter to 1 (Debugging ON)
4. Submit the job.
5. Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
6. Reset profile options in Step 1.
G. To generate a debug for an API:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
WSH: Debug Log Directory
select value from v$parameter where name = 'utl_file_dir'
3. Add the following line of code in the wrapper script which calls the API:
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);
4. Submit the job.
5. Provide the log file
6. Reset profile options in Step 1.
Note: if executing Pick Release from this form, please refer to B. Pick Release below for additional settings and log file.
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - This profile option 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:
select value from v$parameter where name = 'utl_file_dir'
**If the profile option is set to the same path as OM: Debug Log Directory profile option, the file may be retrieved using the Order Management concurrent request Diagnostic: OM Debug File Retrieval (Order Management responsibility, Reports,Requests > Request > Single Request). .
3. In the Shipping form, go to Tools and check the Debug box. Please make a note of the file name displayed for later retrieval.
4. Perform the action you wish to debug.
5. Go to Tools and uncheck Debug.
6. Provide the debug file from the directory specified in step 3. If the profile options WSH: Debug Log Directory and OM: Debug Log Directory are set to the same value, use the concurrent request Diagnostic: OM Debug File Retrieval (Order Management > Run Requests > Single Request) to retrieve the file. To view the debug and save ( View > Requests > Relevent Request_id (button). Click View Output > Save file as "filename.txt". Provide the "filename.txt" file to Support.
7. Reset profile options in Step 1.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358154.1: Diagnostics: WSH Shipping Forms Debugging.
B. To generate a debug for Pick Release:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11 >
3. 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.%
4. In the Release Sales Order for Picking form go to Tools and check the Debug box.
5. Submit the pick release.
6. 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.
7. Reset profile options in Step 1 and if using WMS, Step 3.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358164.1: Diagnostics: WSH Pick Release Debug.
C. To generate a debug for Interface Trip Stop - SRS:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5 WSH: Debug Enabled - set to Yes INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement INV: Debug Level - set to 11
3. Set the Debug Level parameter to 1 (Debugging ON)
4. Submit the job.
5. Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
6. Reset profile options in Step 1.
For a short video on creating and retrieving a Shipping Forms Debug, please refer to Document 1358156.1: Diagnostics: WSH Interface Trip Stops Debug.
D. To generate a debug for an API:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
WSH: Debug Log Directory - This profile option 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:
select value from v$parameter where name = 'utl_file_dir'
**If the profile option is set to the same path as OM: Debug Log Directory profile option, the file may be retrieved using the Order Management concurrent request Diagnostic: OM Debug File Retrieval (Order Management responsibility, Reports,Requests > Request > Single Request). .
3. Add the following line of code in the wrapper script which calls the API:
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);
4. Submit the job.
5. Provide the log file.
6. Reset profile options in Step 1.
Versions 11.5.2 to 11.5.8
E. To generate a debug for Pick Release:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
3. In the Release Sales Order for Picking form go to Tools and check the Debug box.
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.
6. Reset profile options in Step 1.
F. To generate a debug for Interface Trip Stop - SRS:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
3. Set the Log Level parameter to 1 (Debugging ON)
4. Submit the job.
5. Provide the Interface Trip Stop log file (View > Requests > Find > click on View Log... for the appropriate file).
6. Reset profile options in Step 1.
G. To generate a debug for an API:
1. Following Profile Options need to be set before each test case, then reset after completion:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
INV: Debug Trace - set to Yes
2. The following Profile Option once set do not need to be changed.
WSH: Debug Level - set to Statement
INV: Debug Level - set to 11
WSH: Debug Log Directory
select value from v$parameter where name = 'utl_file_dir'
3. Add the following line of code in the wrapper script which calls the API:
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);
4. Submit the job.
5. Provide the log file
6. Reset profile options in Step 1.
No comments:
Post a Comment