hdfc sap payment extractor user manual ver 1

HDFC Bank

SAP Payment Extractor Module – User Manual

Prepared by: L&T Infotech

Document Number: OTC-2009-0001

HDFC SAP Payment Extractor User Manual

Table of contents

1.0 About SAP Payment Extractor 4

2.0 Payment Run Flow 4

3.0 Technical Diagram 5

4.0 Client Details 5

5.0 SAP Payment Extractor Details 65.1 Payments Supported:- 75.2 Automatic Payments 95.3 Manual Payments 155.4 Error Management 205.5 Reverse upload 275.6 Administrative features 295.7 Re-extraction of payment documents 335.8 Uploading Mapping Data 365.9 Encryption utility 385.10 File format 39

6.0 Configuration and settings for Payment extractor Tools 45

7.0 Configurations based on Questionnaire 52

8.0 Unit Test Plan 54

L&T Infotech - Confidential of 58


Record of Release

Author Jignasa Desai/Harshad S.

Reviewer Sameer Godbole

Date of Release 23-Jan-2012



1.0About SAP Payment Extractor

SAP payment interface facilitates the bank’s clients to automate vendor/customer

payments. It eases the data flow between client’s SAP system and Bank application,

thereby reducing the payment processing time. The interface extracts the payment

data on the presentation server in Encrypted format. The data is then uploaded to Bank

portal to outsource Cheque / DD printing and EFT transfers. It requires Minimum user

intervention for multiple payment runs with multiple payment methods

2.0Payment Run Flow



3.0Technical Diagram

4.0Client Details

Client Name : < Update at the time of implementation>

Client functional Consultant Name : < Update at the time of implementation> Client SAP Version : < Update at the time of implementation>



5.0SAP Payment Extractor Details

SAP Payment extractor has the following main features:-1. Payments Supported 2. Automatic payment 3. Manual Payment4. Reverse Upload5. Configuration/Custom tables6. Re-extraction of payment documents7. Uploading mapping data8. Encryption utility9. File format

SAP Payment Extractor Main Menu

T-CODE in SAP for Payment Extractor interface - ZHDFC



5.1 Payments Supported:- Following payment modes are generally supported in the payment extractor:- 1) DD (D) – Demand Draft, 2) CHK (C) - Customer Cheques, 3) NEFT (N) – National Electronic Fund Transfer, 4) RTGS (R) – Real Time Gross Settlement, 5) A2A (I) - (HDFC to HDFC Transfers)

5.1.1 Checklist for different payments:-

1) Cheque (CHK) & Demand Draft (DD) payments a) Cheque number (Only for CHK payments):-

HDFC would generate the Cheque Number series in advance. It becomes Essential to maintain the same in ERPs House Bank and provide the same on sequential



Basis for CHK payment method.

b) Print Location and Payable at location:- Print Location: - This is the HDFC location where cheque needs to be printed. Print Location code generated in transaction is basically picked based on vendor city in the Vendor master. Payable at location: - This is the location where the DD’s needs to be payable at. The Payable at location code is also generally picked based on the vendor city maintained in Master.SAP Payment Extractor Implementation Guidelines 2) NEFT & RTGS payments a) Amount limit – applicable only for RTGS The Minimum threshold for a RTGS transaction is INR 200000 (current RBI limit). In case if a RTGS transaction which has:- A - Amount less then INR 200000, and, B – IFSC not starting with “HDFC” The extractor will automatically convert the payment method to NEFT.

b) Beneficiary Account Number: - It becomes mandatory to maintain account number of Vendor for all electronic fund transfers. (NEFT, RTGS AND A2A transfer) C) Beneficiary Bank Routing Code: - In case of NEFT and RTGS payments, IFSC code is Mandatory and hence needs to be maintained in vendor master. d) For A/C to A/C transfer, if the first 3 characters of IFSC code is ‘HDF’ the payment method automatically converted to internal transfer.

Refer below screenshot for fields in vendor master where bank details needs to be maintained for Electronic fund transfer payments.



