Scribd
Upload
9 views2 pages

Debug Profiles

The document outlines the steps to enable debugging for the Purchase Order (PO) approval process and concurrent requests in Oracle. It includes setting specific profiles, running SQL queries to obtain log sequences, and uploading the outputs for further analysis. Additionally, it provides instructions on enabling trace for concurrent programs to capture SQL execution details for troubleshooting.

Uploaded by

muhammadimtiaz310285
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

Debug Profiles

The document outlines the steps to enable debugging for the Purchase Order (PO) approval process and concurrent requests in Oracle. It includes setting specific profiles, running SQL queries to obtain log sequences, and uploading the outputs for further analysis. Additionally, it provides instructions on enabling trace for concurrent programs to capture SQL execution details for troubleshooting.

Uploaded by

muhammadimtiaz310285
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Please do the following after reducing the amount in 1 line and saving the PO before submitting for

approval.
---------------------------------------------------
Please take debug logs for the approval process as follows:

1) Set profiles below for user that will Submit PO for approval
a) FND: Debug Log Enabled = Yes
b) FND: Debug Log Level = Statement
c) FND: Debug Log Module = %
d) PO: Set Debug Workflow ON = Yes

2) Run the following sql to get the max(log_sequence): << this is needed for FND debug log
SQL> select max(log_sequence) from fnd_log_messages;

3) Execute the following sql query to get max(execution_sequence): << this is needed for PO
workflow debug log
SQL> SELECT Max(execution_sequence) FROM po_wf_debug;

4) Submit #188 for approval and run workflow background process

Steps to get FND log messages:


------------------------------
5) Run the following sql to get the FND log messages :

select module, message_text


from fnd_log_messages
where log_sequence > '&output_step2';

Steps to get the PO Workflow debug messages:


--------------------------------------------------
6) Run the following sql to get the po_wf_debug log messages :

SELECT * FROM po_wf_debug WHERE execution_sequence > '&output_step3';

--------------------------------------------------
Upload outputs of step 5 and step 6 on the SR . Then you can reset the profiles back.

Concurrent request Debug

You can also enable trace for a concurrent program in Oracle by following these steps:

1. Ensure the profile Concurrent: Allow Debugging is enabled


2. Navigate to View > Requests > Submit request

3. Enter the request name

4. Select Debug Options

5. Set the trace values and press Ok

FND: Debug Log Enabled YES


FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT
FND: Debug Log Module %

Sample setting to debug ONLY Receivables:

FND: Debug Log Enabled YES


FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT
FND: Debug Log Module PN%

You can get more options and dynamically enable trace during a program or report submission. A
trace file may be required while debugging an issue to show the SQL run and other important details
about a program or report. A common way to enable trace is via system administration setup with
the "Enable Trace" Checkbox on the concurrent program setup under System Admin > Concurrent >
Program > Define.

You might also like