Scribd
Upload
49 views3 pages

OPP Query and Log File.

The concurrent request ended with a status of "Warning" indicating that the Output Post Processor (OPP) failed to generate an output file. The actual error from the OPP is logged in the OPP log file, which can be obtained by running a SQL script to get the logfile location or accessing it directly from the Concurrent Manager application.

Uploaded by

Pavan Kumar Challa
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
49 views3 pages

OPP Query and Log File.

The concurrent request ended with a status of "Warning" indicating that the Output Post Processor (OPP) failed to generate an output file. The actual error from the OPP is logged in the OPP log file, which can be obtained by running a SQL script to get the logfile location or accessing it directly from the Concurrent Manager application.

Uploaded by

Pavan Kumar Challa
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/ 3

The Concurrent Request ends with Phase 'Completed' and Status 'Warning' which indicates that the Output

Post Processor (OPP) failed to generate an output file.

In such cases the request log file shows a generic error message indicating the the post-processing action has
failed.

+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Output file size:
4974
+------------- 1) PUBLISH -------------+
Beginning post-processing of request 6328232 on node XXXXXXXXXXX at 22-JAN2014 05:13:04.
Post-processing of request 6328232 failed at 22-JAN-2014 05:13:04 with the
error message:
One or more post-processing actions failed. Consult the OPP
service log for details.
+--------------------------------------+
+------------- 2) PRINT
-------------+
Not printing the output of this request because post-processing failed.
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+

The actual error returned by the XML Publisher Core engine is captured in the OPP log file.
One of the easiest way to obtain the OPP log file is to run the below script from the database by providing
request_id.

SELECT
fcpp.concurrent_request_id req_id,
fcp.node_name,
fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = 6328232
Output of the script contains logfile location just like below
/xxxapp/applxxx/inst/apps/XXXXXX_XXXXXX/logs/appl/conc/log/FNDOPP30482.txt

Developer/Administrator/DBA has to go to that location and take the OPP logfile


Alternate Method:
Getting OPP Log from the application itself
a. System Administrator Concurrent Manager Administer

b. Search for 'Output Post Processor'


c. Click the 'Processes' button

d. Click the Manager Log button. This will open the 'OPP'

e. Upload the OPP log file.

You might also like