5.2 Automatic Payments Process flow: -

5.2.1 The payments for due invoices will have to be made through Automatic payment

Transaction (F110) (this is just a sample screen shot. Not actual data) Screenshot for payment made through F110



5.2.3 Once payment run is done, user will input basic parameters in Auto payment extractor interface and generate the payment file Input Parameters a) Company Code b) House Bank



c) House bank account id d) Run date (for F110) e) Run Id (Identification)

5.2.4 Based on the selection parameters the respective proposal data will be extracted in specified format in encrypted form to a txt file either at PC level or server level at a designated path: (e.g. C:\HDFCBANK\IMPORT\).Processed path (e.g. C:\HDFCBANK\PROCESSED\) would be used for archiving the previous payment file extracted .The import folder would always contain the latest output file extracted. Every time extractor is executed for generating output payment file, old processed file would be moved to processed folder.

Whenever the payment extractor is executed after passing the required parameters, a report would also be generated displaying details of successful transactions as well as transactions which got rejected (transactions which were rejected due to validation errors).

Sample screenshot of the payment extractor after successful execution.



Below are sample screenshots of the folder where the encrypted payment file got extracted.



When no data is available for given selection parameters or if all transactions are rejected due to validation error following message comes followed by report. (Sample screenshots)



5.2.5. The extracted File needs to be uploaded (manually or automated) into HDFCbank web portal (HDFCDIRECT) for payment processing.

5.2.6. Test Run feature:-



If test run checkbox is marked, then based on the selection parameters only a report would be displayed containing the payment details of the transaction and no encrypted output file would be generated .The report can be generated n number of times and it doesn’t create a log entry in the custom log table.

5.3 Manual Payments



5.3.1 Payments can be posted manually in SAP using following transactions:-

a) F-53 / F-58 (Payment with print out: Header Data) b) F-48 (Advance/Down Payments) Process:- 1) User will create invoices due for vendors/customers 2) The payments for the due invoices are made using above transactions T-code – F-53 This screen shot shows just sample data. This is not the actual data of the client system.



T-code – F-58 This screen shot shows sample data .this is not actual data of client system

Note: In case of down payments through F-48, A DPR (Down payment Request) would be raised for the vendor initially through F-47 before making payment through F-48. This is sample data screen shot. This is not an actual client system test data.



3) Payment document number would be generated containing the payment details for the vendor/customer

5.3.2. Once the payment document number is generated, user will enter the basic input parameters in manual payment interface to extract payment file containing payment details

Input Parameters for Manual Extractor: - a) Company Code b) House Bank c) Account Id d) Fiscal Year e) Payment Document Number (Clearing Document) f) Payment Method



5.3.3. Based on the selection parameters the respective payment data will be extracted in specified format in encrypted form to a txt file either at PC level or server level at a designated path: (E.G. C:\HDFCBANK\IMPORT\.) and similar to Auto payment extractor ,a report would be generated based on the selection parameters displaying transaction details(both successful and invalid).



5.3.4. Test Run: The procedure for test run is the same as that of Auto payment extract program

5.4 Error Management Common validations implemented in payment extractor based on which error could happen during Execution if not properly maintained:-

1) Payment Amount (should not be less than zero or equal to zero) 2) Cheque Number (valid for chk’s, if cheque series pre-assigned by bank) 3) IFSC code (mandatory for NEFT/RTGS/A/C to A/C (if no separate payment type)) 4) Correct IFSC code (should be of 11 digits) 5) Beneficiary Account number (for NEFT/RTGS/A/C to A/C) 6) Print location can’t be blank (for CHK & DD) 7) Payable at location can’t be blank (for DD) 8) Delivery method can’t be blank (for CHK & DD) 9) Special character validations



(i) Following is the current list of special characters which are allowed in a transaction in Output file.

S No. Fields Allowed Characters

1 Start Indicator ~

2 Program Run date Date Format DD/MM/YYYY

No other Date format/ value allowed

