Template Version 1.

3 Requirement Document Template

REQUIREMENT DOCUMENT TEMPLATE

Template Version 1.3

Information Technology

Copyrights HDFC BANK

Page 1 of 8

Template Version 1.3 Requirement Document Template

Document Control
Authorization
TEMPLATE NAME

Requirement Document Template

TEMPLATE VERSION

1.3

EFFECTIVE DATE

1st April 2012

TEMPLATE OWNER

Information Technology

TEMPLATE APPROVER

Process Owner

DOCUMENT OWNER

To be filled by the Requestor / User

DOCUMENT CLASSIFICATION

Restricted

DOCUMENT VERSION NO.

To be filled by the Requestor / User

Review
TEMPLATE
VERSION

DATE

AUTHOR

DESCRIPTION

1.1

20th April 2010

IT Governance

Released
version
Document Template

1.2

02nd July 2010

IT Governance

1.
2.
3.
4.

1.3

1st April 2012

Copyrights HDFC BANK

IT Governance

Page 2 of 8

of

Requirement

Inserted the Document Control

Matrix
Inserted BPRG
Inserted Business Head with
Operations Head
Added version number: with date
for the document.

Default Document Classification made as

Restricted
Template approver changed to Process
Owner

Template Version 1.3 Requirement Document Template

Frequency of Review Annually

Ownership
Bank's Information Technology is the owner of the document. Unless otherwise specified, no part
of this document may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from Information
Technology (IT). Similarly, distribution of this document to a third party is also prohibited unless
specific approval is taken from IT. This document is allowed to be distributed to vendor by IT
Team.

Placement
The most updated copies of the document can be found on the Bank's information portal under
Information Technology (IT) section. All printed copies of this document are to be treated as
uncontrolled and may be obsolete. You shall always consult the current authorized versions
before making important decisions.

Copyrights HDFC BANK

Page 3 of 8

Template Version 1.3 Requirement Document Template

RD Default Version no. 0, Dated: DD/MM/YY

Subsequent versions to be numbered serially

1. Preparation by
Chanvinder Singh
2. Profile
Project Id:

NETWEVER/PR/FEB13/0001

Project Name:
Business
Group:
Project
Manager:

WIPRO | Netweaver Implementation

Corporate Banking
Chanvinder Singh

3. Introduction
Scope: SAP Netweaver Integration for WIPRO

4. Functional Requirements
Client will be doing Salary payments.
Interfaces required in Bank PI to accept the csv file pushed by client NW, process
/transform the output data into 1 adapter namely NESTLEPAYADAPTER output file as
per format acceptable to Enet.
Client would initiate Salary Payments
Client Input File structure:
1. Input file is a comma separated file.
2. There will be no headers record in the file.

Client sample Input File:

Copyrights HDFC BANK

Page 4 of 8

Template Version 1.3 Requirement Document Template

20130902-161813-4
44_WIPROIDOC_PAYROLL3_J UL13_new.csv.pgp.zip

Output File Format Structure:

A: NESTLEPAYADAPTER
Sr,No
1
2
3
4
5
6

FIELD NAME
Customer Reference No
Bene Name
Bene Account No
IFSC code
Account Type
Amount

TYPE WIDTH M/O

FT
25
M
FT
70
M
S
30
M
AN
11
M
N
2
M
N
15
M

Value date

Remarks

12.XX (12+ . + 2). It

should be with
decimals
Date format:
YYYYMMDD

Mapping of Output File Format Structure:

A: NESTLEPAYADAPTER

Nestle
PayAdapter_V2_04062014.zip

Sample output file attached.

Nestle
PayAdapter.zip

Note:
FT- Free text
N- Numeric
AN- AlphaNumeric
S- String
LOGIC for SPLIT
Is given in mapping file for both the adapters.
Input File naming convention:
- Input File name starts with WIPROIDOC_SALARY_PAYROLL_<Dynamic
Name>_<MONYY>.csv.pgp
- The actual file name is as below
WIPROIDOC_SALARY_PAYROLL_SAL1New_JUL13.csv.pgp

Copyrights HDFC BANK

Page 5 of 8

Template Version 1.3 Requirement Document Template

File name convension is a combination of 5 parameter separated by

Underscore excluding the file extension and pgp extension.
From the input file name, first 3 parameters separated by underscore (_) are static and
the next 2 parameters separated by underscore (_) are dynamic.

