« Chart Fonts Main | PO Line Description Quandary »

EText from Kevin

Excellent introduction to the eText template format from Kevin - check it out


ETEXT Templates for Check Printing - Part 1
ETEXT Templates for Check Printing - Part 2
ETEXT Templates for Check Printing - Part 3


Thanks Kevin, its on my long list of to-do's - you beat me!

Comments (4)

Rahul Sharma:

Very Good Info about etext templates

We are receiving an out of memory error when bursting large xml files in 11.5.10 of Oracle. We ar running 5.6.3 of BI Publisher. We have a very large xml file that we are trying to apply a simple eText format to put into .csv format (since it contains too many rows for most of our Excel users).

It is failing the bursting with out of memory exception.

Start bursting process..
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space


I have tried a number of things including:
1) Following settings:
Profile values:
Concurrent:OPP Initialization Delay 30
Concurrent:OPP Process Timeout 300
Concurrent:OPP Response Timeout 1500

Temporary directory --> /usr/tmp
Properties -> FO Processing ->
Use XML Publisher's XSLT processor =TRUE
Enable scalable feature of XSLT processor =TRUE
Enable XSLT runtime optimization =TRUE

2) Increased Timeout to 1000

3) Created the xdo.cfg file and made sure temporary file location was set

4) Tried to set the jvm heap size to 2, 3, and 4 gb and received the same error for 2 and 3 gb. The 4gb actually failed to start the jvm.
a. Login to SQL*Plus as APPS.
b. SQL>update FND_CP_SERVICES set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx4096m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
c. Bounce the concurrent managers.


Thoughts? Do we just need to find a way to bust up the XML into smaller chunks or do you know of a different option?

Paul :

If an etext file is created. How do we call a command line based third party program that will process the created file.

In Rel 11 a printer driver is setup via concurrent program that calls the executable on the command line. How do we do this in R12.


Phil Williams:

Enable scalable feature of XSLT processor =TRUE

should not this be set to FALSE as per note 737311.1

Post a comment