3 Run Identification

Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

4 Paying Company Code Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

5 Payment document no. Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9



6 Amount

Numeric Characters

0 to 9

Special Characters

. (dot)

7 Currency Alphabetical Characters

A to Z(upper case)

a to z (lower case)

8 Payment method (Cheque, DD, Account Trsf., RTGS or NEFT )


A to Z(upper case)

a to z (lower case)

9 Vendor Account No/Code Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf

10 Title of the Vendor Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters



/ - ? : ( ) . , ' + SPACE CrLf

11 Beneficiary name of the Vendor (Name 1 & Name 2) Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

12 Beneficiary name Of the Vendor (Name 3 & Name 4) Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

13 Address 1 of the Vendor Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf


A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf


A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf



16 Address 4 (District) Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf

17 Address 4 – (City) Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

/ - ? : ( ) . , ' + SPACE CrLf

18 Address 5 – (Postal code)

Numeric Characters

0 to 9

19 House Bank (Bank in SAP) Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

20 HB Account ID (Bank in SAP) – Client Code Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

21 Value date Date Format



DD/MM/YYYY


22 Instruction Date Date Format DD/MM/YYYY


23 Mode of Delivery Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

24 Cheque No

Numeric Characters

0 to 9

25 DD Payable location Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

26 Print Location Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

27 Beneficiary Account Number (For RTGS ) Alphabetical Characters



A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

28 IFSC Code Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

29 Beneficiary Bank Name Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

30 Beneficiary Account Type Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

31 Beneficiary email id Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

- @ . _



Description:

1 Header –1 ~H

2 Client Code Alphabetical Characters

A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

3 Payment Document No.


A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

4 Document Date Date Format DD/MM/YYYY


Detail Record :

1 Start indicator ~D

2-9 Title 1 to 8 : (Value of the title to be printed on the advice)


A to Z(upper case)

a to z (lower case)

Numeric Characters

0 to 9

Special Characters

: / - . Colon to be used as separator ONLY

10-16 Text 1 to 7 Alphabetical Characters

A to Z(upper case)



a to z (lower case)

Numeric Characters

0 to 9

5.5 Reverse uploadReverse Upload Program is basically used for updating the CHK/DD/ UTR Reference number into SAP based on the return file information from bank . The respective transaction reference details for the vendor account are updated either in the assignment or document header text field of the payment document.

Basic input parameters: 1) Company Code 2) Issuance file send by bank



Once reverse file is uploaded , following output will be shown.

By clicking on document number, user will be redirected to actual document display screen.

Sample issuance file (Reverse file):-



5.6 Administrative features



5.5.1. Log Table /Regeneration of payment documents:-

Whenever payment data is extracted into file either using Auto payment extractor or Manual payment extractor, a summary record of the extracted proposal is inserted into the log table. The following details are generally inserted into the table for every transaction:

a) Company Code b) Run Id (for F110) c) Run Date (For F110) b) Payment Document c) Fiscal Year d) File id (count) e) SAP User name f) System date g) System time h) Extracted File path

The entry in the table ensures both auto and manual program will not allow extraction of same payment records again. If value of a given proposal number exists in log table and if extractor is executed to generate the file for the same payment then following message will appear.

List of already extracted payment runs.



5.5.2. Mapping table:-

ZHDFCMAP is the main mapping table where the equivalent data of HDFC library with respect to SAP field is maintained.

The table stores mapping entries of HDFC library for SAP fields. Important mapping fields: a) Payment methods (Rows starting with value ‘PM’) b) DD Payable locations (Rows starting with value ‘BRANCH’) c) Check printing location (Rows starting with value ‘PRINT’)

Mapping table structure is as given below:



5.7 Re-extraction of payment documentsOverview: - Re-extraction feature is basically indented for following scenarios:-1) Manual error:-Wrong inputs provided during execution (e.g. incorrect print location chosen in selection Screen).2) Accidental file deletion:-If extracted file is accidently deleted from PC/server before the file could be Uploaded in HDFCBANK e-portal for payment processing.

