Functional Specification

Format No/ Rev: FS-ABAP-001/ 00

Version: 01 Issue Date 04.11.2016

(dd/mm/yyyy):
Specification No: MSNL-FS-PP-C-0001-Routing
Upload In Preparation Review
Development No: MSNL-FS-PP-C-0001- Routing Approved Released
Upload
Business Process No. :

Revision History
Version Date Description of changes

Responsible
For concept – For Implementation –
Section I: Justification
Area (R/3 PP Date
Module): (dd/mm/yyyy):

Requested by:

Brief description:

Generic question:

1. Impact of not creating the Legal requirements will not be fulfilled

program:
Lack of information required for the business

Lose functionality compared to the old system

Others:

Is there any alternative in the standard Yes No

system:

Page 1 of 10 Date 2/1/2018

Describe the alternative found:

Reason why this alternative was not Performance problems Complexity

acceptable:
Others:

(Explain in brief)

Program type: Report Module Pool Interface

Enhancement Conversion Form

Application Development (Approval from PMT) Others

Priority: High/mandatory Medium/recommended Low/optional

Charateristics Drill Down ALV Others          

Frequency: Daily Weekly Monthly

Biweekly Other:          

Only for Interfaces:

Type of interface: Real-Time Batch

Direction of interface: Inbound Outbound Both

Sign off – Functional Specification

Prepared By Comments        

Date
    /    /       
Team Lead Lead Consultant

Date Date
Approved by Project Management Team     /    /       

(in case of Application development )

       

Received Team Lead/ Lead Consultant        

Date     /    /   
  

Page 2 of 10 Date 2/1/2018

Section II: (a) Business Needs & Requirement (Please use this section for describing the
business requirement in detail preferably with flow diagram)

Authorization requirements: NA

Others: NA

Page 3 of 10 Date 2/1/2018

 Section III: Only For Reports/Forms

Selection Criteria (Input Screen)

Name Table Field/ Comments Default Value Table & Field Name
Check box/ (Single/Multiple
Radio button Selection,
Mandatory etc.)

Selection Logic

Process Logic

Report/Form Layout (Attach format if required)

Page 4 of 10 Date 2/1/2018

 Section III: Only For Interface/ Conversion

Tables PLKO,PLPO,MAPL          
involved:

SAP Input Screen (Data Mapping)

Transaction: CA01

Recording ZROUT

Screen R/3 Screen field Legacy field Remarks

number name

1010 RC27M-MATNR Material

1010 RC27M-WERKS Plant

1010 RC271-STTAG Valid from date

1200 PLKOD-VRWE Usage

1200 PLKOD-PLNAL Group counter

1200 PLKOD-KTEXT Routing text

1200 PLKOD-STATU Status

1400 PLPOD-ARBPL(01) Workcenter

1400 PLPOD-STEUS(01) Control key

1010 PLPOD-VGW03 Labour

1010 PLPOD-VGW02 setup

1010 PLPOD-VGW01 machine

Page 5 of 10 Date 2/1/2018

 Section III: Only for module Pool
Not Applicable

Screen Layout: (attach details of screen layout)

Screen Field Mapping:

Field Field Description SAP Mandatory/Optional Default values
Reference
Field

Process Logic

Page 6 of 10 Date 2/1/2018

Section III: Only For Enhancements

Name Description

Process Logic

Page 7 of 10 Date 2/1/2018

Section IV : FS Review Report:
Ver. SL. No. Description Severity Status Fixed Date Reviewed By

Section IV : Test Case and Test Related

Result specification
Format No/ Rev: TC-ABAP-001/ 00

Page 8 of 10 Date 2/1/2018

Number: TC- PP-HU-O/P -001 Prepared on 18.06.2014
Test Cases (with expected results)
Positive Test:
Mandatory field Test :

Negative Test:

Checks performed
Test sequence and test results
Expected Result :

Section I: Unit Testing

Program name:       Test date:     /    /       
Developer name:      
Team Members
(Functional)

Responsible functional team member for testing:

 File(s) used for test (optional):          
 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.

 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

Page 9 of 10 Date 2/1/2018

Names and Signatures

     
_______________________________________________________________________________________
Team Lead
     
_______________________________________________________________________________________
Lead Consultant

Page 10 of 10 Date 2/1/2018