select value from v$parameter where name = 'utl_file_dir'

B. To generate debug information for Pick Release :

Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Trace - set to Yes
INV: Debug Level - set to 11
FND: Debug Log Enabled - set to Yes
FND: Debug Log Level - set to Statement
FND: Debug Log Module = set to wms.plsql.%
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to StatementIn the Release Sales Order for Picking form go to Tools and check the Debug box.Submit the pick release. Provide the Pick Selection List Generation log file.

C. To generate debug information for Interface Trip Stop - SRS:

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 StatementSet the Debug Level parameter to 1 (Debugging ON) .Submit the job. Provide the log file.

D. To generate debug information for an APIs:

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 - set to a valid writeable directory pathAdd 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); 

Submit the job. Provide the log file.

How to generate WIP debug log files in ONLINE cases?
For 11.5.10 and above, the WIP debug log files will be created if
1. FND: Debug Log Filename = (Make sure this is null)
2. FND: Debug Log Enabled = Yes
3. FND: Debug Log Level = Statement
4. FND: Debug Log Module = WIP%
To get the log file, run the following SQL script. This will create an output called MoveON.txt
set pagesize 500
col message_text format a99
spool MoveON.txt
select message_text from fnd_log_messages where audsid=&audsid order by log_sequence;
spool off
To get the audsid In online cases
Navigate to Help > About Oracle applications
Note AUDSID Under Database Server and use it in the above sql.
To get the log messages for mobile applications
1. Get the maximum log sequence number using the following sql just before performing the test case and make a note of it.
select Max(log_sequence) from fnd_log_messages;
2. To get the log file,run the following SQL script.
set pagesize 500
col message_text format a99
spool log.txt
select message_text from fnd_log_messages where log_sequence > &log_sequence;
Use the log_sequence number which is obtained from the point 1.
Note: For 11.5.9 and prior, there will be NO WIP debug log files generated for online cases.

How to generate WIP log files in BACKGROUND cases?
For 11.5.10 and above, the WIP debug log files will be created if
1. FND: Debug Log Filename = (Make sure this is null)
2. FND: Debug Log Enabled= Yes
3. FND: Debug Log Level = Statement
4. FND: Debug Log Module = WIP%
To get the log file, run the following SQL script. This will create an output called MoveBG.txt
set pagesize 500
col message_text format a99
spool MoveBG.txt
select message_text from fnd_log_messages where audsid=(select oracle_session_id from fnd_concurrent_requests where
request_id = &Concurrent_Request_Id) order by log_sequence;
spool off
For 11.5.9 and prior, the WIP debug log files will be created if
1. TP: WIP Concurrent Message Level = Message Level 2
2. TP: WIP Debug Directory = "valid directory from v$parameter"
You can use the following query to find out a valid directory.
select value from v$parameter where name=utl_file_dir;
3. TP:WIP Debug File = "valid filename"
4. MRP: Debug Mode = Yes

Collecting RCV Debug files & logs in IMMEDIATE mode

1. Set the following profiles at the user level before proceeding further.
Profile Value Comments
RCV:Debug Mode Yes
RCV:Processing mode Immediate
PO:Enable Sql Trace for Receiving Processor Yes
FND:Log Enabled Yes
FND:Log Level Statement
FND:Log Module po% In small case
INV:Debug Level 11
INV:Debug Trace Yes
INV:Debug file utl_file_dir/newfilename To get utl_file_dir, use the following sql :
select value from v$parameter where name ='utl_file_dir';

2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application.

3. Perform the problematic transaction.
=> Note down the concurrent request id of the Receiving Transaction Processor that gets launched.

4. Once RTP completes, get the o/p of the following in .xls format.

select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text
from fnd_log_messages
where timestamp > sysdate - 2/24
and process_id = ( select os_process_id from fnd_concurrent_requests where request_id = &request_id)
and module like 'po%'

Pass the concurrent request_id from step 3.

5. Sql trace file will get generated under udump folder.

Use the following sql to get the udump path.
SELECT value FROM v$parameter WHERE name ='user_dump_dest' ;

select oracle_process_id from fnd_concurrent_requests
where request_id = &p_request_id
Pass the concurrent request_id from step 3.

