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

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

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


Solution:




The Oracle E-Business Suite Release 12 includes a new version of the Account Analysis Report as part of the Subledger Accounting and General Ledger application, implementing the XML Publisher technology for data gathering as well as report generation.
The data is extracted and generated into an XML format using a Data Template, extracted via the Java program XDODTEXE. Subsequent to that, the layout is then generated using the Output Post Processor (OPP) concurrent manager.
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: Yes
 Select check boxes 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 application 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.
o As XML Publisher Administrator navigate to Administration->Configuration.
o 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
o Under FO Processing, set:
 Use XML Publisher's XSLT processor set to True
 Enable scalable feature of XSLT processor set to False (see #4 below),
 Enable XSLT runtime optimization set to True

3. Configure the Output Post Processor's JVM. These steps set the JVM to 2GB.
This setting prevents the error "java.lang.OutOfMemoryError: Java heap space"
in the Output Post Processor's log associated to the Subledger Accounting Program.
Since EBS uses a 32-bit JRE using values greater than 2GB is not going to help.
Addressable memory maxes out between 1GB and 2GB for 32-bit JRE.
o Login to SQL*Plus as APPS.
o 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');
o Bounce the concurrent managers.

4. With the addition of Patch 7599031 XML PUBLISHER SUM(CURRENT-GROUP()) FAILS, the FO Processing option Enable scalable feature of XSLT processor can be safely set to True at the Template level (for large reports), enabling improved JAVA heap utilization.
We still recommend 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.
5. Apply Patch 7687414 REHOSTING XDOPARSER 10.1.0.5 WITH FIX FOR BUG 7586025, 7339075. This patch upgrades the Java Developers Kit (XDK) which is used by XML Publisher for sorting.
6. Test the reports.


References:


How to Configure the Account Analysis Report in Release 12 for Large Reports [ID 737311.1]

Get Oracle Certifications for all Exams
Free Online Exams.com