Professional Documents
Culture Documents
Functional Design Enhancement: E14 BDC For Uploading Bank Statement Using Transaction Code FF67
Functional Design Enhancement: E14 BDC For Uploading Bank Statement Using Transaction Code FF67
Functional Design
Enhancement
E14
BDC for Uploading Bank Statement
using transaction code FF67
Table of Contents
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
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
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.2 Assumptions
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.5 Output
2.3.7 Dependencies
N/A