Oracle-Developer.com Forums

[vj.jain]

First,

Generate the debug log from AUDSID:
This can used for AR, AP, OM, PO or any other module where tax is calculated on a transaction

1) enable the tax debug info by setting the following profiles:

FND: Debug Log Enabled -> Yes at the User level
FND: Debug Log Level -> Statement at the user level
FND: Debug Log Module -> %

2) Get the Logging Entries through SQL from Database FND_LOG_MESSAGES table
using apps login

After enable debug profiles, open the forms, and reproduce the error. The
first piece of information you need to get is the AUDSID of the current form
session. Go to Help->About Oracle Applications, you will find the AUDSID
field, for example, the AUDSID is 227395.

the query to get the debug log when audsid is found is as following:
set linesize 1000
set heading off Via SQL Plus run the following query:
.
select module, message_text
from fnd_log_messages
where audsid = 227395
and module like 'ZX%'
order by log_sequence;

the message_text is the log information you are looking for.

In case customer Fail to got AUDSID in about Oracle Application, kindly use the following steps to generate the debug log file:

1) Reproduce the error scenario in the instance.

2) Execute the following query:

SELECT user_id
FROM fnd_user where user_name ='ONAP' (ONAP is a sample user name used. Use the applications login username);


3) By using the user_id obtained from the previous command execute the following query to obtain the debug log file:

SELECT module, message_text
FROM fnd_log_messages
WHERE user_id =
AND module like 'ZX%'
AND timestamp > SYSDATE - 1 ORDER BY log_sequence;

B. Generate debug log from REQUEST_ID:
This can be used to generate the debug log for AR Autoinvoice and other document import process in AP and PO.

1) enable the tax debug info by setting the following profiles:

FND: Debug Log Enabled -> Yes
FND: Debug Log Level -> Statement
FND: Debug Log Module -> %

2) Get the Logging Entries through SQL from Database FND_LOG_MESSAGES table
using apps login

After enable debug profiles, open the forms, and reproduce the error. Get the request_id of your concurrent program.

the queries to get the debug log is as following:
set linesize 200
set heading off

Via SQL Plus run the following query:

SELECT LOG.module, LOG.message_text message
FROM FND_LOG_MESSAGES LOG,
FND_LOG_TRANSACTION_CONTEXT CON
WHERE CON.TRANSACTION_ID = &request_id
AND CON.TRANSACTION_TYPE = 'REQUEST'
AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
AND LOG.module like 'ZX%'
ORDER BY LOG.LOG_SEQUENCE;

the message_text is the log information you are looking for.

C. Generate the debug log from sequence_id :
This can be used to generate log files for PO process. Since PO's process include forms and OA page, which belong to difference session.

1) enable the tax debug info by setting the following profiles:

FND: Debug Log Enabled -> Yes
FND: Debug Log Level -> Statement
FND: Debug Log Module -> %

2) Get the Logging Entries through SQL from Database FND_LOG_MESSAGES table
using apps login

After enable debug profiles, run the following query to get the maximum log_sequence of the debug logs in the fnd_log_message table:

SELECT MAX(log_sequence)
FROM FND_LOG_MESSAGES;


Open the forms, and reproduce the error. Run the following query to get the debug log for the issue via SQLPLUS:

SET LINE 200
SET PAGES 999

select module, message_text message
from fnd_log_messages
where log_sequence > &log_sequence
and module like 'ZX%'
order by log_sequence;

the message_text is the log information you are looking for.