Detailed Item Cost Report (XML) timed out waiting for the Output Post-processor to finish

In this Document

APPLIES TO:

Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.

SYMPTOMS

"Detailed Item Cost Report (XML)" runs for 31 hours,when "Detailed Item Cost Report" completes in 4 min for the same parameters.

STEPS

1. Navigator -> Cost Management -> View (M) -> Requests -> Submit a New Request (B) -> Single Request -> Detailed Item Cost Report (XML)
2. View the output
3. Encounter the issue

CAUSE

Detailed Item CostReport (XML) - the incorrect setup for OPP parameters

SOLUTION

1. Increase the number of Output Post Processor as follows:
* logon to Applications with "System Administrator" responsibility
* Navigate to Concurrent -> Manager -> Define
* Query for "Output Post Processor"
* Click on "Work Shifts" and Increase the number of processes.
(If you have 2 processes then make them 4 if required to 8).

* make sure that you have oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 under Parameters

2. Please ensure the following settings:
* logon to Applications with "XMLPublisher Administrator" responsibility .
* On the admin tab ensure the following settings:
- Use XML Publisher's XSLT processor TRUE
- Enable scalable feature of XSLT processor TRUE
- Enable XSLT runtime optimization TRUE
* Set the Temporary Directory to a valid path
Make sure that the tmp directory is at least 5GB or 20x larger thanlargest data file running
See also <Note 406195.1> XML Publisher Temp Directory.

3. Increase the value of the Concurrent:OPP Process Timeout as follows:
-logon to Applications with "System Administrator" responsibility
- Navigate to Profile -> System
- Query for "Concurrent:OPP Response Timeout".
If the value of the Concurrent:OPP Response Timeout is 120 increase it to 240. (Value * 2)
- Query for "Concurrent:OPP Process Timeout".
Set the value to 10800 sec (3 hours)

4. Determine the heap size per OPP process:

    select DEVELOPER_PARAMETERS from FND_CP_SERVICES 
 
  where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES 
 
  where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'); 

The default is: J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

You can increase the heap space per process to 1024 (or another value like 2048 depending on the java capabilities on the concurrent server)
For example,to increase to 1024:

update FND_CP_SERVICES
set DEVELOPER_PARAMETERS ='J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

Things to be checked for each concurrent program:

A. In XML Publisher Administrator responsibility navigate to Data Definition

Although the scalable feature of the XSLT can be set at the Site level,it is recommended to enable it rather at the Data Definition level for those concurrent programs that are expected to produce large XML data files.
Navigation Path : XML Publisher Administrator responsibility
- query the data definition
- on the View Data Definition page select Edit Configuration button
(similar navigation path for Templates)
The XSLT related properties are stored under Properties > FO Processing
- set 'Use XML Publisher's XSLT processor' to True
- set 'Enable scalable feature of XSLT processor' to True
- set 'Enable XSLT runtime optimization' to True

Note that these property values,set at the Data Definition level,take precedence over values set at the Site level.

B. Under Concurrent > Program > Define,query for Detailed Item Cost Report (XML) thatis receiving the error.
(Only for two step method when not using the OPP)

* In the 'Options' field changed the value to -Xmx1024M.

Once the changes are done please Restart the concurrent manager so that changes take effect.

REFERENCES

BUG:19678099 - DETAILED ITEM COST REPORT COMPLETED WARNING WITH OUTPUT IN XML 原文链接：https://www.f2er.com/xml/294737.html