« Bursting: Conditional delivery | Main

Bursting & Translation

I see this question very often. Yes, bursting supports the translation and the implementation depends on the flavor. Lets go through the different scenario through these examples

Using bursting control file where layout templates and xlf files are on file system. In this
scenario, set the translation attribute under template section to xlf file path.


<xapi:document key="${EMPNO}"
output="c:\burst\sample\${EMPNO}_${ENAME}.pdf"
output-type="pdf" delivery="123">
<xapi:template type="rtf" locale="de-DE"
location="d:\burst_test\deptSummary.rtf"
filter=".//EMPLOYEE [locale='de-DE']"
translation="d:\burst_test\translation\deptSummary_de_DE.xlf" />
<xapi:template type="rtf" locale="en-US"
location="d:\burst_test\deptSummary.rtf"
filter=".//EMPLOYEE [locale='en-US']"
translation="d:\burst_test\translation\deptSummary_en_US.xlf" />

<xapi:template type="rtf" locale="ja-JP"
location="d:\burst_test\deptSummary.rtf"
filter=".//EMPLOYEE [locale='ja-JP']"
translation="d:\burst_test\translation\deptSummary_ja_JP.xlf" />
</xapi:document>




Bursting-EBS integration where layout template and xlf stored in Template Manager repository. Use the
XDO protocol to define the template location.


<xapi:document key="${TRX_NUMBER}" output="${TRX_NUMBER}"
output-type="pdf" delivery="file1"> <xapi:template type="rtf" locale=""
location="xdo://AR.RAXINV.${language}.${territory}/?getSource=true"
translation="" filter="" />
</xapi:document>


Based on Template code, Application Code, Language and Territory, process extracts the
translated layout from Template Manager repository.

In Enterprise release, Bursting is based on SQL query that we define in Bursting criteria page
of the Report. The Translation is based on the Locale value in SQL Query.

SELECT
CUSTOMER_ID KEY,
CST_TEMPLATE TEMPLATE,
TMPL_TYPE TEMPLATE_FORMAT,
CST_LOCALE LOCALE,
CST_FORMAT OUTPUT_FORMAT,
CST_DEL_CHAN DEL_CHANNEL,
CST_EMAIL PARAMETER1,
'accounts.receivable@oracle.com' PARAMETER2,
'bip-collections@oracle.com'PARAMETER3,
'Your Invoices' PARAMETER4,
'Hi'||CUST_FIRST_NAME||chr(13)|| 'Please find attached your
invoices.' PARAMETER5,
'true' PARAMETER6,
'donotreply@nowhere.com' PARAMETER7
FROM CUSTOMERS

Sample Control files are available here

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mt/mt-tb.cgi/12644

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on June 28, 2009 12:43 AM.

The previous post in this blog was Bursting: Conditional delivery.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle