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.
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.
Output of the script contains logfile location just like below
/u01/app/inst/apps/NZAPPS/logs/appl/conc/log/FNDOPP10981694.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.
In such cases the request log file shows a generic error message indicating the the post-processing action has failed.
...
+------------- 1) PUBLISH -------------+
Beginning post-processing of request 3181343 on node FINAPPS at 25-OCT-2011 11:41:30.
Post-processing of request 3181343 failed at 25-OCT-2011 11:41:31 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
+--------------------------------------+
...
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 = &request_id;
Output of the script contains logfile location just like below
/u01/app/inst/apps/NZAPPS/logs/appl/conc/log/FNDOPP10981694.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.
check OOP file as follows:
sysadmin -> Concurrent -> Manager -> administer ->
Output Post Processor -> processes -> manager log
or better way is from find request window , choose concurrent
program -> Diagnostics -> view XML
Check the xml file in the end for error.
This is really too useful and have more ideas from yours. keep sharing many techniques. eagerly waiting for your new blog and useful information. Keep doing more..................
ReplyDeleteR12 Financials Training