Pricing Engine Request Trace:
1. Set the profile option QP:
Debug to Request Viewer On at the user level.
2. Price the line or the order.
3. On Orders Workbench, go to Tools->Pricing
Engine Request Viewer to view the pricing request log.
Shipping Trace
WSH:Debug Enabled : Yes or No
(Default is No)
WSH:Debug Log Directory : Must be
specified as UTL_FILE parameter value
WSH:Debug Level : Valid Values are:
Performance,Statement,Procedure (Default),Event
Inventory Transaction Trace
INV:Debug Trace : Yes or No (Default
is No)
INV:Debug file (Including the
complete path): Must be specified as UTL_FILE parameter value AND the .dbg file
be created in that directory (e.g. /usr/tmp/San_Inv_trace.dbg) with the file permissions
allowing oracle to write to that file.
INV:Debug Level : Valid Values are:
1 to 10. 10 being the highest level of logging supported.
Order Management Trace
Set the following profile options:
OM: Debug Level - set to 5 OM: Debug Log Directory - any directory that can be
written to by the database
Set profile option OM: Debug Log Directory
at the Site & Application Level.
In the OM form, go to Tools ->
Debug and select 'Write to a File'. Perform the action you wish to debug.
Go to Tools -> Debug and select
'Turn Debug Off' to complete debugging.
The debug log file is on the Database
Server tier.
To retrieve the debug file, navigate
to Order Management > Run Requests. Then choose: Diagnostics: OM Debug File
Retrieval. Parameters: Give the name of the debug file noted in step above.
Only give the file name, not the directory path. Remember the first letter in
the file name is lower case 'L'.
To view the debug file, navigate to
View > Requests. Click View Output.
To generate debug information for a
concurrent process, set the profile option OM: Debug Level to 5. This will
cause debug statements to be generated in the concurrent request log file.
Using
Forms trace
1. Before running a trace, make sure
that timed_statistics is turned on at the database level:
alter system set timed_statistics = true;
2.To turn trace on at the form level,
go to the toolbar and navigate to
HELP -> TOOLS -> TRACE. By
clicking on the word trace, a checkmark will appear next to it, indicating that
trace has been turned on. Reproduce the problem.
Navigate to HELP -> TOOLS ->
TRACE, and click on the word trace to uncheck trace and turn it off.
3. Finding Your Trace File:
select name, value from v$parameter
where name = 'user_dump_dest';
4. Run tkprof
tkprof <filename.trc> <output_filename>
Using SQL trace
1. Before running a trace, make sure
that timed_statistics is turned on at the database level:
Alter system set timed_statistics = true;
2. Set the trace on using this SQL:
Alter session set sql_trace = true;
3. Finding Your Trace File:
Select name, value from v$parameter
where name = 'user_dump_dest';
4. Run tkprof
tkprof <filename.trc> <output_filename>
MSCA Trace
Getting Mobile Debug Log
------------------------
For Release 11i
Please set the Debug profiles for
the Mobile in the instance,
1. Navigate to 'cd $MWA_TOP/secure'
2.
Open the file mwa.cfg
3. In this file, check for the log
level setting , it should be
'mwa.LogLevel=trace'
Also check for 'mwa.logdir' to be set accordingly
4. Restart Mobile Server
5. After doing a test case there
will be files created in log directory
(specified in mwa.cfg) like
<port-number>.WMS.log
<port-number>.INV.log
<port-number>.system.log
For Release 12
Please set the Debug profiles for
the Mobile in the instance,
1. Navigate to 'cd $INST_TOP/admin/install'
2. Open the file mwa.cfg
3. In this file, check for the log
level setting , it should be
'mwa.LogLevel=trace'
Also check for 'mwa.logdir' to be set accordingly
4. Restart Mobile Server
5. After doing a test case there will
be files created in log directory
(specified in mwa.cfg) like
<port-number>.WMS.log
<port-number>.INV.log
<port-number>.system.log
