XDO file name: Mapping of Payment Format: Date: 07/03/2015

ERP_HDFC_UPLOAD.rdf HDFC Payments EFT Format

Format Setup:

Hint: Define formatting options…

<TEMPLATE TYPE> FIXED_POSITION_BASED
<OUTPUT CHARACTER SET> iso-8859-1
<NEW RECORD CHARACTER> Carriage Return

Format Data Records:

Hint: This is the body of the format. Define your format records here.
Create one table for each record or group of records that are at the same level.
For example, RequestHeader is one level, and Payment is another level.
<Comment_Pls_Delete> The file header record should be mapped to the PayerInstrument level. One important point to remember is in 11iX the
sender of the OutboundPaymentInstruction is the same as the 1st party payer; there will be only one 1st party payer for an
OutboundPaymentInstruction. Further, we will have an option in the payment instruction build program. When the option is set it will make one
payment instruction to be built from one payment request only. For US NACHA format the user will set this option. So effectively we will have
only one PayerInstrument in the extract. This is required in order to correctly map the File Header record.
</Comment_Pls_Delete>

<LEVEL> G_RECORD_IDENTIFIER_HEADER
<POSITION> <LENGTH> <FORMAT> <PAD> <DATA> <COMMENTS>
<NEW RECORD> FileHeaderRec
1 1 Alpha TRANSACTIONTYPE
2 1 Alpha ‘,’
4 Alpha BENEFICIARY_CODE
1 Alpha ‘,’
3 25 Alpha BENEF_BANK_ACCOUNT L, ‘0‘
1 Alpha ‘,’
4 20 Number, INSTRUMENT_AMOUNT L, ‘0‘
###.00

1
 1 Alpha ‘,’
40 Alpha BENEFICIARY_NAME
5 9 Alpha ‘,,,,,,,,,’
20 Alpha BENEFICIARY_NAME
1 Alpha ‘,’
20 Alpha PAYMENT_DETAILS_1
9 Alpha ‘,,,,,,,,’
8 10 Date,DD/ SYSDATE
MM/YYYY
2 Alpha ‘,,’
9 15 Alpha BENEF_BANK_IFSC_CODE L, ‘0‘
1 Alpha ‘,’
1 Alpha ‘,’
1 Alpha ‘,’
50 Alpha BENEF_MAIL_ID
<END LEVEL> G_RECORD_IDENTIFIER_HEADER