Failure File format

-

All failure Transaction from the respective input file to be shared to Client in
the single file only against the respective input file.
File format will be exactly similar to the file format received under input file.

Failure File naming convention:

- File naming starts with FAILURE_ followed by exactly similar to the input
file name.csv
- i.e if the input file received from Wipro is
WIPROIDOC_SALARY_PAYROLL_SAL1New_JUL13.csv.pgp than the failure file name
will be FAILURE_ WIPROIDOC_SALARY_PAYROLL_SAL1New_JUL13.csv
Transaction/Data Flow
Data flow will be Bi-directional .i.e from
Client to Bank (Payment Data) and
From Bank to Client (for upfront Failure transaction while generating Output
file through Netweaver)
Summary Report File
3. Post conversion, Netweaver to generate a csv report having total no. of Actual
Data, Sum of Actual data, No. of HDFC records, Sum of HDFC records, No. of
Non-HDFC records, Sum of Non-HDFC records, No. of Error records, Sum of
Error records.
4. It should also contains the no. of file generated post splitting along with the
Sum for both HDFC and Non-HDFC records.

Naming convention of Summary Report file

-

File naming to start with SummaryReport_ followed by exact input file

name.csv
i.e if the input file received from Wipro is
WIPROIDOC_SALARY_PAYROLL_SAL1New_JUL13.csv.pgp than the Summary report
file name will be
SummaryReport_WIPROIDOC_SALARY_PAYROLL_SAL1New_JUL13.csv

Sample Summary File attached

Summary Report.zip

EMAIL NOTIFICATION
Email Notification for Upload File ( Batch Created)

Email Notification required to be triggered to recipients once the Enet Upload File /
Batch is created for Enet processing.

Copyrights HDFC BANK

Page 6 of 8

Template Version 1.3 Requirement Document Template

Email Notification for failure transactions while generating Output File

Email Notification required to be triggered to recipients on transferring the files
having only failure transactions to Wipro end (for upfront Failure transaction while
generating Output file through Netweaver).
The scope of Enet reverse file sending to Wipro end is not in the project scope.
Email Notification for SummaryReport File
Email Notification required to be triggered to recipients once all the output file from
the input file is created through Netweaver.
Batching Methodology:
Currently there is no batching.
Acknowledgment XML for Upload File:
NA

Methodology To Derive out File Name of Upload File

Each Input file will have only 1 Debit Account no. If multiple then reject the complete file
stating Multiple debit a/c no. found in the input file
-ClientCode Value for actual file name should be derived from the Look up file
maintained in Bank PI.
-Look Up file to have below Fields/Parameter
# Debit Account Number
# Client Code
# Domain ID
-Value of the Debit Account Number should be derived from the Source File column 3
(pushed by client).

Example:-

Assuming file pushed on 25/11/2013, Debit Account Number received in the file is
0001123412341999 then actual file name should be
DOMAINID_CLIENTCODE_CLIENTCODEDDMM.SEQ
i.e: WAL1_ABCD_ABCD2509.001

Broad Process Flow Salary payment file

- File is created through ERP and the same will be pushed though the existing
Net weaver channel of client to Bank PI.
Copyrights HDFC BANK

Page 7 of 8

Template Version 1.3 Requirement Document Template

File
received
from
WIPRO
will
be
in
a
PGP
encrypted.
Bank
PI
to
read
the
csv
file
with
comma
separated.
- Post generation of output files formats it will push the file to ENET
application.
- PGP encryption to be enabled.

5. Operational Concepts and Scenarios

6. Target Environment
Netweaver

7. Interface Requirements
a. Graphical User Interface
b. Hardware Interface
c. Communication interface
d. Software Interface
8. Migration/Transition Plan (if applicable)
9. Non-functional Specific/Additional Requirements
10. Assumptions/Dependencies/Limitations
11. Systems Impacted (if any) :
12. Screen Shots (if any)
13. Acceptance Criteria
14. Additional Information

Prepared by / Date
(BSG / BPRG Manager)

Reviewed by / Date
(IT Manager)

Approved by / Date
(BSG / BPRG Application
Owner)

Approved by / Date
(IT Application Owner)

Reviewed by / Date
(BPRG / BSG)

Concurred by / Date
(Operations Head / Business
Head, if required)

Copyrights HDFC BANK

Page 8 of 8