Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: How To Create A Debug Log File In An AR Form.
Solution:
If you are on 11.5.9 and below, you need to enable profile option
'AR: Enable Debug Message Output' at user level to be able to produce
a debug logfile through setting AR_DEBUG_FLAG.
This can be done in your Receivables Responsibility through
Control > Profile Options.
1.
Navigate to the form where there is a problem/error.
Start with the steps to reproduce the issue.
Stop just before the problem/error occurs.
Don't hit the key that will invoke the error.
2.
On the menu, click help/diagnostic/examine (11.5) or
help/tools/examine (10.7 and 11.0).
3.
Change block field, then choose from the list of values: PARAMETER
4.
For the field, then TYPE in: AR_DEBUG_FLAG
There is no LOV for this field. Explicitly type in AR_DEBUG_FLAG.
5.
For the value, then TYPE in:
FS
There must be the blanks between FS, the path, and the file name.
a)
FS
FS creates a file, displaying Forms and Server debug messages.
b)
This is where the AR Debug Log file will be written to.
To find out where the log file must be saved, type the following in
SQL*Plus:
select value from v$parameter
where upper(name) = 'UTL_FILE_DIR';
It should return something similar to
VALUE
--------------------------------------------------------------------------------
/sqlcom/inbound, /sqlcom/outbound, /sqlcom/log, /sqlcom/out
Type in a path exactly as shown in the output of the select statement.
If value returned is *, it should be allowed to write the log to any directory.
The directory should have the correct permissions, privileges (write privileges)
.
c) Decide what to call the debug log file. For example, debug2.dbg
If the file specified already exists, the new debug messages will be
appended to it. In general, it is recommended to define a new debug file for
each problem reported.
d)
Full example:
Block: PARAMETER
Field: AR_DEBUG_FLAG
Value: FS /sqlcom/log debug2.dbg
6. To turn on Trace: go to menu, click on help/diagnostics/trace.
This can be skipped if a Trace is not needed.
7.
Continue to navigate through the form as started under 1. and reproduce
the problem/error.
Once done, exit the form.
8.
To turn off Trace: go to menu, click on help/diagnostics/trace
9.
Go to the directory where your AR Debug Log is located.
This is the path entered in step 5.
10.
Go to the directory where the Trace is located.
To find out where the Trace is written (if there was no message with the
description of the path and filename, when you enabled/disabled Trace),
type the following in SQL*Plus:
select value from v$parameter
where name='user_dump_dest';
11.
Upload AR Debug Log and raw and tk-proffed Trace to Metalink in your Service
Request (TAR).
Comments:
Trace is NOT required to activate AR_DEBUG_FLAG.
So if a Trace is not needed, steps 6, 8 and 10 can be skipped.
References:
Note 152164.1 How To Create A Debug Log File In An AR Form.
Solution:
If you are on 11.5.9 and below, you need to enable profile option
'AR: Enable Debug Message Output' at user level to be able to produce
a debug logfile through setting AR_DEBUG_FLAG.
This can be done in your Receivables Responsibility through
Control > Profile Options.
1.
Navigate to the form where there is a problem/error.
Start with the steps to reproduce the issue.
Stop just before the problem/error occurs.
Don't hit the key that will invoke the error.
2.
On the menu, click help/diagnostic/examine (11.5) or
help/tools/examine (10.7 and 11.0).
3.
Change block field, then choose from the list of values: PARAMETER
4.
For the field, then TYPE in: AR_DEBUG_FLAG
There is no LOV for this field. Explicitly type in AR_DEBUG_FLAG.
5.
For the value, then TYPE in:
FS
There must be the blanks between FS, the path, and the file name.
a)
FS
FS creates a file, displaying Forms and Server debug messages.
b)
This is where the AR Debug Log file will be written to.
To find out where the log file must be saved, type the following in
SQL*Plus:
select value from v$parameter
where upper(name) = 'UTL_FILE_DIR';
It should return something similar to
VALUE
--------------------------------------------------------------------------------
/sqlcom/inbound, /sqlcom/outbound, /sqlcom/log, /sqlcom/out
Type in a path exactly as shown in the output of the select statement.
If value returned is *, it should be allowed to write the log to any directory.
The directory should have the correct permissions, privileges (write privileges)
.
c) Decide what to call the debug log file. For example, debug2.dbg
If the file specified already exists, the new debug messages will be
appended to it. In general, it is recommended to define a new debug file for
each problem reported.
d)
Full example:
Block: PARAMETER
Field: AR_DEBUG_FLAG
Value: FS /sqlcom/log debug2.dbg
6. To turn on Trace: go to menu, click on help/diagnostics/trace.
This can be skipped if a Trace is not needed.
7.
Continue to navigate through the form as started under 1. and reproduce
the problem/error.
Once done, exit the form.
8.
To turn off Trace: go to menu, click on help/diagnostics/trace
9.
Go to the directory where your AR Debug Log is located.
This is the path entered in step 5.
10.
Go to the directory where the Trace is located.
To find out where the Trace is written (if there was no message with the
description of the path and filename, when you enabled/disabled Trace),
type the following in SQL*Plus:
select value from v$parameter
where name='user_dump_dest';
11.
Upload AR Debug Log and raw and tk-proffed Trace to Metalink in your Service
Request (TAR).
Comments:
Trace is NOT required to activate AR_DEBUG_FLAG.
So if a Trace is not needed, steps 6, 8 and 10 can be skipped.
References:
Note 152164.1 How To Create A Debug Log File In An AR Form.
No comments:
Post a Comment