In large implementations with large transaction base in GL, it is very common to get java.lang.OutOfMemoryError" errors in the Output Post Processor log of the Subledger Accounting program Account Analysis Report. This report produces the output in BI Publisher.
To resolve this, you need to implement the steps below
1. Navigate to XML Publisher Administrator responsibility
2. Click Administration->Configuration
General--> Temporary directory- Site alue=/remp ( This directory should be under concurrent progressing tier and must have at least 5GB space)
The three values must be set as below
XML Publisher's XSLT processor set to True
Scalable feature of XSLT processor set to False
XSLT runtime optimization set to True
Now to avoid "java.lang.OutOfMemoryError: Java heap space" in the Output Post Processor's log associated to the Subledger Accounting Program, set the size
update
FND_CP_SERVICES
set
DEVELOPER_PARAMETERS ='J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx5120m'
where SERVICE_ID =
(select MANAGER_TYPE
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
COMMIT ;
The default config in the service table is
select service_handle, DEVELOPER_PARAMETERS, SERVICE_ID
from FND_CP_SERVICES
where DEVELOPER_PARAMETERS is not null
SERVICE_HANDLE | DEVELOPER_PARAMETERS | SERVICE_ID |
CAQCTSVC | C:FND:FNDAQCT |
1051 |
WFMAILER | C:FND:WFMLRGSM |
1032 |
XDPCTRLS | C:XDP:XDPCTRLS |
1020 |
DebugSvc | J:oracle.apps.fnd.cp.gsm.GenCart |
1030 |
FNDCPGSC | J:oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer |
1052 |
OAMGCS | J:oracle.apps.fnd.oam.OAMGSLoaderMain |
1031 |
XDPAMONS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1028 |
XDPQTMRS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1027 |
XDPQFAS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1023 |
XDPQWIS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1022 |
XDPQORDS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1021 |
XDPQFES | J:oracle.apps.xdp.dequeuer.core.QueueService |
1024 |
XDPQMSGS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1026 |
XDPQEVTS | J:oracle.apps.xdp.dequeuer.core.QueueService |
1025 |
XDPSMITS | J:oracle.apps.xdp.sm.example.MyService |
1029 |
FNDOPP | J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m |
1091 |
IEMDPDEV | J:oracle.apps.iem.emta.gsm.IEMDPCART |
1092 |
Comments
We are facing an issue in XML publisher where the OPP fails to generate the excel in case the data is huge.. we ahve around 65 columns in our report and the number of rows exceeds to 70000+ for a single day so when the report is ran for a complete month then it doesnot create the excel and goes in warning.. after seeing this solution i tried using this but i had a clarification that in the second point its mentioned to set the Enable the scalable feature of XSLT Processor to TRUE and in the very next point its mentioned to set as False, what should be the exact Value for this.. And the report we are working upon is the Custom Reoport and not a standard one, based on a single query which fetches the data in 2-3 mins(for a day) but the corresponding program takes around 2 hrs + and still completes in warning .. Please help...
Thanks ,
Ajay Khurana
RSS feed for comments to this post