Sample Templates for eText BI Publisher Reports (Delimiter & Fixed Position)

Introduction to eText BI Publisher Reports

Oracle BI Publisher (BIP) provides eText report templates to generate text-based output files such as .txt, .dat, or interface files required for integrations with external systems.

Unlike PDF or Excel outputs, eText reports are mainly used when:

• Data must follow a specific layout

• Files are consumed by external payroll, banking, or legacy systems

• Strict formatting rules (delimiter or fixed length) are required

In this blog, we’ll cover:

• What eText BI Publisher reports are

• how to create eText report in BI Publisher

• Differences between Delimiter-Based and Fixed Position-Based eText

• BI Publisher eText report example

• how to create fixed position eText report

• common errors in BI Publisher eText report

---

Difference Between Delimiter & Fixed Position eText

Delimiter VS Fixed Position eText

You can see step by step video to develop eText BIP Report using this Link

---

🔹 Sample 1: Delimiter-Based eText Template

This template generates output with values separated by a delimiter (for example, |).

You can see step by step video to develop eText BIP Report using this Link

<TEMPLATE TYPE>	DELIMITER_BASED
<OUTPUT CHARACTER SET>	iso-8859-1
<CASE CONVERSION>	UPPER
<NEW RECORD CHARACTER>	Carriage Return

 

<LEVEL>	DATA_DS
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	TableHeader
20	Alpha	'Person Id'
1	Alpha	'|'
20	Alpha	'Title'
1	Alpha	'|'
20	Alpha	'First Name'
1	Alpha	'|'
20	Alpha	'Last Name'

 

<LEVEL>	G_1
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	CLRDAta
20	Alpha	PERSON_ID
1	Alpha	'|'
20	Alpha	TITLE
1	Alpha	'|'
20	Alpha	FIRST_NAME
1		'|'
20	Alpha	LAST_NAME
<END LEVEL>	G_1

 

<END LEVEL>

DATA_DS

 This format is useful when the target system expects delimiter-separated text files.

⭐ HDL Template for Personal Payment Method in Oracle Fusion HCM (PersonalPaymentMethod.dat + Direct Deposit Example)

 HDL Template for Personal Payment Method in Oracle Fusion HCM

PersonalPaymentMethod.dat Step-by-Step Guide (Direct Deposit Example)

Personal Payment Method is used in Oracle Fusion HCM Payroll to define how an employee receives salary payments, such as:

• Direct Deposit (Bank Transfer)

• Check

• Cash (based on country setup)

Instead of manually entering payment methods for each employee, you can load them in bulk using HCM Data Loader (HDL).

This blog explains how to load Personal Payment Method details using:

📌 PersonalPaymentMethod.dat

---

✅ Prerequisites (Mandatory)

Before loading Personal Payment Method details, ensure the following are already loaded:

1) Bank and Bank Branch

You must load:

• Bank.dat

• BankBranch.dat

2) External Bank Account

You must load:

• ExternalBankAccount.dat

⚠️ If these are missing, the PersonalPaymentMethod HDL will fail.

Links : 

1. Bank and Bank Branches data should be loaded. Click here to find the sample bank details.  

2. External bank Account should be loaded. Click here to find the sample file.  

Video Link - You can see step by step video to load Personal Payment Method Details using this Link

---

✅ HDL File Used

For Personal Payment Method, use:

📌 PersonalPaymentMethod.dat

---

✅ Business Object Used

• PersonalPaymentMethod

This object creates the payment method record for the assignment.

---

📌 Sample HDL Template (Personal Payment Method)

1) PersonalPaymentMethod HDL Example (Direct Deposit)

METADATA|PersonalPaymentMethod|SourceSystemOwner|SourceSystemId|LegislativeDataGroupName|AssignmentNumber|PersonalPaymentMethodCode|EffectiveStartDate|PaymentAmountType|Amount|Percentage|ProcessingOrder|OrganizationPaymentMethodCode|BankName|BankBranchNumber|BankCountryCode|BankAccountNumber|BankAccountType

MERGE|PersonalPaymentMethod|XXTEST|XXTEST_PAYMETHOD2|US Legislative Data Group|XXTEST_ASSIGN2|XXTEST_PAYMETHOD2|2021/04/19|P||100|1|Direct Deposit|American Bank|000000123|US|3456|Checking