To re-extract payment document pertaining to vendor, following is the procedure for both Auto and Manual payment extractor:-



Delete the record of desired Proposal number from table ZHDFCLOG for which payments needs to be extracted again. The steps are as follows:-

5.6.1. Go to admin settings.

5.6.2. Select the required rows to be deleted



5.6.3. Delete the required rows from table ZHDFCLOG table.



5.6.4. Save changes.

5.6.5. Extract the payment again after entering the input parameters (Refer 5.1.3).

5.8 Uploading Mapping Data Following are the steps for uploading all mapping entries into ZHDFCMAP table.



Click on map upload data in payment extractor main menu:-



Steps: a) Save the file in specified format (tab delimited txt file) containing mapping data into PC/ Laptop. b) Select the file from the path where it is saved. c) Execute the transaction (Please ensure that the file is not open). d) Mapping entries will be updated successfully in the mapping custom table.

Mapping configuration in table ZHDFCMAP:-

5.9 Encryption utility There are two types of Encryptions supported i.e. one is with Desktop level (AES 256) and the other is Server Level generic encryption.

Desktop level (AES 256) :-Once the Payment extraction file gets downloaded to designated folder, the .EXE file identifies it and adds up a encryption at the end of the



file.This encryption ensures that same file will not get uploaded twice into the

HDFCDIRECT portal.

Server Level generic encryption: - This generic encryption will be installed by HDFC bank to client server. Which will encrypt the file created in Source folder by extraction ,and generate a new encrypted file in destination folder (The source and destination path can be change as per the requirement)

5.10 File format

Upload File:

Sr No Description O /M Type Size

1 First Payt Doc M Char 1 ~

2 Program Run date M Date 8 01/02/2006

3 Run Identification M Char 6 UVR3

4 Paying Company Code M Char 4 0001

5 Payment document no. M Char 20 4200000613

6 Amount M Num 13.2 000000435456.00-

7 Currency M Num 5 INR

8 Payment method (Cheque, DD, Account Trsf., RTGS or NEFT )

M Char 1 C,D,I,R ,N

9 Vendor Account No/Code M Char 20 0000100000

10 Title of the Vendor O Char 15 M/S

11 Beneficiary name of the Vendor (Name 1 & Name 2)

M Char 70 EMIRATES READYMIX EST. (40 Characters in case of RTGS & NEFT payment

12 Beneficiary name Of the Vendor (Name 3 & Name 4)

O Char 70

13 Address 1 of the Vendor O Char 35



16 Address 4 (District) O Char 35

17 Address 4 – (City) O AN 35

18 Address 5 – (Postal code) O AN 35

19 House Bank (Bank in SAP) M Char 5 HDFCB

20 HB Account ID (Bank in SAP) – Client Code

M Char 5 0001

21 Value date M Date 8 12/05/2006 (This will



be printed on on the cheque and transactions will be processed on this date)

22 Instruction Date M Date 8 12/05/2006

23 Mode of Delivery O Char 12 C

24 Cheque No O Char 13 100005

25 DD Payable location O/M Char 20 Location of DD Payable and pay order (MUM ,DEL,CHE – Cashin Codes…) Mandatory for Demand Draft

26 Print Location O Char 20 Print Location valid cashin code (MUM ,DEL,CHE – Cashin Codes…)

27 Beneficiary Account Number (For RTGS )

O/M Char 25 (Mandatory incase of RTGS & NEFT)

28 IFSC Code O/M Char 20 SBIN0000300 (Mandatory incase of RTGS & NEFT)

29 Beneficiary Bank Name O Char 100 State Bank Of India

30 Beneficiary Account Type O Char 3 011

31 Beneficiary email id O Char 100 Valid Email id separated by comma for the mail to be send for RTGS & NEFT payment to be separated by comma

Advice Format –

Explanation

Description O/M Type Size

Header –1 M ~H

Client Code M Char 4 UETL

Payment Document No. M Char 10 4200000613

Document Date M Date 8 12/03/2002

Detail Record 1(1) O ~D

Title 1 : (Value of the title to be printed on the advice)

O Char 41 Invoice Number: 99999999999999999 Title details



( OPTIONAL ),File may contain 1,2,3,4,5 ,6,7 or 8 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)


