How to Configure the Account Analysis Report in Release 12 for Large Reports

A typical problem for application user's of these reports is the fact that it is likely to fail when generating the report for very large data sets so the environment needs to be configured properly to handle that.

1. Set the Scalable Option to on for these programs.
--> This prevents the following 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 scalable mode...***
The scalability option is set by performing these steps:
1. As System Administrator: Navigate to Concurrent->Program->Define
2. Query up the report: Account Analysis Report
3. Add a parameter named ScalableFlag:

* Value Set: yes_no
* Default Value: 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).

Complete these steps for both the General Ledger and the Subledger Accounting concurrent program definitions.

2. Configure the XML Publisher Administrator Configuration settings. This prevents "java.lang.OutOfMemoryError" errors in the Output Post Processor log associated to the Subledger Accounting program.

* As XML Publisher Administrator navigate to Administration->Configuration.
* Under Temporary Directory pick a temporary file location on your concurrent processing node. This should be at least 5GB or 20x larger than largest XML data file you generate
* Under FO Processing, set:

o Use XML Publisher's XSLT processor set to True
o Enable scalable feature of XSLT processor set to False
o Enable XSLT runtime optimization set to True

3. 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.

* Login to SQL*Plus as APPS.
* 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'); * Bounce the concurrent managers.

4. Test the reports

How to Get the Forms,PLL,LDT,Reports Version from O/S level

Login in as the user who owns the application file system,

1. Forms

When considering forms one needs to get the version from $JA_TOP and $AU_TOP as well.

Navigate to cd $JA_TOP/forms/US

Execute command --- > strings -a grep '$Header'

Example

strings -a JAINPORE.fmx grep '$Header'

Navigate to cd $AU_TOP/forms/US

Execute command --- > strings -a grep '$Header'

Example

strings -a JAINPORE.fmb grep '$Header'

2. Reports

Navigate to cd $JA_TOP/reports/US

Execute command --- > strings -a grep '$Header'

Example

strings -a JAINARDR.rdf grep '$Header'

3. Library files

Navigate to cd $AU_TOP/resource

Execute command --- > strings -a grep '$Header'

Example

strings -a CUSTOM.pll grep '$Header'

4. LDT

Navigate to cd $JA_TOP/patch/115/import/US

Execute command --- > strings -a grep '$Header'

Example

strings -a jai115cp_F.ldt grep '$Header'