Sairam Nimmagadda

When a concurrent request for an Xml Publisher concurrent Request ends up with a Warning. If you have system administrator access you can access the Output Post Processor Log using the Concurrent -- Manager Menu. If you don't have access to System Administrator Responsibility, using the following query you can get the location of the log that's stored on the application server. From the Log: +------------- 1) PUBLISH -------------+  Beginning post-processing of request 19280863 on node SERVER at 15-MAY-2014 13:39:18. Post-processing of request 192808 failed at 15-MAY-2014 13:39:18 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_

To purge the workflow from the Oracle Database, we need to use the standard workflow purge sql file provided by Oracle. The file is located under the FND_TOP/sql folder. The file name is wfrmitt.sql Connect to the server. Connect to the sqlplus session as apps/*****. Execute the above mentioned file sql> @wfrmitt.sql sql> @FND_TOP/sql/wfrmitt.sql Will list all the item types. Will ask for the item type that needs to be purged. XXXXXX (item type) The workflow will be purged and all the activity information, error information will be purged. The child workflow (WF_ERRORS) for the workflow wont be purged. That would be a pre requisite for this activity.