You are on page 1of 5

Functional Specification

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

Version: 00 Issue Date 04-04-2018


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

Revision History
Version Date Description of changes

Responsible
For concept – NAME For Implementation -
Section I: Justification
Area (R/3 SD Date 04/04/2018
Module): (dd/mm/yyyy):

Requested by: Functional Consultant’s Name

Brief description: 1. Trigger a mail to concerned to raise Invoice

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: Otherwise it has to be performed manually.

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)
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 Name Comments
Date Date

Team Lead Lead Consultant


Date Date / /

Approved by Project Management Team / /


(in case of Application development)

Received Team Lead/ Lead Consultant


Date
Description and Purpose:

1. Trigger of Email

Trigger of email for the list of open sales order for billing.
Email to be triggered on every 25th of the month.
Email to be received by the users (specified) in outlook.
The email layout is embedded below.

Email 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

Base of the check point is sales order and following the logic to trigger a list of open sales order to be
billed.
Check the status of the line item for vbap <> 'C'
Select vbap-aubel for vbak-vbtyp = 'B' (Quotation).
Select those quotations which has valid from and valid to falls between schedule date i.e 25th every
month.
If above condition satisfies then
Trigger a mail to mail ids mentioned in set. (MAILID_ITSL)
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


Names and Signatures

_______________________________________________________________________________________
Team Lead

_______________________________________________________________________________________
Lead Consultant

You might also like