OPP - Output Post Processor

OPP ( Output Post Processor ) [ When BI Publisher is setup ]

The standard Oracle reports are not much user friendly where as XML Publisher reports are very user friendly and easy to understand as it allows you to have
report in the form of graphs,Statistics etc etc

When ever you run a report request once processig the report the Conc Mgr contacts OPP to apply the XML Publisher template and finally creates the o/p

To activate OPP keep in mind these things

- Set Profile Concurrent: GSM Enabled to 'Y'

-  While defining Work Shift's of the OPP

    Set
            Processes = 2
    and
            Parameters = oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
    and
            Sleep Second = 30

( Note here Processes = 2 and Threads =5 means it can handle 2*5=10 requests in parallel )


Profiles controlling OPP timeout

Concurrent:OPP Response Timeout - Specifies the amount of time a manager waits for OPP to respond to its request for post processing. [ Default 120 seconds (2 min.) ]

Concurrent:OPP Process Timeout - Specifies the amount of time the manager waits for the OPP to actually process the request. [ Default  300 seconds (5 min.) ]


This depends on


size of the XML Data File
complexity of the template
performance of the server
....

Key Pts :

For OPP to run  as told before profile "Concurrent: GSM Enabled to 'Y'" needs to be set which means Service Manager needs to be up and running.

When ever you see that OPP is not up check for Service Mgr is up or not. This is common issue after cloning.

UR's Key Run ;-)