Functional Design Document

Functional Design Document (FDD)

Purpose
This document is used to describe the functional design and specification for Report, Interface,
Extension/Enhancement, Form or Workflow.

Version History

Version Date Author Reviewer Description Ref. or CR No.

0.1 Document created

Ref. or CR No. Description

Table of Content

Last Updated 8/07/2020 11:48 PM Page 1 of 9

Functional Design Document

1. PROGRAM DETAILS 3
2. GENERAL REQUIREMENTS 4
3. DESIGN 5
4. TESTING REQUIREMENTS 9

Page 2 of 9
 Functional Design Document

1. PROGRAM DETAILS

RIEFW Title: (Required) RIEFW Id:

S

RIEFW Description: (Required)

A report needs to be developed which will provide the net cash balances by considering all incoming,
outgoing and non-cleared payment during a specified period. The net cash balances should match the
corresponding amount as per bank statement.
This report should be executed on the basis of Company code, House Bank Number, House Bank ID and
Transaction Date

Application: (Optional)
N/A

Project: (Required) RIEFW Type: (Required)

SAP Report

Team: (Required)
TR

Sub Team: (Required)

BANK

Comments: (Optional)

Approval

Created By: (Required) Creation Date:

FD Approved By: (Required) Approval Date: (Required) Sign-Off: (Required)

Page 3 of 9
 Functional Design Document

2. GENERAL REQUIREMENTS

General User Requirement:

Currently the business is facing problems to reconcile the cash balance to the corresponding amount on
its bank statement. A report needs to be developed which will provide the net cash balances by
considering all incoming, outgoing and non-cleared payment during a specified period. The net cash
balances should match the corresponding amount as per bank statement.
This report should be executed on the basis of Company code, House Bank Number, House Bank ID and
transaction date

3. ASSUMPTIONS:

4. DESIGN
Detailed Description of Enhancement/Extension: (Required)
In SAP, supplier payments are incomplete transactions which need to be cleared once the payment has
been processed by the related House Bank. Moreover, payments are managed as open items on the
balance sheet until either the related bank statement is processed in the system or the item has been
cleared otherwise. Clearing of these items requires posting the value to offset the amount, creating a
balance of 0, and can happen either automatically or manually. This happens automatically
through Electronic Bank Statement (EBS) processing and clearing, and manually through the
reprocessing of bank statements or manual clearing. In simple terms, the clearing process matches
supplier payments generated by the system and the outgoing payments from the bank statement to to
close off any outstanding debts or accounts
Bank Reconciliation report will be developed to fetch the details of those incoming, outgoing payment of
the specific bank for a specific period. This report will consider the opening balance at that specific date.
It will derive the closing balance by adding incoming payment with the opening balance and deduct the
outgoing payment (ACH and Wire Transfer). To get the net cash balance, non-cleared items will be added
with the ending balance.
3.1 Selection Screen
SAP Selection Screen Layout

Page 4 of 9
Functional Design Document

SAP Selection Screen Field Description

No. Field Name Field Data Type Length Logic

1 Company Code T012K-BUKRS CHAR 4
Default Value “2000”
2 House Bank T012K- HBKID CHAR 4 BNKA- BNKLZ

3 Account ID T012K- HKTID CHAR 10

4 Transaction Date KONA-BOSTA CHAR 1 Default “ ”, “A”, and “B” if

action “Carry out rebate
settlement” is selected.

SAP Selection Screen Validation

To execute “Bank Reconcilation ” using this program, agreement must not yet settled.
Logic: If Agreement status (KONA-BOSTA) in input screen “ ” Open, “A” Settlement Is Being
Checked for Release, or “B” Agreement Released for Settlement, process next step.
Else, return error message “To carry out rebate settlement, select only agreement status
“ ” Open, “A” Settlement Is Being Checked for Release, or “B” Agreement Released for
Settlement”.

Page 5 of 9
 Functional Design Document

5. BANK RECONCILIATION REPORT LAYOUT

Bank Reconciliation report

Bank Reconciliation Report-Header Level

No. Display Technical Name Data Length Logic
Column Type
1 Bank Code KONA-KNUMA CHAR 10

2 Bank KONA-BONEM CHAR 10

Description

3 Bank Account KONA-DATAB DATS 10

No

4 Currency Key KONA-DATBI DATS 10

4 Beginning KONA-BOSTA CHAR 1

Balance

5 Incoming “Cleared” or “Not CHAR 13

Cleared”
6 Outgoing-
Check

7 Outgoing-Wire
Transfer

Page 6 of 9
 Functional Design Document

No. Display Technical Name Data Length Logic

Column Type
8 Outgoing-ACH

9 Ending Balance

10 Not Cleared

11 Cash Balance

Bank Reconciliation Report-Line Item Level

No. Display Column Technical Name Data Type Length Logic

1 Document ACDOCA- CHAR 10 Pass Company Code,

Number

2 Doc. Header CHAR 10

Text

3 Assignment DATS 10

4 Customer DATS 10

5 Customer CHAR 1
Name

6 Posting Date

7 Incoming

8 Outgoing-
Check

9 Outgoing-Wire
Transfer

10 Outgoing-ACH

11 Ending Balance

12 Not Cleared

13 Cash Balance

Page 7 of 9
 Functional Design Document

Logic:

6. AUTHORIZATION:
Basis Team need to provide access of the report to the specific User group.

7. PERFORMANCE CONSIDERATIONS:
Performance of the program is based on number of payment document processed on the transactional date.

8. TEST PLAN
Brief description of issue/Test Case:
Brief description of resolution: Report will be generated with details of
Environment: SAP

SCENARI TEST CONDITION EXPECTED HOW

O# RESULT VERIFIED/ACTUAL
RESULTS
Report should only provide output
for the specific company code,
date range, fiscal year and bank
1 account number mentioned in the
selection screen

Page 8 of 9
Functional Design Document

Page 9 of 9