Functional Specification

Functional Specification

Name: Vendor Ageing

1/9
 Functional Specification

Document History

Specification
Section I: Object General Information
Title (RICEF No): FI-R-001 Date: 02.07.2016
Short description: Vendor Ageing

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/9
 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 7
2.1.2. Selection Criteria 7
2.1.3. Other Information 7
2.1.4. Program Name 7
2.2. Error Handling 7
2.3. Security and Authorization 7
2.4. Processing and Operational Considerations 8
2.4.1. Performance 8
2.4.2. Batch Requirements 8
2.4.3. Others 8

3. Test Script 8
3.1. Testing Pre-requisite 8
3.2. Test Case 8

4. Appendix 9
4.1. Glossary of Terms 9
4.2. Additional Reference Documentation 9

3/9
 Functional Specification

1. Overview and Scope

1.1. Functional Description

Ageing analysis is required for Vendor

1.2. Assumptions

1.3. Transaction Volume

1.4. Frequency & Timing

1.5. Processing Type

1.6. Output Time

1.7. Retention Requirements

4/9
 Functional Specification

1.8. Audience and Distribution

2. Detailed Functional Requirements

2.1. Functional Specification for Reports / Forms

Based on Key Date (BUDAT) and Break criteria (ZFBDT) specified in selection, create
buckets for ageing. If vendor is selected for specified vendors (LIFNR) pick data from table
BSIK. From table BSAK as required, where clearing date (AUGDT) is after key date
(BUDAT) pick relevant data.

Create Transaction Code “ZFI_VAGE” for Accounts Payable / Receivable Ageing Report.

Provide following fields for input:

Output of the Report should have following columns:

Field Name

5/9
 Functional Specification

Vendor Number
Vendor Name
Account Group
Account Group description
City
Country
Industry Key
Description of Industry Key
User Id
User Name
Bill Date
Posting Date
Bill Number
Purchase Group
PO Number
PO Value
Debit/Credit Indicator
Document Type
Profit Center
Name of Profit Center
Period
Tax Code
Tax Code Text
Amount in Local Currency
Amount in Document Currency
Document Currency
Payment Terms
Payment Terms Text
Item Text
Base Line Date
Days
Due Date
Special GL Indicator
Reference Document number
Day Bucket -1
Day Bucket -2
Day Bucket -3 up to …
Not Yet Due

The Output should be in ALV form, and should have options of Total, Sub-Total, and
download to excel etc

6/9
 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
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: ZFI_VAGE

2.2. Error Handling

2.3. Security and Authorization

7/9
 Functional Specification

2.4. Processing and Operational Considerations

2.4.1. Performance

2.4.2. Batch Requirements

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

8/9
 Functional Specification

4. Appendix

4.1. Glossary of Terms

Term Definition

4.2. Additional Reference Documentation

9/9