Functional Specification
Functional Specification
Name: Dunning Letter -1
1/8
Functional Specification
Document History
Specification
Section I: Object General Information
Title (RICEF No): FI-F-013 Date: 30.06.2016
Short description: Dunning Letter -1
SAP Module/Team: SAP FI
Functional Contact: Atul Kumar Vashist
Technical Contact Dinesh Kumar
Priority:
Complexity Level
Program type Form
Reviewer
Role Name Signature Date
Consultant Atul Kumar Vashist
Approver
Role Name Comments Received Date
Project Manager Aditi Guptaa
2/8
Functional Specification
Table of Contents
1. Overview and Scope 4
1.1. Functional Description 4
1.2. Assumptions 4
1.3. Transaction Volume 4
1.4. Frequency & Timing 4
1.5. Processing Type 4
1.6. Output Time 4
1.7. Retention Requirements 4
1.8. Audience and Distribution 5
2. Detailed Functional Requirements 5
2.1. Functional Specification for Reports / Forms 5
2.1.1. Report / Form Fields 6
2.1.2. Selection Criteria 6
2.1.3. Other Information 6
2.1.4. Program Name 7
2.2. Error Handling 7
2.3. Security and Authorization 7
2.4. Processing and Operational Considerations 7
2.4.1. Performance 7
2.4.2. Batch Requirements 7
2.4.3. Others 7
3. Test Script 7
3.1. Testing Pre-requisite 7
3.2. Test Case 8
4. Appendix 8
4.1. Glossary of Terms 8
4.2. Additional Reference Documentation 8
3/8
Functional Specification
1. Overview and Scope
1.1. Functional Description
DLIN require to send reminder letter to customer if payment is not received on time as per
term and conditions of the Sales Order.
In DLIN Dunning functionality is configured, Forms are attached along with Logo
The development has been done as per the requirement given by the DLIN.
1.2. Assumptions
Dunning Master data is maintained in Customer Masters.
1.3. Transaction Volume
1.4. Frequency & Timing
1.5. Processing Type
1.6. Output Time
4/8
Functional Specification
1.7. Retention Requirements
1.8. Audience and Distribution
2. Detailed Functional Requirements
2.1. Functional Specification for Reports / Forms
Tables to be used: BSID, BSAD, BKPF, BSEG
Change the language, Logo, Company Name etc. as per the below form
5/8
Functional Specification
2.1.1. Report / Form Fields
2.1.2. Selection Criteria
2.1.3. Other Information
1. Heading information
2. Sub Heading information
3. Totaling or other calculation requirements
6/8
Functional Specification
4. Sorting
5. Page breaks
6. Stationary details ( layouts, paper size, etc)
7. Logo(s)
8. Interactive capabilities
2.1.4. Program Name
T-Code: F150
2.2. Error Handling
2.3. Security and Authorization
2.4. Processing and Operational Considerations
2.4.1. Performance
2.4.2. Batch Requirements
7/8
Functional Specification
2.4.3. Others
3. Test Script
3.1. Testing Pre-requisite
[Indicate the pre requisite conditions to use to verify successful operations of the conversion.]
Pre-requisite Type Data Element Details
(Master data, Config,
Other Development)
3.2. Test Case
Test Test Step Description T Code Input Data Expected Results Results Obtained
Step
No
1
4. Appendix
4.1. Glossary of Terms
Term Definition
4.2. Additional Reference Documentation
8/8
