Sub Templates In Oracle BI

There May be scenarios that where and when we have some part of XML data needs to be represent in fixed format and remaining XML data needs to be represent in multiple formats based on some conditions (let us say for each country specific remaining data XML data needs to be processed) in that case  once after registering the concurrent program (either rdf or Data template type) we can create one Default data template for the concurrent program  and other multiple sub templates for each country specific .

  Create one Default or main Data template for concurrent program along with the multiple sub templates for the same data definition in oracle apps.

 We can create sub templates in the oracle apps by selecting sub template option as "Yes" while creating template using Xml Publisher Administrator responsibility.

 While creating the main or Default Data template RTF file first we have to import all the sub templates that are going to be called in this as below.

 <?import:xdo://XXPIC.TEST_FRT.en.us?>

 xxpic ->Application Shortname
TEST_FRT-> Subtemplate Code.

 After Importing all required sub templates  next we have to design the layout that is common in all cases.

 Now based on conditions we have to call different sub templates.

 <?IF:SUBTEMPLATE='TEST_FRT'?> <?call-template:TEST?> <?END IF?>
<?IF:SUBTEMPLATE='TEST_FRT2'?><?call-template:TEST1?><?END IF?>

 Here TEST and TEST 1 are Sub template Names

 This concludes the creation of the Main RTF template.

 Now in each Sub template we have to design the layout between below tags.

 <?TEMPLATE:TEST?>
----Layout design---
<?END TEMPLATE?>

 TEST : Sub template Name
Please See this Oracle white Paper on Sub templates





Comments

Post a Comment

Popular posts from this blog

Queries For Oracle Interface Errors Records.

Below are the queries to get the error records information while processing interface data. AP Invoices:   SELECT    airl.last_update_date process_date,    HU.NAME,   nvl(ail.invoice_line_id,aii.invoice_id) process_id,   'AP' module,   'Import AP Invoice' interface_name,   aii.source source,   NVL(SUBSTR( ail.dist_code_concatenated,1,instr(ail.dist_code_concatenated,'.',1,1)-1),'ALL') company,   'ERROR' status,   ail.line_type_lookup_code ,   airl.parent_table ,   ail.description ,   NVL(ail.distribution_set_name,dist_code_concatenated) ,   pvsa.vendor_site_code ,   listagg(NVL(airl.reject_lookup_code,'AP_INV_ERROR') ,';') within group (order by NVL(airl.reject_lookup_code,'AP_INV_ERROR')) error_code,   listagg(flv.meaning,';')  within group (order by NVL(flv.meaning,'AP_INV_ERROR'))error_summary,   NULL error_details,   pv.vendor_name ,   pv.segment1 ,   aii.invoice_amount,   aii.i
Read more

Customising PO Output For Communication Report in Oracle Purchasing

Image
PO Print PDF Report: Oracle EBS provided  a standard functionality to print the PO report directly from the PO form itself by clicking tools menu and view PDF option. Once we select that option output will be rendered in PDF format in the browser instantly. Internally it will run the concurrent program 'PO Output For Communication'. This concurrent program is of JAVA type which will uses the seeded package  'PO_COMMUNICATION_PVT'  for generating the XML data and later this XML data will be processed and formatted by using the XSL template of data definition 'Standard Purchase Order Data Source' in case of standard PO's. Oracle by default will provide one standard BI publisher template for this. In case if we want to have custom layout for this report we can build a new template for the same data definition and this template has to be used while doing the setup for PO Document types. Creating Custom Template and Setup this for PO Document type: To c
Read more

Oracle APPS Useful Queries

                       ACCOUNT PAYABLES Payable Open Interface Rejection:   SELECT ail.* FROM AP_INVOICES_INTERFACE ai ,   ap_invoice_lines_interface ail ,   ap_interface_rejections AIR WHERE ai.GROUP_ID='EO_AUG-13_010813_443' AND ai.status    ='REJECTED' AND ai.invoice_id=ail.invoice_id   --and ail.dist_code_concatenated='66810-00-999-00000000-00000000-00000-FI100' AND air.parent_id = DECODE(air.parent_table,'AP_INVOICES_INTERFACE',AI.INVOICE_ID,'AP_INVOICE_LINES_INTERFACE',ail.invoice_line_id,NULL) ORDER BY 2; AP Invoices Query: /*+INDEX (AP_INVOICES_ALL [XXDG_TEST]) */ SELECT  apia.invoice_id,        alc.displayed_field "Invoice Type",        apia.invoice_num "Invoice Number",        apia.invoice_date "Invoice Date",        apia.gl_date   "Invoice GL Date",        nvl(apia.VOUCHER_NUM,doc_sequence_value)"Voucher Number",        apia.description inv_Description,  
Read more