FUNCTIONAL SPECIFICATION

[Title]
[Company]

Role and Reason for Approval

Role Reason for Approval

Author The author is signing to confirm that this document has been
prepared in accordance with the programme document
management process, that relevant input from any contributory
authors has been included and that an appropriate review/editing
process has been conducted.
SAP Solution The SAP Solution Lead or Architect is signing, on behalf of the
Lead or Workstream, to confirm that this Functional Specification meets the
Architect Acceptance Criteria expected of it and assigned to it in the
Deliverable Quality Log.
SAP The SAP Development Lead or Manager is signing, on behalf of the
Development Development Team, to confirm that this Functional Specification
Lead or meets the Acceptance Criteria expected of it and assigned to it in
Manager the Deliverable Quality Log.

Note. Master copy of this document, with signatories, is held on Solution Manager

DATE: 01/05/2020
Version Date Name Alteration Reason

Table of Content
1 Context 3
1.1 Business Background 3
1.2 Why is SAP standard not appropriate or sufficient? 3
1.3 Alternative Approaches Considered 3
1.4 Out of Scope 3
1.5 Assumptions 3
1.6 Dependencies 3
1.7 Links 3
2 Solution Design 4
2.1 Solution 4
2.2 Scenario 4
2.3 Authorisation 4
2.4 Validation 4
2.5 Rules 4
2.6 Table of Field Mappings 4
2.7 Process Flow Diagram 4
2.8 Report Output 4
2.9 Drilldown and follow-on activities 4
2.10 Batch Frequency and Timing 4
2.11 Unit Test Case 5
Appendix 1. Selection Screen Requirements 6
3 FS Review Checklist 7

Page 2 of 7
1 Context

1.1 Business Background

1.2 Why is SAP standard not appropriate or sufficient?

1.3 Alternative Approaches Considered

1.4 Out of Scope

1.5 Assumptions

1.6 Dependencies

1.7 Links

Page 3 of 7
2 Solution Design

2.1 Solution

2.2 Scenario

2.3 Authorisation

2.4 Validation

2.5 Rules

2.6 Table of Field Mappings

2.7 Process Flow Diagram

2.8 Report Output

2.9 Drilldown and follow-on activities

2.10 Batch Frequency and Timing

Page 4 of 7
2.11 Unit Test Case

Scenario Input Selection Criteria Expected Result Results

Page 5 of 7
FS [Title]
{O2C}

Appendix 1. Selection Screen Requirements

Table/Structure Name Field Name Format Default Value Table Select Single, Mandatory Field Labels
Value / Option or Range, or
Checkbox Paramete Multiple Optional
/ Radio r ranges
Button /
Radio
Button
Group

Table 1 Selection Parameters

Any grouping of selection screen fields into blocks? Title of Selection Screen Block? Any preferred layout of the Selection Screen?

Page 6 of 7
FS [Title]
{O2C}

3 FS Review Checklist

Please fill in the respective tabs of the attached FS review checklist. This checklist ensures the availability of the content for the development team to
start review process. The FS author should fill in the column E (Self Review) and the development Team Lead/Developer will review and reach out to
the FS owner in case of additional information (if needed). All the high priority ones must be fulfilled for the development to begin the review. Any
Categories/Points which are not applicable for the current FSD can be filled in with a “N/A”.

FS Review
Checklist.xlsx

Page 7 of 7