Oracle EBS各个模块日志收集的方法

MSCA(Mobile Supply Chain Application)日志的收集 Reference Note:338291.1 - Howto Enable WMS / MSCA Logging 1. Locate the

MSCA(Mobile Supply Chain Application)日志的收集

Reference Note:338291.1 - Howto Enable WMS / MSCA Logging

1. Locate the mwa.cfg file:
In 11i: $MWA_TOP/secure/
In R12: $INST_TOP/admin/install/

2. Ensure trace is enabled in the mwa.cfg file.
You should see trace level: mwa.LogLevel=TRACE
Also check for 'mwa.logdir' to be set accordingly

3. Restart the mobile server and hit ctrl-X, see what directory is for the logging

4. After you perform the transaction again, get the following log files from that log directory
[port].INV.log
[port].system.log

Inventory模块日志的收集

Reference Note:148651.1 - INV DEBUG: How to get Debug Information for Inventory
Set the System Profile Values as follows:
SYSTEM PROFILE VALUES
-- Summary
INV: Debug Trace: Yes
INV:Debug Level: 11
INV: Debug file:  /usr/tmp/invdebug.log

-- Details
INV: Debug Trace: set Yes to turn on the debug functionality.
set No to turn off the debug functionality.

INV:Debug Level: set 0 , will print the summary debug messages.
set 10 , to print the detail debug messages.

INV: Debug file (Including the complete path):
The path is one of the directories from the valid
directories defined in the obtained v$parameter
through the following sql :

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

Make sure to include the file name at the end of the
path, e.g. '/<...>/trx_mgr.log'

Order Management模块日志收集方法

Reference (NOTE:121054.1):How to generate a debug file in OM

OM: Debug = 5
OM: Debug Log Directory = select value from v$parameter where name = 'utl_file_dir';
The User must have write privilege to this directory>

Log off and log back in the application for the profile settings to take place.

Shipping模块日志收集方法

Reference Note:290432.1 - How to Create a Debug File in Shipping Execution

A. To generate a debug file from the Shipping Transaction or Quick Ship forms

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 - any directory that can be written to by the database
To check, run the following SQL statement:

Code:

select value from v$parameter where name = 'utl_file_dir'Set profile option WSH: Debug Log Directory at the Site & Application Level.

In the Shipping form go to Tools and check the Debug box. This will print out a file name - NOTE down this file name.

Perform the action you wish to debug.

Go to Tools and uncheck Debug.

After you have completed generating the debug file, please set thevalue of the profile OM: Debug Level back to 0 and WSH: Debug Enabledset to No, otherwise there will be some performance impact. Retrievethe debug file from the directory specified in step 1.

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 Statement

In 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 Statement

Set 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 path

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);

Submit the job.

Provide the log file.

WIP模块日志收集方法

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

，