Scribd
Upload
127 views

Functional Specification: Bajaj Power Generation Business

This functional specification document outlines the need for a workflow to track bank guarantees that are expiring within specific timeframes. It describes the business need of triggering email alerts to designated people if a bank guarantee is expiring within the next 2, 15, or 30 days. The document includes sections on justification, program type and priority, screen layout details, test cases, and sign-off procedures. It provides the key details required to develop a program to fulfill the legal and business requirements for tracking expiring bank guarantees.

Uploaded by

Bipul Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
127 views

Functional Specification: Bajaj Power Generation Business

This functional specification document outlines the need for a workflow to track bank guarantees that are expiring within specific timeframes. It describes the business need of triggering email alerts to designated people if a bank guarantee is expiring within the next 2, 15, or 30 days. The document includes sections on justification, program type and priority, screen layout details, test cases, and sign-off procedures. It provides the key details required to develop a program to fulfill the legal and business requirements for tracking expiring bank guarantees.

Uploaded by

Bipul Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Functional Specification

Bajaj Power Generation Business


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

Version: 00 Issue Date 31/01/2012


Specification No FS-MM-0002 (FS-XXX-YYY-999) (dd/mm/yyyy):
BBP Refrence : BEPL_BBP_MM_PUR_RFQ_1 In Preparation Review
Development No FS- (TS-XXX-YYY-999) Approved Released
(To be filled by Technical Department)

Revision History
Version Date Description of changes

00 24/01/2012

Responsible
For concept – Sumit jain For Implementation - BAJAJ
Section I: Justification
Area (R/3 MM Date 31/01/2012
Module): (dd/mm/yyyy):

Requested by: Anil Chaudhary

Brief description: Workflow for Bank Gaurantee

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:

Describe the alternative found:

Reason why this alternative was not Performance problems Complexity


acceptable:
Others:      

(Explain in brief)

Page 1 of 5 Date 3/17/22


Program type: Report Module Pool Interface
Enhancement Conversion Form
Application Development 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 Amit Comments      
Date 24/01/2012
Anil
BEPL BEPL      
Chaudhary/Ashok
Date Kumar Date   /  /    

24/01/2012
Approved by Project Management Team   /  /    
(in case of Application development)
     

Received Team Lead/ Lead Consultant      


Date   /  /    

Page 2 of 5 Date 3/17/22


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

Description and Purpose :


Provision for BG workflow

Business Process Detail :


If BG expired in next 2,15 & 30 days then mail should triggered to designated person.

Section III: Only for module Pool

Screen Layout: (attach details of screen layout)

3. Report Selection

4. Report Output

Screen Field Mapping:


Field Field Description SAP Mandatory/Optional Default values
Reference
Field

Process Logic

Page 3 of 5 Date 3/17/22


Section IV : Test Case and Test Related
Result specification
Format No/ Rev: TC-ABAP-001/ 00

Number: TC-   -   -    (TC-XXX-YYY-999) Prepared on   /  /    


Test Cases (with expected results)
     

Checks performed Details about the test


Test sequence and test results Sequence in which the test would be performed.
Expected Result          

Section I: Unit Testing


Program name:       Test 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

Page 4 of 5 Date 3/17/22


Names and Signatures

     
_______________________________________________________________________________________
Team Lead
     
_______________________________________________________________________________________
Lead Consultant

Page 5 of 5 Date 3/17/22

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy