Вы находитесь на странице: 1из 11

FUNCTIONAL SPECIFICATION

Scenario (Business Area): <Name>


Business Process: < Name >

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 Template


This 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 1
General Object Overview 3
Process Requirements Reference.......................................................................................................4
Generic WRICEF Descriptions............................................................................................................4
Object Specific Design 6
Reporting (operational and analytical).................................................................................................6
Test Conditions 10
Document History 11

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 2
General Object Overview

OBJECT OVERVIEW

Business
Object ID
Process

SAP
SAP Release
Module
( ) Report
( ) Interface
( ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow

Object Title

Object Description

Mock Up ID / Name

Required
Cycle of Testing / C1 / C2 / C3 / C4 DDMONYY
Development
Sprint Cycle
Completion Date

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

SAP Transaction (following naming SAP Program


Name convention guidelines) Name

Similar SAP Similar SAP


Transaction Program

FS CONTROL

<Customer>
Functional Consultant
Last Name, First Name Process Owner Last Name, First Name
– Author and Phone
and Phone
Number
Number

Planned Date of FS DDMONYY Actual Date of FS DDMONYY


Completion Completion

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

Other Contact and Other Contact and


Phone Number Phone Number

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 3
Process Requirements Reference
PROCESS REFERENCE
Requirement ID
Requirement
Description
Gap to be addressed
Alternative 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

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 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)

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 5
Object Specific Design
Reporting (operational and analytical)
<reference to the RICEFW section in the BPD.>

REPORTING
WRICEF- Description Report Type Data Elements Relevant KPI Owner
ID (ABAP, BI,
BOBJ)
XX-xx-
R001

SELECTION CRITERIA
[Please enter the selection criteria that should be available to users before running the report. Indicate
if the criteria are optional or mandatory and if any data restrictions should apply]

Table/ Field Name Format Default Table Select Mandatory Field


Structure Value Value/ Option or or Labels
Name Checkbox/ Parameter Optional
Radio
Button/
Radio
Button
Group

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

Any preferred layout of the Selection Screen?

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 6
FUNCTIONAL DESIGN, VALIDATION AND VARIANTS
What is the data to be extracted? Does the Selection Criteria include the full primary keys of the tables
from which data is to be extracted?

How should the data be processed in the program – functional logic?

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 7
REPORT OUTPUT

Output Method
[Please indicate the expected output method(s) for the report]
Example:
Saved to File / Sent to print / Send to email account / Download to excel

Main Heading
[Provide the main heading field for the report]
Example:
The main report heading will be: Contracts Nearing Expiry

Sub Heading
[Provide any required sub-headings and breaks required in the report]

Example:
There will be a sub section under the main contract information detailing the date and time the report
was executed and the users username

LAYOUT
Table/Structure Field Format Default Value Column Name Translation Rule
Name Name (ie
decimal
places)

Please list the sequence of the fields (SAP Field names) in which the output must be displayed?

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 8
DRILLDOWN REQUIREMENTS

TOTALING
[List any totaling or other calculation requirements for the report]
Example:
Number of contracts matching user selection criteria to be displayed at the bottom of the report

Any page-break requirements?

SORTING
[List any sorting requirements for the report]
Example:
Users will be able to sort on contract type and vendor. Default sort sequence will be by contract type.

Any page-break requirements?

PAGE BREAK
[Provide details of any page breaking requirements that should be used in addition to field breaks]
Example:
Page breaks will be used where necessary to prevent overflow of retrieved data

ERROR HANDLING
[Include potential errors, notification procedures, and contingency procedures.]
Typical errors include: No data found for given selection criteria.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 9
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

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 10
Document History
AUTHORS & PARTICIPANTS
Role Name
Business System Analyst

Project Process Owner

Business Unit Process Owner

Consultant

Workshop Participant

REVISION HISTORY
Date Document Version Document Revision Author
Description
<< Date >> 1.0 Draft for customer << Name >>
review

REVIEWED AND APPROVED BY


Name Title Date Approved

<<NAME>> Business System Analyst


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

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 11