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.
|
Bursting-EBS integration where layout template and xlf stored in Template Manager repository. Use the
XDO protocol to define the template location.
|
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