O Char 41 Invoice Date : 13/05/2006 Title details ( OPTIONAL ),File may contain 1,2,3,4,5 ,6,7 or 8 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)


O Char 41 Title details ( OPTIONAL ),File may contain 1,2,3,4,5 ,6,7 or 8 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)






O Char 41 Title details ( OPTIONAL ),File may contain 1,2,3,4,5 ,6,7 or



8 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)




O Char 41

Text 1 O Char 70 SERVICE CHGS.-CONDUCTING INTERVIEW/TRADE TEST Text details ( OPTIONAL ),File may contain 1,2,3,4,5 ,6 or 7 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)

Text 2 O Char 70

Text 3 O Char 70

Text 4 O Char 70

Text 5 O Char 70

Text 6 O Char 70

Text 7 O Char 70

Detail Record 1(2) O ~D


O Char 41 Invoice Number: 99999999999999999


O Char 41 Invoice Date : 13/05/2006


O Char 41


O Char 41


O Char 41




O Char 41


O Char 41


O Char 41

Text 1 O Char 70 SERVICE CHGS.-CONDUCTING INTERVIEW/TRADE TEST Text details ( OPTIONAL ),File may contain 1,2,3,4,5 ,6 or 7 text Lines. No line would be blank. These lines may or may not come at all (Even blank line will not be there)

Reverse File

File Naming Convention

File Naming Convention Client Code + DDMM +”.” + Serial Number

Field Separator ~

File type Delimited

Example file name HDFCB258A0512.r001

Payment Types

Reverse File can be generated for the following payment types,

A/c to A/c Transfer.Cheque Printing if Cheque number is not given in Upload file. DD Printing.RTGS.NEFT.

Reverse File Structure

Field #

Field Name Field Mapping Data Type

Field Width

O/M Start Pos

End Pos

1PROGRA

Program Run date of Upload file

Date 10 M 1 10



M RUN DATE

Field 2 from the UploadFile

2RUN IDENTIFICATION

As given in upload fileField 3 from the Upload File

Char 6 M 11 16

3 Vendor Code Vendor Code of upload file.Field 9 from the Upload File

Char 10 M 17 26

4 Voucher No. Payment Doc. No. of Upload fileField 5 from the Upload File

Char 20 M 27 48

5 Value Date As given in upload file.Field 21 from the Upload File

In case Grace Period is used and transaction is authorized after value date then the date when transaction is fully confirmed

Date 10 M 49 58

6 Bank Ref No Generated by system for a/c to a/c. transfer only Fetched from HDFC database Manatory in case of I transaction type

Char 12 M/O 59 70

7CHEQUE NUMBER

Cheque no generated by HDFC Bank. Mandatory only in case of “C” transactionsFetched from

Char 10 M/O 71 80



HDFC database in case no Cheque number is given at the time of Upload in the Upload file

8DD NUMBER

DD no generated through HDFC bank. Mandatory only in case of “D” transactionsFetched from HDFC database

Char 10 M/O 81 90

9 Amount As given in upload fileField 6 from the Upload File

Num 13.2 M 91 105

10 Transaction Status All transaction status such as Executed/Rejected/Parked/Hold/Pending Authorization will be displayedFetched from HDFC database

Char 2 M 106 107

11 UTR /NEFT Ref No

Char 20 O 108 127

12 Reject Reason Fetched from HDFC database

Char 40 O 127 166

If Cheque number is given by client in the upload file then there will be no reverse file generated for Cheque payment and status will remain in confirmed status.

Sample output file for reference:-

6.0Configuration and settings for Payment extractor Tools



6.1.1 Extractor Installation steps:-

