Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 6

Functional Design - Enhancement SAP Implementation at MRL

Functional Design
Enhancement

E14
BDC for Uploading Bank Statement
using transaction code FF67

Prepared By: Y Sivaramaiah Page 1 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01
Functional Design - Enhancement SAP Implementation at MRL

Table of Contents

1. SIGN-OFF, REVISION HISTORY & QA CHECKLIST............................................................................................3

2. FUNCTIONAL DESIGN.................................................................................................................................................4
2.1 OVERVIEW....................................................................................................................................................................4
2.1.1 Priority..................................................................................................................................................................4
2.1.2 Complexity............................................................................................................................................................4
2.1.3 Type of Enhancement............................................................................................................................................4
2.2 ASSUMPTIONS...............................................................................................................................................................4
2.3 DETAILED FUNCTIONAL REQUIREMENTS.....................................................................................................................4
2.3.1 Selection Criteria / User Interface.......................................................................................................................4
2.3.2 Processing............................................................................................................................................................8
2.3.3 SAP Transaction and/or scenario.........................................................................................................................8
2.3.4 SAP Standard/Custom Tables...............................................................................................................................8
2.3.5 Output...................................................................................................................................................................8
2.3.6 Interactive Capabilities........................................................................................................................................8
2.3.7 Dependencies........................................................................................................................................................8
2.3.9 Historical Data Requirements..............................................................................................................................8
2.3.10 Reusability Considerations.................................................................................................................................9
2.3.11 Security and Authorization Considerations........................................................................................................9
2.3.12 Performance Considerations..............................................................................................................................9
2.3.13 Other Considerations.........................................................................................................................................9
2.3.14 Known Exceptions..............................................................................................................................................9
2.4 Unit Test Conditions for Developers............................................................................................................................9

Prepared By: Y Sivaramaiah Page 2 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01
Functional Design - Enhancement SAP Implementation at MRL

1. Sign-off, Revision History & QA Checklist


Document:
Team: Finance

Revisions
List all revisions in this section. The details of each revision should be clearly marked and
indicated in the appropriate section.
# Date Author Sections Revised
1 25-07-08 Sivaramaiah Yella

QA Checklist
1. Have all sections been completed or marked with N/A?
2. Have all considerations been documented?
3. Have all outstanding design issues been resolved?
4. Have all working assumptions been documented?
5. Have all revisions been properly documented in the Revisions section?

FD Status
Status: In Progress, Completed, Signed off

FD Sign-off

Responsibility Name Signature Date

Functional Designer Y Sivaramaiah ________________ __________

Process Owner SK Sharma ________________ __________

Prepared By: Y Sivaramaiah Page 3 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01
Functional Design - Enhancement SAP Implementation at MRL

2. Functional Design

2.1 Overview
Bank gives their Statement on daily basis. It will be uploaded into SAP through transaction code
FF67.

2.1.1 Priority
High

2.1.2 Complexity
Medium

2.1.3 Type of Enhancement


.

2.2 Assumptions

2.3 Detailed Functional Requirements


2.3.1

2.3.2 Processing
BDC has to written for the transaction code “FF67” and the fields are as mentioned in the below
excel file

BDC_FF67.xls

2.3.2 Processing

2.3.3 SAP Transaction and/or scenario

Prepared By: Y Sivaramaiah Page 4 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01
Functional Design - Enhancement SAP Implementation at MRL
2.3.4 SAP Standard/Custom Tables

2.3.5 Output

2.3.6 Interactive Capabilities

2.3.7 Dependencies
N/A

2.3.8 3rd party Impact Considerations


Not Applicable

2.3.9 Historical Data Requirements


N/A

2.3.10 Reusability Considerations


N/A

2.3.11 Security and Authorization Considerations


N/A

2.3.12 Performance Considerations


Daily
No Performance Problem will arise due to this development.

2.3.13 Other Considerations


N/A

2.3.14 Known Exceptions

List known exceptions in the above process flow.


Exception Action Expected
N/A N/A

2.4 Unit Test Conditions for Developers

No. Test Condition Expected Result


1.

Prepared By: Y Sivaramaiah Page 5 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01
Functional Design - Enhancement SAP Implementation at MRL
2.

Prepared By: Y Sivaramaiah Page 6 of 6


Created on 20/06/2008 03:31:00 Status: DRAFT
Filename: FIPR.01

You might also like