- OracleApps Epicenter - http://www.oracleappshub.com -

Output Post Processor – OPP

Concurrent Processing uses the Output Post Processor (OPP) to enforce Post Processing actions for concurrent requests.

The Output Post Processor (OPP) is an enhancement to Concurrent Processing and is designed to support XML Publisher as post-processing action for concurrent requests. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

Ensure that enough OPP process existing to serve the incoming request load. Otherwise increase โ€œprocessโ€.

Thread Vs Process :You can either increase process (or) threads. It depends on the load .

Reseting and altering can be done via these navigation

Concurrent -> Manager -> Define > Output Post Processor


If you refer to metalink node 563233.1 , it is advised to have each PCP node should have one OPP must be defined.

Locating OPP log file?

whenever XML issues or other publishing problems occurs, first thing you will do is to trace the OPP logfile.Locating such logs is not a big things, just follow the steps below:

  1. logon with System Administrator
  2. Function: Concurrent --> Manager --> Administration and select the Output Post Processor
  3. Click on the Processes button
  4. Select the Concurrent Process which was active during the time that the request ran
  5. Click on the Manager Log button to open the Output Post Processor log file

Directly from the file system based after identifying the corresponding OPP log file name using the following SQL statement:

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

Bi Publisher Enhancement Parameters

You often encounter issue whenever you have XML Publisher concurrent program with OOP. You can slightly enhance without chasing DBA everytime.

  • Use XML Publisher's XSLT processor set to True (see fig 1 & 2cbelow)
  • Enable XSLT runtime optimization set to True (see fig 3 below)
  • Enable scalable feature of XSLT processor set to False.
    • Small Report - It is still recommended this remain false at Site level. This has the advantage of faster performance by not using temporary files for XSLT processing for small to medium reports.
    • Large Reports - what you need to do apply Patch 7599031. once Patch is applied this will safely set to True at the data definition level, enabling improved JAVA heap utilization along with ScalableFlag parameter and 'Options' field with the value to -Xmx1024M (or higher).

Simply follow these steps

Go to sys admin
add XML publisher administrator and choose the same responsblity
Home ->Administration

select the FO Properties

Fig 1: select FO processing

next is to reset these values

Fig 2: reseting the FO processing paramater

Go to sys admin
add XML publisher administrator and choose the same responsblity
Home ->Data Definition
search for data definition and view
then reset the value to TRUE as per figure below

Fig 3: reseting the XSLT runtime optimization set

Hope this post will help you to understand OOP.