Unable to Burst e-mail because Template not found

Question

Hello,
I am working on getting a bursting control file set up to e-mail some invoices out and can't seem to get past a hurdle where the publisher cannot find the template file to use.
Here is the Control file info:
?xml version="1.0" encoding="UTF-8" ?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/LIST_G_ORDER_BY/G_ORDER_BY/LIST_G_INVOICE">
<xapi:delivery>
<xapi:email id ="123" server="SFO1001EX02.NA.CORP.YR.COM" port="25"
from="[email protected]" reply-to="[email protected]">
<xapi:message id="123" to="[email protected]" cc="" attachment="true"
content-type="text/html" subject="Invoice Number: ${TRX_NUMBER}">Please
see attached Invoice File: ${TRX_NUMBER}</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output-type="pdf">
<xapi:template type="rtf" location="xdo://LANSELUKINV2.EN.US"/>
</xapi:document>
</xapi:request>
</xapi:requestset>
It is actually delivering an e-mail, but with no attachment. The log file indicates:
XML/BI Publisher Version : 5.6.3
Updating request description
Retrieving XML request information
Preparing parameters
Set Bursting parameters..
Start bursting process..
[012109_022849394][][EXCEPTION] The URL ( xdo://LANSELUKINV2.EN.US ) is invalid.
[012109_022849397][oracle.apps.xdo.batch.BurstingProcessorEngine][EXCEPTION] java.lang.NullPointerException
     at com.sun.java.util.collections.Hashtable.put(Hashtable.java:381)
     at oracle.apps.xdo.batch.BurstingProcessorEngine.validateTemplateLocation(BurstingProcessorEngine.java:3394)
Can anyone help me out?
Thanks in advance.

Answer 1

I can't seem to find any examples in Oracle documentation specifically about setting the location="xdo://....". The closest thing I can find is in the XMLP 5.6.2 user guide on page 2-117 (pdf page 139). The syntax for getting a template from XML Publisher in EBS is:
location="xdo://APPCODE.TEMPLATE_CODE.lang.TERR"
Example: xdo://SQLAP.APXT7F99P.en.US
The "burst_template_location" column of this SQL will assemble the location name for you (assuming you have previous run a XMLP request with this data definition):
SELECT distinct
NVL (r.description, cp.user_concurrent_program_name) prg_desc
,xds.application_short_name || '.' || xds.data_source_code || '.' || lower(fl.iso_language) || '.' || ft.territory_code as burst_template_location
,cp.concurrent_program_name
,cp.template_appl_short_name
,cp.template_code
,r.nls_language
,r.nls_territory
,r.nls_codeset
,r.printer
,cp.output_print_style
,xds.application_short_name
,xds.data_source_code
FROM fnd_concurrent_requests r
,fnd_concurrent_programs_vl cp
,xdo_ds_definitions_b xds
,fnd_languages fl
,fnd_territories ft
WHERE
r.program_application_id = cp.application_id
AND r.concurrent_program_id = cp.concurrent_program_id
AND xds.application_short_name = (SELECT application_short_name
FROM fnd_application
WHERE application_id = cp.application_id)
AND xds.data_source_code = cp.concurrent_program_name
AND r.output_file_type = 'XML'
and r.nls_language = fl.nls_language
and r.nls_territory = ft.nls_territory
and xds.data_source_code like '%LANSELUKINV2%'
ORDER BY prg_desc