Configure the Account Analysis Report in SLA/GL : In R12 the Account Analysis Report in applications Subledger Accounting and

General Ledger, have been completely written as XML Publisher programs. The data is extracted and generated into XML format using a Data Template extract vi a the JAVA program XDODTEXE. The layout is then generated using the Output Post Processor concurrent manager. The problem for users of these reports is that they generate very large data se ts so the Release 12 instance needs to be configured to handle these large progr ams. A. Set the Scalable Option to on for these programs. This prevents this error in the Subledger Accounting program's log: Calling XDO Data Engine... ****Warning!!! Due to high volume of data, got out of memory exception...*** ****Please retry with scalable option or modify the Data template to run in scal able mode...*** 1. As System Administrator: Navigate to Concurrent->Program->Define. 2. Query up the report: Account Analysis Report (do this for both the General Ledger and the Subledger Accounting program defini tions). 3. Add a parameter: ScalableFlag. Value set should be yes_no Default value should be Y. Select checkboxes Enable and Required. Do not select the check box Displayed, or users could turn this off at runtime. Token needs to be ScalableFlag (this is a case sensitive value). B. Configure the XML Publisher Administrator Configuration settings. This prevents "java.lang.OutOfMemoryError" errors in the Output Post Processor l og associated to the Subledger Accounting program. 1. As XML Publisher Administrator navigate to Administration->Configuration. 2. Under Temporary Directory pick a temporary file location on your concurrent p rocessing node. This should be at least 5GB or 20x larger than largest XML data file you generate. 3. Under FO Processing: Use XML Publisher's XSLT processor set to True Enable scalable feature of XSLT processor set to False Enable XSLT runtime optimization set to True C. Configure the Output Post Processor's JVM. These steps set the JVM to 2GB, depending upon your server's size you might find 3 GB (-mx3072m), 4GB (-mx4096m) or even 5GB (-mx5120m) is a better value. This setting prevents the error "java.lang.OutOfMemoryError: Java heap space" in the Output Post Processor's log associated to the Subledger Accounting Program. 1. Login to SQL*Plus as APPS. 2. SQL>update FND_CP_SERVICES set DEVELOPER_PARAMETERS = 'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m' where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'); 3. Bounce the concurrent managers.