R12 How To Create / Modify Payment Formats
IBY_PAY_CHK_STANDARD_1? [ID 562806.1]
Modified 25-MAY-2008 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
References
Applies to:
Oracle iPayment - Version: 12.0
Oracle Payables - Version: 12.0.0
Information in this document applies to any platform.
Goal
The goal of this article is to provide information about XML publisher .
Solution
Financial institutions, payment systems, and/or countries have specific formatting
requirements for funds capture transactions, funds disbursement transactions, payment
documents, and payment-related reporting.
Formats are created within Oracle Payments to represent these requirements. Each format
in Oracle Payments corresponds to one Oracle XML Publisher template. Oracle
Payments uses Oracle XML Publisher templates to format funds capture and funds
disbursement transactions according to the formatting requirements of specific financial
institutions or payment documents.
Some seeded payment formats shipped with standard product are
Name Code
Standard Check Format IBY_PAY_CHK_STANDARD_1
US NACHA Generic Format IBY_PAY_EFT_NACHA_US
A basic business requirement is to modify / create a payment format as the seeded ones
will not suffice.
1. XML data extract (Nothing but data wrapped in XML tags)
2. XML Publisher template (A word file with extension .rtf dictating how data
pulled from XML extract should be arranged)
3. Oracle BI Publisher Desktop (Software which plugs into Microsoft Word and
helps us to design the template)
Note:- This software can be downloaded from the following link:
http://bipublisher.us.oracle.com/bin/XMLP_Desktop.zip
Here goes the logic behind how XML publisher combines all these elements to create
payment format
Payment format is generated by XML Publisher engine which combines XML Data
extract and XML Publisher template at run time to generate the payment format.
Let's have a look at the standard check format
Follow the below navigation from seeded AP Menu
Query for standard Check format and click on Update icon
Here we can see what are the elements this format is comprised of ie. Data extract and
XML Publisher Template.
On pulling these elements to have a closer look on it.
1. Rich Text Format (.rtf) Template
On clicking on download button you can able to save this file to your system.
On opening this RTF(Rich Text File) on MS Word you can able to see the arrangement
of fields.
These fields are nothing but data mapped to XML data extract.
Note:-
On Left top corner we can see the Oracle BI Publisher Plug-in (Data - Insert - Preview -
Tools - Help)
2. XML Data Extract
Trickiest part is to get the data extract.
a) Query the 'Standard Check Format' and choose the XML Publisher Template to
'Extract Identity'.
b)Query the the concurrent program 'Format Payment Instructions' from System
Administrator responsibility and change the output of it from pdf to XML.
On creating a Quick payment using a 'Payment Process Profile' and 'Payment Document'
using this modified 'Standard Check Format' will trigger 'Format Payment Instructions'
program which will give the required XML data extract.
The output of this concurrent program is the XML Data extract which you are looking for
You may download the extract from the following link to create your own template:
XML Data Extract
Now the real business need..
Instead of the conventional output seen below
We want the output of the payment format to be as below
How to achieve this mission?
At this point you will appreciate the beauty and robustness of BI Publisher (Previously
known as XML Publisher)
"Oracle XML Publisher is a template-based publishing solution delivered with the Oracle
E-Business Suite. It provides a new approach to report design and publishing by
integrating familiar desktop word processing tools with existing E-Business Suite data
reporting. At runtime, XML Publisher merges the custom templates with the concurrent
request data extracts to generate output in PDF, HTML, RTF, EXCEL (HTML), or even
TEXT for use with EFT and EDI transmissions"
Our mission can be made easy by just creating an RTF template with the help of 'Oracle
BI Publisher Desktop' software plug-in and the XML Data extract gathered before and
attaching this RTF template to the payment format will do.
The RTF template designed to make our mission possible can be downloaded from the
following link:
RTF Template
Open this template in MS Word and add / delete fields in 2 easy steps
1. Load the XML data extract - Navigation (Data - Load XML data)
2. Insert / Delete fields - Navigation(Insert - Fields)
You may visit
http://bipublisher.us.oracle.com/docs/guides/ReportingStandards/index.htm for more
information on editing the templates and demos.
References
NOTE:316447.1 - About Oracle XML Publisher Release 5.5
NOTE:465389.1 - R12 Create Or Modify A Payment Format Using XML Builder
Attachments
Conc (94.14 KB)
Conc2 (34.58 KB)
Conv (12.46 KB)
E2 (115.99 KB)
Extract (48.79 KB)
Log (54.27 KB)
Navigation from AP responsibility (90.11 KB)
Out (22.72 KB)
RTF (310.98 KB)
Standd (70.52 KB)
Template1 (93.91 KB)
Template2 (88.88 KB)
Template3 (74.03 KB)
Word (102.06 KB)
XMLE (11.87 KB)
Related
Products
• Oracle E-Business Suite > Financial Management > Procure to Pay > Oracle
Payables
• Oracle E-Business Suite > Financial Management > Procure to Pay > Oracle
Payments
