Functional Specification

Functional Specification
FS id: FI-C-076
Name: Overdue customer line item alert notifi-
cation

1/8
 Functional Specification

Document History

Specification
Section I: Object General Information

Title (RICEF No): FI-INC0035600 Date: 10.12.2018

Short description: Overdue customer line item alert notification for Sales team.
SAP Module/Team: SAP FI
Functional Contact: Srinivas Birdar
Technical Contact Aayush Anand
Priority: Medium
Complexity Level Medium
Program type

Reviewer

Role Name Signature Date

Consultant Kumar Vashist, Atul.

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

Overdue Amount alert should go to the sales team at least 10 days before the 30 days over-
due bucket is breached.

A program would be developed which would run every day and to send the email to the sales
team.

1.2. Assumptions
Customer Billing Posted through SD route

1.3. Transaction Volume

1.4. Frequency & Timing

Daily

1.5. Processing Type

Email notification

1.6. Output Time

1.7. Retention Requirements

4/8
 Functional Specification

1.8. Audience and Distribution

2. Detailed Functional Requirements

2.1. Functional Specification for Reports / Forms

After overdue of 20 days of customer line items email should be trigger to the sales team.
(ZFI_CAGE Customer Ageing Report to calculate overdue days).

Create one field Alert in TMG ZSD_OVERDUE to maintain the Alert day
T-code: ZFI_CAGE
Program: ZFI_AR_AGEING
LOGIC:

Execute as per below selection criteria

Customer- 1000000 to 99999999

5/8
 Functional Specification

Date- Defaulted (don’t change)

Tick summary report

Hard code first All Intervals.

REST Intervals - 01 02 03 04 05 06 07 08 09 19 20 30

For entries found with 19 to 20 Day Take the KUNNR (customer code) and DMBTR
(Amount) in ZFI_CAGE
Go to the KNVV table pass the KUNNR (customer code) and get the values of VKORG
(Sales organization) = 5300
Create the Z table and maintain the sales team mail id’s
Use the standard FM SO_OBJECT_SEND to send the emails to the sales team

2.1.1. Report / Form Fields

2.1.2. Selection Criteria

Date

2.1.3. Other Information

1. Heading information

6/8
 Functional Specification

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_Overdue

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