FUNCTIONAL SPECIFICATION

PROJECT IDENTIFICATION

Project Name CPI/Project Number Project Type(CBI, Implementation, CSS, Upgrade, Internal, other)

Customer Name Customer Number Planned Start/Finish

SAP Customer Partner Project Sponsor Program Manager

SAP Project Manager Customer Project Manager Partner Project Manager

How to use the TemplateThis document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical

specification during Realization. A Functional Specification has three main sections

General Object information, to be filled in for all RICEFW objects

Object specific details

Test conditions and considerations

This document builds and refers to two preceding documents

Requirements - BPR

Solution design – BPD

In addition, all RICEFW object are consolidated in the RICEFW list

[Please note: The project manager and the quality manager have to revise this template before it is used for the project

and especially before it is given to the customer. Sometimes instructions, guidelines, explanations, hints, and tips are

provided. It should always be removed from the template for the project.

Top-level chapters may not be deleted or inserted; required additions should be made as sub-chapters to existing

chapters to provide a consistent representation of this document to the customer. ]

TABLE OF CONTENTS

How to use the Template.................................................................................................................1General Object Overview................................................................................................................3Process Requirements Reference.....................................................................................................4Generic WRICEF Descriptions..........................................................................................................4Object Specific Design....................................................................................................................6Forms / Output...................................................................................................................................6Test Conditions................................................................................................................................8Document History............................................................................................................................9

2

General Object Overview

OBJECT OVERVIEW

Object IDBusiness Process

SAP ReleaseSAP Module

Object Type

( ) Report( ) Interface( ) Conversion( ) Enhancement( ) Form( ) Workflow

Object Title

Object Description

Mock Up ID / Name

Cycle of Testing / Sprint Cycle

C1 / C2 / C3 / C4Required Development Completion Date

DDMONYY

Complexity of Object Simple / Medium / Complex Priority Low / Medium / High

SAP Transaction Name

(following naming convention guidelines)

SAP Program Name

Similar SAP Transaction

Similar SAP Program

FS CONTROL

Functional Consultant – Author and Phone Number

Last Name, First Name<Customer> Process Owner and Phone Number

Last Name, First Name

Planned Date of FS Completion

DDMONYY Actual Date of FS Completion

DDMONYY

FS Approved By Last Name, First Name FS Approval date DDMONYY

Other Contact and Phone Number

Other Contact and Phone Number

3

Process Requirements Reference

PROCESS REFERENCE

Requirement IDRequirement DescriptionGap to be addressedAlternative SAP Standard Solution

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

4

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)

5

ID Value Description

xxxxx 3

xxxxxxxxxxxxxxx

xxxxx 4

xxxxxxxxxxxxxxx

xxxxxxxxxx 5

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Form Title Date: xxxxx 1

User: xxxxx 2

Object Specific Design

Forms / Output <Identify outputs and forms>

OUTPUT

WRICEF-ID

Description Data Object (Sales Order)

Output Type (Form, EDI, etc.)

Frequency Volumes Owner

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:

6

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

LEGAL REQUIREMENTSDetermine 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

7

Test ConditionsBUSINESS 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

8

Document HistoryAUTHORS & PARTICIPANTSRole Name

Business System Analyst

Project Process Owner

Business Unit Process Owner

Consultant

Workshop Participant

REVISION HISTORYDate Document Version Document Revision

DescriptionAuthor

<< Date >> 1.0 Draft for customer review

<< Name >>

REVIEWED AND APPROVED BYName Title Date Approved

<<NAME>> Business System Analyst

<<NAME>> Project Process Owner

<<NAME>> Business Unit Process Owner

<<NAME>> Corporate Process Owner

<<NAME>> Internal Audit

9