Now search for the file names *< output of previous query >* under the udump folder.

6. Other files to be uploaded:
a) Inv log file.
b) rcv11i o/p.
c) Appscheck for PO & INV

Collecting RCV Debug files & logs in BATCH mode

1. Set the following profiles at the user level before proceeding further.
ProfileValueCommentsRCV:Debug Mode Yes RCV:Processing mode Batch PO:Enable Sql Trace for Receiving ProcessorYes FND:Log Enabled Yes FND:Log Level Statement FND:Log Module po% In small case INV:Debug Level 11 INV:Debug Trace Yes INV:Debug file utl_file_dir/newfilename To get utl_file_dir, use the following sql :
select value from v$parameter where name ='utl_file_dir';

2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application.

3. Get the dumps of rcv_headers_interface & rcv_Transactions_interface for the transaction before running the Receiving Transaction Processor (RTP)
Please give the output in .xls format, say rti_before_rtp.xls & rhi_before_rtp.xls
=> Note down the group_id.

4. Run 'Receiving Transaction Processor' by passing the group_id from step 3.
=> Note down the concurrent request id of the Receiving Transaction Processor that gets launched.

5. Once RTP completes, get the o/p of the following in .xls format.

select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text
from fnd_log_messages
where timestamp > sysdate - 2/24
and process_id = ( select os_process_id from fnd_concurrent_requests where request_id = &request_id)
and module like 'po%'

Pass the concurrent request_id from step 4.

6. Get the dumps of rcv_headers_interface & rcv_Transactions_interface transaction after RTP run.
Please give the output in .xls format, say rti_after_rtp.xls & rhi_after_rtp.xls

7. Sql trace file will get generated under udump folder.

Use the following sql to get the udump path.
SELECT value FROM v$parameter WHERE name ='user_dump_dest' ;

select oracle_process_id from fnd_concurrent_requests
where request_id = &p_request_id;

Pass the concurrent request_id from step 4.
Now search for the file names *< output of previous query >* under the udump folder.

8. Other files to be uploaded:
a) Inv log file.
b) rcv11i o/p.
c) Appscheck for PO & INV

Collecting RCV Debug files & logs in ONLINE mode

1. Set the following profiles at the user level before proceeding further.
ProfileValueCommentsRCV:Debug Mode Yes RCV:Processing mode Online FND:Log Enabled Yes FND:Log Level Statement FND:Log Module po% In small case INV:RPC Time Out 1000 INV:Debug Level 11 INV:Debug Trace Yes INV:Debug file utl_file_dir/newfilename To get utl_file_dir, use the following sql :
select value from v$parameter where name ='utl_file_dir'; Initialization SQL Statement - Custom Begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SETTRACEFILE_IDENTIFIER='||''''||'123456'||''''||' EVENTS='||''''||'10046TRACE NAME CONTEXT FOREVER, LEVEL 12'||'''');End;
Pls type the above in a single line

2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application.

3. Run SELECT MAX(LOG_SEQUENCE) FROM FND_LOG_MESSAGES;
=> Note down this value : value 1

4.Perform the transaction that is failing. Wait till you get the error message.

5. Run SELECT MAX(LOG_SEQUENCE) FROM FND_LOG_MESSAGES;
=> Note down this value : value 2

6. Pls get the o/p of the following query in .xls format

select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text
from fnd_log_messages
where log_sequence between < value1 > and < value2 > ;

7. Sql trace file will get generated under udump folder.

Use the following sql to get the udump path.
SELECT value FROM v$parameter WHERE name ='user_dump_dest' ;

Nowsearch in this udump folder for all files having the string '123456' inthe file name & upload all such files.

8. Other files to be uploaded:
a) Inv log file.
b) rcv11i o/p.
c) Appscheck for PO & INV

Reference Note:338291.1 - Howto Enable WMS / MSCA Logging

[port].system.log

Refer http://blog.csdn.net/pan_tian/article/details/7433252

Refer:http://blog.csdn.net/pan_tian/article/details/7677120

====EOF====

转载请注明出处：http://blog.csdn.net/pan_tian/article/details/7687582