Good way to enable FND Trace/Diagnostics in R12/11i

Published August 27, 2012

Here is clean way to enable FND TRACE:

a) Just Before replicating the error, please truncate FND_LOG_MESSAGES table as follows (You need to make sure earlier entries are not part of any other current analysis before doing this) :
truncate table applsys.FND_LOG_MESSAGES;
b) Login as a user with System Administrator responsibility and then navigate to:

Profile-> System.
Then in the Forms, set the following system profile options:

FND: Debug Log Enabled = Yes
FND: Debug Log Filename =
FND: Debug Log Module = %oid% < For OID related logs
FND: Debug Log Level = Statement
FND: Diagnostics = Yes
FND: Debug Log Mode = Asynchronous with Cross-Tier Sequencing

There is no need to stop and restart E-Business Suite.
C) Then replicate the error you are getting and query the table as follows and upload the text Output:

SQL> select module||’ ‘||message_text from fnd_log_messages
order by timestamp;

Make SURE you enable the diagnostics, perform the desired steps as indicated and turn off
diagnostics or get the O/P ASAP. If NOT it will write redundant entries in the the table that will
interfere in this specific problem troubleshooting process.

If you can perform the SQL query in a tool like TOAD or SQL developer and upload the O/P in EXCEL
FORMAT for better viewing, it would be great.

Then replicate the error you are getting and query the table as follows and upload the text Output



contact
NEWS

To receive Evidian news, please fill the following form.

`