a) Initial transport files (Data files and Co files) containing objects pertaining to payment Extractor would be imported into SAP server. b) Payment extractor would be modified under package name ZHDFC in SAP b) All Custom tables would be created / modified for mapping and log entries and table Maintenance would be generated. d) The payment extractor would basically cover both automatic payment run and manual Payments and also reverse upload for updating transaction reference numbers back into SAP Payment document.

6.1.2 Folder creation and RFC configuration :-

Before execution of payment extractor following configuration needs to be maintained:-

1) Folder path needs to be created where file needs to be placed for uploading into HDFCDIRECT Portal. There are two ways of file download:-

a) File generation in Local PC/Laptop

Create HDFCBANK folder in designated path (e.g. ‘C’ drive) and maintain IMPORT and PROCESSED folders.

Copy HDFCbank.exe file (Encryption utility) to HDFCBANK folder.

Sample screenshots of the folders

Check whether the user has Write authorization to HDFCBANK folder created in local drive.



Maintain following RFC connection using SM59 t-code.1. Go to transaction SM59



2. Click onto TCP/IP connections and then click ‘Create ‘. The following screen will open up.



Enter RFC destination : HDFCBANKClick onto ‘Connection type’ the following screen will open up.



Choose connection type ‘T’.



Give a description in the field ‘Description’.



Click onto ‘Technical settings’ tab.Select the radio button ‘Start Front End Work Station’.



Give the Program name ‘C:\HDFCBANK\ENCRYPT.exe’

Save the changes the RFC destination will be created.

7.0 Configurations based on Questionnaire Based on initial questionnaire, following is the configuration in SAP payment extractor interface:-

S No. Questionnaire Solution1. SAP version ECC 6.02. Server Details UNIX/WINDOWS



3. Initial standard payment extractor objects were imported into SAP dev server

Yes

4. Type of payment extractor programs Auto payment extractor (for F110) and Manual Payment Extractor (For F-53/F-58/F-48)

5. SAP House Bank Configuration details House Bank – HDFCAccount Id - HDFC

6. Payment methods setup CHK,DD,NEFT,RTGS,A/C to A/C transfer(HDFC transfers)

7. Cheque No allotments Pre assigned series allotted by HDFCbank is being maintained for House bank and would be assigned in series for payments

8. Customer Payments in extractor required Yes9. Type of Vendors 1)Normal Vendor

2)One time Vendor3)Alternate Payee (Bank or vendor)

10. Deductions to be shown in payment advice Withholding taxes, Advance deductions, credit memo etc.

11. Advice details Order of details:1) S No.2)Invoice Ref3)Document No4)Document Date5)Invoice gross amount6)Deductions

12. Reverse Upload Program required Yes13. File download path Local PC/Server14. Encryption Methodology Checksum/SMIME15. Print location dynamics(CHK & DD) 1)for send to beneficiary –

print location code populated based on city field in vendor master2)for send to customer-Print location code populated based on business areas/business



location3) Default Print location – Mumbai (HDFC12)

16. Payable at location dynamics (DD) 1) for send to beneficiary –payable at location code populated based on city field in vendor master2)for Send to customer –Payable at location code populated based on Business Area/Business location3)Default payable at location – value defaulted to HDFC payable at par (HDFCBA)

17. Delivery Method (CHK & DD) Delivery type determined at transaction levelFree field assigned with following values while posting payment document:-‘SB’- Send to beneficiary‘SC’- Send to Customer‘HC’-Hold to customer

18. Transaction Reference Number Payment document Number/Cheque Number

8.0 Unit Test Plan

Once all mapping data is maintained in configuration table and all the technical configurations are completed, post few payment documents for all required payment types and then run payment extractor to generate output file. Upload output file into ENET portal using the profile mapped. If the format and details are correct, the transaction would be completed and the status in ENET would be complete. If in case of any validation errors, the same would be displayed.

Unit test data should be provided by client functional consultant.UTP attached for reference:-


hdfc sap payment extractor user manual ver 1

Documents