Objective:
The objective of this material is to provide a beginner's guide( similar to Hello world codes in Java world) to BIP eText report developers. Using this material, any report developer with basic knowledge on BIP can start working on eText Templates.
Introduction
An eText template is an RTF-based template used in generating text output intended for electronic communication. For the same reason, the eText templates must follow very specific format instructions for exact placement of data. At runtime, BI Publisher applies this template to an input XML data file to create an output text file that can be transmitted to a bank or other customer.
eText templates are categorized as Electronic Funds Transfer (EFT) and Electronic Data Interchange (EDI).
An EFT(Fixed Position) is an electronic transmission of financial data and payments to banks in a specific fixed-position format flat file (text).
EDI(Delimiter Based) is similar to EFT except it is not only limited to the transmission of payment information to banks. It is often used as a method of exchanging business documents, such as purchase orders and invoices, between companies. EDI data is delimiter-based, and also transmitted as a flat file (text).
In this series, I am developing BIP reports with Delimiter based and Fixed position templates.
Delimiter Based eText Report:
For creating Delimiter based eText Report, please follow the trailing steps.
1. Use trailing sample data and create a Datamodel.
<DATA_DS>
<G_1>
<Bank>600</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>XYz Indus Valley
bank</Customer_Name>
</G_1>
<G_1>
<Bank>601</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>O'Commerce bank</Customer_Name>
</G_1>
<G_1>
<Bank>602</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>ABC bank</Customer_Name>
</G_1>
</DATA_DS>
2. Create a RTF template file. To begin with, Copy trailing content and save it as Delimetr_eText.rtf.
Hint: Define formatting options...
<TEMPLATE TYPE> |
DELIMITER_BASED |
<OUTPUT CHARACTER SET> |
iso-8859-1 |
<CASE CONVERSION> |
UPPER |
<NEW RECORD CHARACTER> |
Carriage Return |
Hint: Format Data Records Table for DELIMITER_BASED
<LEVEL> |
DATA_DS | ||
<MAXIMUMLENGTH> |
<FORMAT> |
<DATA> |
<COMMENTS> |
<NEW RECORD> |
TableHeader | ||
20 |
Alpha |
'Bank' |
|
1 |
Alpha |
'|' |
|
20 |
Alpha |
'Obligor' |
|
1 |
Alpha |
'|' |
|
20 |
Alpha |
'Customer_Name' |
|
1 |
Alpha |
'|' |
|
<LEVEL> |
G_1 | ||
<MAXIMUMLENGTH> |
<FORMAT> |
<DATA> |
<COMMENTS> |
<NEW RECORD> |
CLRDAta | ||
20 |
Alpha |
Bank |
|
1 |
Alpha |
'|' |
|
20 |
Alpha |
Obligor |
|
1 |
Alpha |
'|' |
|
20 |
Alpha |
Customer_Name |
|
1 |
|
'|' |
|
<END LEVEL> |
G_1 |
<END LEVEL> |
DATA_DS |
3. Create a BIP report with the above Data model (ref point 1) , upload Delimetr_eText.rtf file with template type as eText.
4. Execute the Report. You might expect outcome as below:
5. For detailed steps, kindly go thro the Oracle link https://docs.oracle.com/cd/E10091_01/doc/bip.1013/b40017/T421739T481436.htm.
Fixed Position Based Report:
For creating Fixed Position Based Report, please follow the trailing steps.
1. Use trailing sample data and create a Datamodel.
<DATA_DS>
<G_1>
<Bank>600</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>XYz Indus Valley
bank</Customer_Name>
</G_1>
<G_1>
<Bank>601</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>O'Commerce bank</Customer_Name>
</G_1>
<G_1>
<Bank>602</Bank>
<Obligor>600664421</Obligor>
<Customer_Name>ABC bank</Customer_Name>
</G_1>
</DATA_DS>
2. Create a RTF template file. To begin with, Copy the trailing content in a word document and save it as FixedPositionr_eText.rtf .
XDO file name: Mapping of Payment Format: Date: 4/15/2018
FixedPositionr_eText.rtf US NACHA Payments EDI Format
FIXED POSITION Format Setup:
Hint: Define formatting options...
<TEMPLATE TYPE> |
FIXED_POSITION_BASED |
<OUTPUT CHARACTER SET> |
iso-8859-1 |
<CASE CONVERSION> |
UPPER |
<NEW RECORD CHARACTER> |
Carriage Return |
Hint: Format Data Records Table for FIXED_POSITION_BASED
<LEVEL> |
DATA_DS | ||||||||||
<POSITION> |
<LENGTH> |
<FORMAT> |
<PAD> |
<DATA> |
<COMMENTS> | ||||||
<NEW RECORD> |
TABLE_HEADER | ||||||||||
1 |
15 |
Alpha |
R, ' ' |
'Bank' |
| ||||||
16 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
19 |
15 |
Alpha |
R, ' ' |
'Obligor' |
| ||||||
35 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
39 |
50 |
Alpha |
R, ' ' |
'Customer_Name' |
| ||||||
90 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
|
<NEW RECORD> |
ENTRY_DETAIL_A | |||||||||
|
2 |
90 |
Alpha |
R, ' ' |
'________________________________________________________________________________________________________' |
| |||||
<LEVEL> |
G_1 | ||||||||||
<POSITION> |
<LENGTH> |
<FORMAT> |
<PAD> |
<DATA> |
<COMMENTS> | ||||||
<NEW RECORD> |
TABLE_HEADER | ||||||||||
1 |
15 |
Alpha |
R, ' ' |
Bank |
| ||||||
16 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
19 |
15 |
Alpha |
R, ' ' |
Obligor |
| ||||||
35 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
39 |
50 |
Alpha |
R, ' ' |
Customer_Name |
| ||||||
90 |
3 |
Alpha |
R, ' ' |
'|' |
| ||||||
<NEW RECORD> |
NewLine | ||||||||||
|
2 |
90 |
Alpha |
R, ' ' |
'________________________________________________________________________________________________________' |
| |||||
<END LEVEL> |
G_1 | ||||||||||
<END LEVEL> |
DATA_DS | ||||||||||
3. Create a BIP report with the above Data model (ref point 1), upload FixedPositionr_eText.rtf with template type as eText.
4. Execute the Report. You might expect outcome as below:
5. For detailed steps, kindly go thro the Oracle link https://docs.oracle.com/cd/E10091_01/doc/bip.1013/b40017/T421739T481436.htm.