You are on page 1of 9

Report Functional Specification

(Name)
Version 1.0

Page 1 of 9
DOCUMENT REVISION HISTORY

Version Revision Date Author(s) Revision Notes

NOTE: Localizations should be captured using Track Changes to redline content within
the document.

Page 2 of 9
CONTENTS
1.0 Request Details........................................................4
2.0 General Information.................................................4
3.0 Standard/Application Text(s)..................................................................................................................4

4.0 Functional Requirements..........................................5


4.1 Detailed Process Description.................................................................................................................5
4.2 Business Justification.............................................................................................................................5
4.3 Security / Authorization / Control Requirements....................................................................................5
4.4 Assumptions..........................................................................................................................................5
4.5 Dependencies........................................................................................................................................5
4.6 Additional Information............................................................................................................................5

5.0 Report Details..........................................................7


5.1 Selection Screen....................................................................................................................................7
5.2 Layout....................................................................................................................................................7
5.3 Special Requirements ...........................................................................................................................7

6.0 Unit Test Scenarios..................................................9


7.0 Open Design Questions.............................................9

Page 3 of 9
1.0 Request Details
Title
ID Type Report/Form
Process Team Author
Phone
Email
Other Key Contacts Related Objects
SAP System and Version Process Doc. Ref
SAP Module and Workstep / Task
Sub module
Priority Mandatory ( Required by law) Release Rel 1
Essential ( Business critical) Rel 2
Important Rel 3
Nice to Have
Complexity High / Medium / Low

2.0 General Information


Object Type Operational Report / Analytical Report / Form
Output medium Online / Local Printer / System Printer / E-Mail / Fax / Excel Extract/Etc
Paper requirement Paper Size / Special Forms
Initiation Process Manual / Scheduled Job / Event (Please specify event)
Run Frequency On-demand / Hourly / Daily / Weekly / Monthly / Other (Please specify)
No. of pages Average Run / Peak Run
Abbreviations

Form Specific Information


Form type P.O. / Invoice / Customer Statement / Remittance Advice / Etc.
Output Type
SAP Standard program Specify the SAP program to trigger the Form
SAP Standard Form Specify the SAP standard Form name
Logo
Letterhead
Other
• Please attach sample Logo, etc.

3.0 Standard/Application Text(s)


Standard / Text / Field name Object Text ID Language Description
Application text

• Font, Size, Format and special instructions

Page 4 of 9
4.0 Functional Requirements

4.1 Detailed Process Description

• Please provide a detailed description of the requirement, including detailed Process Description,
SAP and Custom tables involved

4.2 Business Justification

Is there an alternative in the


standard system? Please list
any standard Report/form that is
available.
Reasons why alternative is not
acceptable

4.3 Security / Authorization / Control Requirements

• Please describe any specific Security/Authorization requirements

4.4 Assumptions

4.5 Dependencies

• Please provide any configuration and master data prerequisites. Include predecessor and
successor processes if any

4.6 Additional Information

• Please specify transaction codes used for identifying fields any other related transaction codes
and data related information, screenshots for the required fields etc.
• Please ensure that all transactions used for validating the fields are listed here
• Non-Functional Requirements
[The Non-functional Requirements are categorized in this section. Input the requirements For
the relevant category. If the system doesn’t have requirements pertaining to some of the list
below, Document ‘Not Applicable’ for that Item. If necessary, add new itemsto the template
that are pertinent to your project.

Page 5 of 9
o Architectural requirements
o Performance requirements
o Usability requirements
o Legal Requirements
o Globalization Requirements
o Packaging Requirements
o Hardware Requirements
o Software Requirements
o Network Requirements
o Portability Requirements
o Enterprise Operations Monitoring (EoM) Requirements
o Security Management Requirements

Page 6 of 9
5.0 Report Details

5.1 Selection Screen


(Not applicable for standard forms)
Field Name Selection Type of Search Validation Default Comments
Text/ Field Help / Pick Required Value (Range, Single /
Description (Check Box List / List (Y / N) Multiple
/ Radio of Please list Selection,
Button / possible any Mandatory,
Select- values special Optional, etc.)
option / Required rules
Parameter) (Y / N)

• To get the fieldname from the screen: Please press F1 and then click on the technical information
button and then take the screen field name from the technical information screen
• Please update the SAP transaction code(s) used to find these field either in the comments
section

5.2 Layout
Attach Sample Here

Narrative Flow

• Please attach sample layout and example in PDF, XLS or DOC format. Please do not copy and
paste

5.3 Special Requirements

• Please provide any special requirements such as report distribution requirements, etc.

Page 7 of 9
• Please describe the sort order numerically. All sorts are assumed as ascending unless stated otherwise in the comments section
Report Details
# Report Field Field Definition Report Sort Total SAP Table-field Processing Description /
Name Level Calculation Logic
Header/
Item

Page 8 of 9
6.0 Unit Test Scenarios
# Scenario Description

• Please provide any unit test scenarios from a business perspective that need to be performed
• Please document any test data that can be used

7.0 Open Design Questions


No Issue / Resolution Description Name Date Status

Page 9 of 9