Functional Specifications

BUSINESS REQUIREMENT DOCUMENT

Customer Ageing with Provision

Project : GoAir

By KPMG Advisory Services Private Limited

Date Feb 14, 2017

DOCUMENT INFORMATION

DOCUMENT NAME BUSINESS REQUIREMENT DOCUMENT BDC for FB41

TITLE BUSINESS REQUIREMENT DOCUMENT BDC for FB41
DOCUMENT BDC FOR FB41
PURPOSE
KEY WORDS BDC, FB41, FOREGROUND, BACKGROUND
DOCUMENT STATUS COMPLETED
CONTACT FOR TEJAL STALEKAR
ENQUIRIES

REVISION HISTORY
VERSION AUTHOR | REVISION
1.0 TEJAL STALEKAR 14.02.2017

THIS DOCUMENT HAS BEEN REVIEWED BY

REVIEWER DATE REVIEWED
1
2
3
4
5

THIS DOCUMENT HAS BEEN APPROVED BY

SUBJECT MATTER ADVISORS
NAME SIGNATURE DATE REVIEWED
1
2
3
4
5

PROCESS BUSINESS REQUIREMENT DOCUMENT NONE

APPLICABLE COMPANIES GOAIR

 1- Functional specification

Version: 1.0 Issue Date 14/02/2017

Specification No : (dd/mm/yyyy):
(To be filled by Technical Department) In Preparation Review
Approved Released

Responsible
For concept : Tejal Stalekar For Implementation: INTERFACE POSTING
Section I: Justification
Area ( Module): FI Financial Accounting Date 14/02/2017
(dd/mm/yyyy):

Requested by: Yusuf Abbasi

Brief description: BDC for FB41

Program type: (select Conversion Batch Interface Online Interface Report

the check box)
Form Enhancement Extension Dialog
Modification Unknown Others BAPI
ALE/ IDOC Application Development Infotype Development

Characteristics Drill Down ALV Others (Smart form)

Priority: High/mandatory Medium/recommended Low/optional

Only for Interfaces:

Type of interface: Real-Time Batch
Direction of interface: Inbound Outbound Both
Frequency: Daily Weekly Monthly
Biweekly Other:

Only for Reports:

1. The report will be created via: Report Painter Report Writer ABAP Query
2. Requested characteristics: ABAP Program Info System
3. Praposed execution is Drill-down Pushbuttons Sort
online/background
Entry files Others:
4. Any Authority checks are required
5. If any LDB is available? if yes, which
screen to use
 2- Sign off Functional Specification
Prepared By Tejal Stalekar Comments
14/02/2017
Date

Team Lead Lead Consultant Tejal Stalekar

Date Date 04/02/2017

Reviewer
Date
Approved by Project Management Team / /
(in case of Application development)

Received Team Lead/ Lead Consultant

Date / /

Section II: (a) Business Requirement (Please use this section for describing the business
requirement in detail preferably with flow diagram)
General Definition:
LSMW for FB41
(b) Detailed Functional Description Concept Operational Requirements (describe in
detail)
Create BDC for tcode FB41 Post Tax Payable

As discussed, attached is the format with comments

1 system should allow us to post multiple entries with different document no in one format only
2 user will keep one blank row to understand different entries. - As shown in Sheet 1 there 2 are different
entries. So if we will keep 1 line blank in between 2 entries, system should capture it as seprate entries
and generate 2 separate Document Number
3 to upload user should have 2 options (i) in background and (ii) in foreground
4 fields highlighted in yellow colour are to be mandatory fields to upload
5 the above format should be linked with T-code FB41- Whatever fields we have mentioned in LSMW
format should be captured in FB41.

Process Flow:
Selection Screen
Header: BDC for Post Tax Payable
Create a path for error file.
If any document has not got posted due to any error, give output of those lines same as upload file with
column for error description. So that same error file can be used to upload again.

Attached is the format of the file for upload

BDC_for
FB41_Shital_V1.1.xlsx

Process Logic:
User will insert Counter in the first column to signify one accounting entry.

Should check that the total of all posting keys 40 should be equal to total of all posting keys 50

Use the BAPI BAPI_ACC_DOCUMENT_POST

Please check if the Tcode FB41 uses the Tcode FB01 in background.

Tables:
Structure:

3. Effort Estimation
Effort Estimation Breakup: Total Hours
Requirement Analysis 0.30 HRS
Functional Specification 1 HRS
Development - HRS
Testing HRS

4. For Conversion
Tables Tables and field name are mentioned in the above functional description concept.
involved:

5. For Interface
Fields Required From Source System:

Field Description Field Name in Source System Data Type

Fields Required From Target System:

Field Description Field Name in Target System Data Type

Data Mapping:

Field Name in Source System Field Name in Target System

Validation:
Procession Logic:

Error Handling Requirements:

6. SAP Input Screen (Data Mapping)

Transaction ZFICUSTAGE
:

Screen R/3 Screen field Legacy field Remarks

number name

Run Date

Upload file path

7. Online Consistency checks

Tables
involved:

Item Screen Field Description

1.
2.

8. Forms
Tables Tables and fields have been mentioned above
involved:

Design of
drcrnote_final.docx
desired
form
Layout set:
 9. Enhancement:

Specify the available enhancement name, customizing path and details about what must be done.
Please ensure all customization done w.r.t. testing

Test Case and Test Related Result specification

Format No/ Rev: TC-ABAP-
001/ 00
Number: Prepared on
Test Cases (with expected results)
1. Select Position
2. Select Department
3. Select Working Location
4. Select above fields for Superior also

Section I: Unit Testing

Program Test / /
name: date:
Developer
name:
Team
Members
(Functional)
Responsible functional team member for testing:

1. File(s) used for test (optional):

2. Does the program comply with the functional specification ?
Yes No
Note: If the program is OK just sign the form. If necessary include some comments in the appropriate section.
3. If the answer to question 2 is "No" please describe the problems that were found in the
program.

Sign off after testing

Team Lead Lead Consultant

Date / / Date / /
 Sign-Off and Acceptance of developed object
Names and Signatures
_______________________________________________________________________________________
Team Lead

_______________________________________________________________________________________
Lead Consultant

Daman liddar

Annexure 1

2017 KPMG Advisory Services Private Limited , an Indian Partnership and a member firm of the KPMG
network of independent member firms affiliated with KPMG International Cooperative (KPMG
International), a Swiss entity. All rights reserved.

Proprietary Nature of Document

This document is prepared for the sole and exclusive use of Go Air. Application support. Therefore, this
document is considered proprietary to KPMG Advisory Services Pvt. Ltd and Go-Air and Wadia group and
may not be made available to anyone other than the addressee or persons within the addressees
organisation.
Copyright
All rights reserved. No part of this document may be reproduced or transmitted in any form by any means,
electronic or mechanical, including photocopying and recording, or by information storage or retrieval
system, except as may be permitted, in writing, by KPMG.