Functional Specification(FS)- For Forms

[Type the abstract of the document here. The abstract is typically a short summary of the contents of the
document. Type the abstract of the document here. The abstract is typically a short summary of the contents of
the document.]
Author Document Location (repository/path/name)
<Author> <Document location>

Version Status Date (YYYY-MM-DD) Document

Classification
0.1 Final <Date> Confidential

REVISION HISTORY
Date Document Version Document Revision Description Author

<< Date >> 1.0 Draft for customer review << Name >>

REVIEWED AND APPROVED BY

Name Title Date Signature

<<NAME>> Business System Analyst

<<NAME>> Project Process Owner
<<NAME>> Business Unit Process
Owner
<<NAME>> Corporate Process Owner
<<NAME>> Internal Audit

Project Identification (Fill if applicable otherwise leave blank)

Project Name
Customer Name
SAP Project Manager
Customer Project Manager
Table of Contents

1 General Object Overview.........................................................................................................................3

1.1 Process Requirements Reference....................................................................................................3
1.2 Generic WRICEF Descriptions..........................................................................................................3
2 Object Specific Design.............................................................................................................................5
3 Test Conditions.......................................................................................................................................16
1 General Object Overview
OBJECT OVERVIEW

Business
Object ID
Process
SAP Release SAP Module
( ) Report
( ) Interface
( ) Conversion
Object Type
( ) Enhancement
( ) Form
( ) Workflow
Object Title

Object Description

Mock Up ID / Name
Required
Cycle of Testing / Development
C1 / C2 / C3 / C4 DDMONYY
Sprint Cycle Completion
Date
Complexity of Simple / Medium /
Priority Low / Medium / High
Object Complex
SAP Transaction (following naming SAP Program
Name convention guidelines) Name
Similar SAP Similar SAP
Transaction Program
FS CONTROL
<Customer>
Functional
Process Owner
Consultant – Author Last Name, First Name Last Name, First Name
and Phone
and Phone Number
Number
Planned Date of FS Actual Date of
DDMONYY DDMONYY
Completion FS Completion
FS Approval
FS Approved By Last Name, First Name DDMONYY
date
Other Contact
Other Contact and
and Phone
Phone Number
Number

1.1 Process Requirements Reference

PROCESS REFERENCE
Requirement ID
Requirement
Description
Gap to be
addressed
Alternative SAP
Standard Solution

1.2 Generic WRICEF Descriptions

JUSTIFICATION
< [Provide a high level description reason from deviation from standard SAP reports or BW reports.>

FUNCTIONAL DESCRIPTION / DESIGN

< [Provide a high level description of the Report and the business requirement that will be addressed.]

Example:

The report will allow users to display contracts that are due to expire and to view the details of these contracts>

TRANSACTION VOLUME
<[Please provide an indication of the expected number of records that will need to be read and displayed using this report]

Example:

The expected number of records to be displayed on this report is between 10 and 30 from approximately 200 current contracts>

FREQUENCY & TIMING

<[Please indicate the frequency that the report should run; i.e.) Ad Hoc, Daily, Weekly, Quarterly etc, and any timing
considerations that should be applied; i.e.) must be run before 7am Monday morning]

Example:

The report will be run on a monthly basis on the last day working day of the month.>

DEPENDENCIES
<[Predecessors and successors]>

AUTHORIZATION REQUIREMENTS
 <Every authorization object needs to be documented to provide the security administrator information on the purpose and use of
the object. The following sections are the minimal documentation requirements.>

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING REPORT, ETC)

2 Object Specific Design

2.1 Output (e.g. forms)

<Identify outputs and forms>

OUTPUT
WRIC Description Data Object Output Type Frequency Volumes Owner
EF-ID (Sales (Form, EDI, etc.)
Order)
XX-xx-
O001

PROCESS FLOW DIAGRAM

[Please insert a flow diagram describing the form output procedure e.g. Purchase Order input using transaction
ME21N; save Purchase Order automatically generates Purchase Order Form printout]

FORM LAYOUT
Please provide a sample layout for first, subsequent and last pages, detailing actual positions of output fields,
fonts, font sizes]

Please indicate if there is pre-printed stock and which portions are on the pre-printed stock

Example:

1
Form Title Date: xxxxx
2
User: xxxxx

ID Value Description
3 4 5
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx

PRINTER REQUIREMENTS
Duplex Printing, label printing, label dimensions, standard, etc.

LEGAL REQUIREMENTS
Determine if there is any text that is required legally on the form, including font size, text to be printed on the back
of documents,

EXISTING SAMPLE FORMS

[If an existing program is available to be enhanced, provide details in this section]
• Program Name
• Menu / Transaction
• Legacy Form name
• Legacy Program Title
• Legacy Form Number
• Related Transactions
3 Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)
[Please indicate the business level test conditions that should be used to verify successful operations of the Report]

[Document all technical scenarios associated with this development. Examples would include 1) testing an error-free run; 2)
testing the exception processes; 3) testing the error handling.]

[Document all control scenarios associated with this development. Examples would include 1) Rounding of dollars and cents; 2)
Audit trail processing; 3) Reconciliation reporting]

Scenario # Input Selection Criteria Expected Result

Intentionally left blank