BI Publisher – Introduction and eText

template customization

Kondaiah Mandadi
Oracle Fusion Payments

June 03, 2020

Agenda
1. BI Publisher introduction
2. Types of templates supported in Payments
3. How to get XML extract
4. XML structure
5. How to check output file for custom template
6. Output formats supported for eText templates
7. Known limitations
8. DFFs supported in FD extract
9. Best practices
10. Demo
11. Q&A
2 Copyright © 2020, Oracle and/or its affiliates
Types of templates supported in Payments

1. eText template
 Fixed Position Based
 Delimiter Based
2. RTF templates
3. XSL templates

3 Copyright © 2020, Oracle and/or its affiliates

How to get XML extract
1. Use IBY_IDENTITY template to create a transaction.
2. IBY_IDENTITY is a seeded XSL template available under My Folders >> Shared Folders >> Financials >> Payments >
Funds Capture Settlement and Authorization templates
3. Download the template.
4. Rename the template.
5. Upload the template.
6. Create a transaction.
7. Output generated will be standard XML extract

4 Copyright © 2020, Oracle and/or its affiliates

Standard XML extract structure
<OutboundPaymentInstruction>
<OutboundPayment>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
</OutboundPayment>
<OutboundPayment>
<DocumentPayable>
</DocumentPayable>
</OutboundPayment>
</OutboundPaymentInstruction>

5 Copyright © 2020, Oracle and/or its affiliates

PPR status report XML extract structure
<PaymentProcessRequest>
<ProposedPayment>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
</ProposedPayment>
<ProposedPayment>
<DocumentPayable>
</DocumentPayable>
</ProposedPayment>
</PaymentProcessRequest>

6 Copyright © 2020, Oracle and/or its affiliates

Positive pay file XML extract structure
<PositivePayDataExtract>
<OutboundPayment>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
<DocumentPayable>
<Line1>
<Line2>
</DocumentPayable>
</OutboundPayment>
<OutboundPayment>
<DocumentPayable>
</DocumentPayable>
</OutboundPayment>
</PositivePayDataExtract>

7 Copyright © 2020, Oracle and/or its affiliates

How to check output file for custom template
Use BI Desktop viewer tool to check the output of custom templates
Download the tool from Transactional Business Intelligence
Direct link to download –
https://www.oracle.com/middleware/technologies/bi-publisher/downloads.html

8 Copyright © 2020, Oracle and/or its affiliates

Output formats supported for eText templates
1. Following output formats are supported –
i. Text
ii. Data (XML)
iii. Data (CSV)
2. When eText template is uploaded, default output will be text.
3. There are option to change it to Data (XML) or Data (CSV)

Note: Data (CSV) is not supported directly. If you want to get the output file in CSV, you have to options –
Option - 1
A. Create a delimiter based BIP template with comma as separator .Upload the template and keep the output file as Text.
B. Create a payment. Payment file will be created with .txt extension. Change the file extension as .csv.
Option - 2
a) Create a delimiter based BIP template. Upload the template and keep the output file as Text.
b) Create a transmission configuration with UCM Upload Protocol. Set the File Name extension as .csv.
c) Attach the transmission configuration to payment process profile.
d) You can also set the file extension at the payment process profile.
e) Create a payment. Navigate to ‘File Import and Export’. The file will be created with .csv extension

9 Copyright © 2020, Oracle and/or its affiliates

Known limitations/issues
1. Payments does not support Payments extract extensibility. You cannot add new elements to be included in the payment file.
2. Support of output file with .xlsx extension.
3. Support of output in Data (CSV)
4. If there is an issue in uploading of template, application will use the default template for generating the payment file.
5. If custom folder is created, Oracle newly seeded templates will not be automatically reflected under custom folder.

10 Copyright © 2020, Oracle and/or its affiliates

DFFs supported in FD extract
Functional Area DFF or GDF Extracted?
Invoice header DFF and GDF Both DFF and GDF
Invoice Line DFF No
Invoice Installment DFF and GDF Both DFF and GDF
Invoice Distributions DFF and GDF No
Payee Bank Account DFF Yes
PPR – Proposed Payment Review DFF Yes
Single payment DFF and GDF Yes
Disbursement Bank Account DFF Yes
Supplier – Profile DFF Yes
Supplier – Site DFF Yes
Payee – Profile DFF Yes
Payee – Site DFF Yes
Payment System DFF No
Payment System Account DFF Yes
Payment Method DFF Yes
Payment Process Profile DFF Yes
Payment Format DFF Yes
Legal Entity DFF Yes
11 Copyright © 2020, Oracle and/or its affiliates
Best practices
1. Use XMLP sever URL for making customizations.
2. Use an existing template to create a custom template
3. Use desktop viewer to verify the custom template
4. Create custom folder by selecting ‘Customize’ option only.
5. Upload custom templates only under custom template.
6. Use a sample XML while customizing a template.
7. Select the correct parameters while uploading the template
8. Select the correct default output.

12 Copyright © 2020, Oracle and/or its affiliates

 Q&A
Questions will be taken via the Q&A panel.
Please send your questions to All Panelists.

13 Copyright © 2020, Oracle and/or its affiliates