You are on page 1of 21

FUNCTIONAL SPECIFICATION SCENARIO (BUSINESS AREA): <NA E! BUSINESS PROCESS: < NA E !

PROJECT IDENTIFICATION
Project Name CPI/Project Number Project Type
(CBI, Implementat on, C!!, "p#ra$e, Internal, ot%er&

Cu'tomer Name

Cu'tomer Number

Planne$ !tart/F n '%

!AP Cu'tomer Partner

Project !pon'or

Pro#ram (ana#er

!AP Project (ana#er

Cu'tomer Project (ana#er

Partner Project (ana#er

How to use the Template


[This chapter gives only explanations on the template. Remove it before completing the template.] T% ' $ocument ' nten$e$ to 'pec )y RICEF* object )rom a )unct onal per'pect +e, It - ll be )ollo-e$ by a tec%n cal 'pec ) cat on, T% ' $ocument %a' t%ree ma n 'ect on' .eneral Object n)ormat on, to be ) lle$ n )or all RICEF* object' Object 'pec ) c 'ect on, only rele+ant 'ect on' nee$ to be ) lle$ n, e,#, ) t% ' $ocument 'pec ) e' a report ) ll out t%e #eneral n)ormat on, t%e report 'pec ) c an$ t%e te't con$ t on 'ect on at t%e en$, T% ' $ocument bu l$' an$ re)er' to t-o prece$ n# $ocument' Re/u rement' 0 BPR !olut on $e' #n 1 BPD In a$$ t on, all RICEF* object are con'ol $ate$ n t%e RICEF* l 't 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. t should al!ays 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
2o- to u'e t%e Template,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,3 Purpo'e o) t% ' $ocument,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,4 .eneral Object O+er+ e-,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,5 $rocess Requirements Reference.......................................................................................................% &eneric 'R ()* +escriptions............................................................................................................% Object !pec ) c De' #n,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,6 Reporting ,operational and analytical-.................................................................................................. nterfaces ..........................................................................................................................................// +ata (onversion 0 1istorical +ata ..................................................................................................../2 )nhancements.................................................................................................................................../3 4utput ,e.g. forms- ............................................................................................................................/. 'or5flo! .........................................................................................................................................../6 Te't Con$ t on',,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,78 Document 2 'tory,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,73

Pu"pose o# th$s %o&ume't


The Specification is the basis for the developments that !ill be done in S7$. )rror8 Reference source not found has to verify and approve it formally. Reali9ation starts only after approval. 'ithin the S7$ (ustom +evelopment :ethodology, the Specification is the lin5 bet!een the business requirements ,normally given in the solution proposal- and the technical design ,a separate document-. t has the follo!ing goals8 Reference to the business requirements ,customer requirements- given in the solution proposal. Sho! the mapping into standard S7$ products. +escribe the solution from an external ,user or customer- point of vie!. mplementation details ,database model, report names, and so on- are generally ;4T part of the Specification. [(ustomers shall be enabled to recogni9e that all their requirements are ta5en into consideration. *or approval of the Specification they have to understand the solution.]

(e'e"al O)*e&t O+e"+$ew


OBJECT O9ER9IE* Bu' ne'' Proce'' !AP (o$ule , , , , , , - Report - nterface - (onversion - )nhancement - *orm - 'or5flo!

Object ID !AP Relea'e

Object Type

Object T tle Object De'cr pt on (oc: "p ID / Name Cycle o) Te't n# / !pr nt Cycle Comple; ty o) Object !AP Tran'act on Name ! m lar !AP Tran'act on (/ 0 (< 0 (= 0 (2 Simple 0 :edium 0 (omplex ,follo!ing naming convention guidelinesRe/u re$ De+elopment Complet on Date Pr or ty !AP Pro#ram Name ! m lar !AP Pro#ram ++:4;>> ?o! 0 :edium 0 1igh

F! CONTRO<
Funct onal Con'ultant 1 Aut%or an$ P%one Number Planne$ Date o) F! Complet on F! Appro+e$ By Ot%er Contact an$ P%one Number =Cu'tomer> Proce'' O-ner an$ P%one Number Actual Date o) F! Complet on F! Appro+al $ate Ot%er Contact an$ P%one Number

?ast ;ame, *irst ;ame

?ast ;ame, *irst ;ame

++:4;>> ?ast ;ame, *irst ;ame

++:4;>> ++:4;>>

Proce'' Re/u rement' Re)erence PROCE!! REFERENCE Requirement + Requirement +escription &ap to be addressed 7lternative S7$ Standard Solution .ener c *RICEF De'cr pt on' J"!TIFICATION [Provide a high level description reason from deviation from standard SAP reports or BW reports.

F"NCTIONA< DE!CRIPTION / DE!I.N


[Provide a high level description of the Report and the business requirement that will be addressed.] )xample8 The report !ill allo! users to display contracts that are due to expire and to vie! the details of these contracts

TRAN!ACTION 9O<"(E
[Please provide an indication of the e pected number of records that will need to be read and displa!ed using this report] )xample8 The expected number of records to be displayed on this report is bet!een /@ and =@ from approximately <@@ current contracts

FRE?"ENC@ A TI(IN.
[Please indicate the frequenc! that the report should run" i.e.# Ad $oc% &ail!% Wee'l!% (uarterl! etc% and an! timing considerations that should be applied" i.e.# must be run before )am *onda! morning] )xample8 The report !ill be run on a monthly basis on the last day !or5ing day of the month.

DEPENDENCIE!
[Predecessors and successors]

A"T2ORIBATION RE?"IRE(ENT!
+,ver! authori-ation ob.ect needs to be documented to provide the securit! administrator information on the purpose and use of the ob.ect. /he following sections are the minimal documentation requirements.0

RE<ATED DOC"(ENTATION (ATTAC2 O!! NOTE!, E(AI<!, DO*N<OAD OF ECI!TIN. REPORT, ETC&

O)*e&t Spe&$#$& ,es$-'


Report n# (operat onal an$ analyt cal& Areference to the R ()*' section in the B$+.C REPORTIN. 'R ()*" + FF"xx" R@@/ !E<ECTION CRITERIA [$lease enter the selection criteria that should be available to users before running the report. ndicate if the criteria are optional or mandatory and if any data restrictions should apply] +escription Report Type ,7B7$, B , B4BD+ata )lements Relevant E$ 4!ner

Table0 Structure ;ame

*ield ;ame

*ormat

+efault Galue

Table Galue0 (hec5box0 Radio Button0 Radio Button &roup

Select 4ption or $arameter

:andatory or 4ptional

*ield ?abels

7ny grouping of selection screen fields into bloc5sH Title of Selection Screen Bloc5H 7ny preferred layout of the Selection ScreenH

F"NCTIONA< DE!I.N, 9A<IDATION AND 9ARIANT! 'hat is the data to be extractedH +oes the Selection (riteria include the full primary 5eys of the tables from !hich data is to be extractedH

1o! should the data be processed in the program I functional logicH

REPORT O"TP"T 4utput :ethod [Please indicate the e pected output method1s# for the report] )xample8 Saved to *ile 0 Sent to print 0 Send to email account 0 +o!nload to excel

:ain 1eading [Provide the main heading field for the report] )xample8 The main report heading !ill be8 (ontracts ;earing )xpiry

Sub 1eading [Provide an! required sub2headings and brea's required in the report] )xample8 There !ill be a sub section under the main contract information detailing the date and time the report !as executed and the users username

?7>4JT Table0Structure ;ame

*ield ;ame

*ormat ,ie decimal places-

+efault Galue

(olumn ;ame

Translation Rule

$lease list the sequence of the fields ,S7$ *ield names- in !hich the output must be displayedH

+R ??+4'; R)KJ R):);TS

T4T7? ;& [3ist an! totaling or other calculation requirements for the report] )xample8 ;umber of contracts matching user selection criteria to be displayed at the bottom of the report 7ny page"brea5 requirementsH

S4RT ;& [3ist an! sorting requirements for the report] )xample8 Jsers !ill be able to sort on contract type and vendor. +efault sort sequence !ill be by contract type. 7ny page"brea5 requirementsH

$7&) BR)7E [Provide details of an! page brea'ing requirements that should be used in addition to field brea's] )xample8 $age brea5s !ill be used !here necessary to prevent overflo! of retrieved data

)RR4R 17;+? ;& [4nclude potential errors% notification procedures% and contingenc! procedures.] Typical errors include8 ;o data found for given selection criteria.

10

Inter)ace' A dentify all interfaces required to provide inputs to or outputs from this part of the process. $rovide a functional description of the interfaces including the source and type of data.C INTERFACE 'R ( )*" + FF"xx" @@/ +escription nterface :ethod 7pplications +ata )lements *requency 0 Golumes 4!ner

INTERFACE PROCE!! F<O* DIA.RA(, INC<,TRAN!FER (ET2OD/ NET*ORD INTE.RATION [Please insert an interface flow diagram showing source and target s!stems with directions] /his will include the screen flow diagram% specif! the proposed load method 1e.g. 4&56% batch transaction processing#% and the proposed transfer program name and the inbound7outbound file format 1e.g. .t t% . ls#]

FI<E !PECIFIC! [8ilenames% deliver! method% file t!pe 1ascii% comma2delimited% etc#

11

(APPIN. !AP FIE<D! TO !O"RCE / TAR.ET


[Please provide details of the e pected mapping between the Source 7 /arget s!stem and SAP fields. /his can either be done within a table in this document or as an attached *apping &ocument. Specifications for the following elements should be present on the *apping document 1where applicable#9 S7$ Transaction S7$ Screen number S7$ Table name S7$ *ield name ,functionalS7$ *ield name ,technicalS7$ field length S7$ field type :andatory 0 4ptional flag Source 0 Target *ield + Source 0 Target *ield ;ame ,functional 0 technicalSource 0 Target *ield length Source 0 Target *ield type :apping +etails mplementation (omments

:apping.xls

12

RECONCI<IATION PROCED"RE! A A"DIT RE?"IRE(ENT!


Report n# [Please describe an! reporting that is e pected to be provided in support of this interface]

Approac% [&etail the method of data reconciliation e.g. reports produced in SAP]

(etr c' [Provide details on the metrics used to facilitate reconciliation e.g. Record 6ount]

Error 2an$l n# [4nclude potential errors% notification procedures% and contingenc! procedures.]

13

Data Con+er' on / 2 'tor cal Data A;ote all master and transactional data conversion requirements. $lease note specific fields that are unique to this design and the business requirement that drives that design. ;ote !hether manual and automated data conversion requirements. $rovide details of all data required from ?egacy Systems ,(onsider System name, level of detail, time dimension-. dentify requirements for historical data conversion mandatory for the process. This is not meant to be an exhaustive functional spec but a place to list conversions related to this process.C CON9ER!ION! ''R () *" + (onversion 4bject Source (onversion 7ctivities ,e.g. cleansing(onversion :ethod ,manual 0 automatedL of 4bjects to be converted 4!ner

FF"xx" (@@/ 3(APPIN. !AP FIE<D! TO !O"RCE / TAR.ET [Please provide details of the e pected mapping between the Source 7 /arget s!stem and SAP fields. /his can either be done within a table in this document or as an attached *apping &ocument. Specifications for the following elements should be present on the *apping document 1where applicable#9 S7$ Transaction S7$ Screen number S7$ Table name S7$ *ield name ,functionalS7$ *ield name ,technicalS7$ field length S7$ field type :andatory 0 4ptional flag Source 0 Target *ield + Source 0 Target *ield ;ame ,functional 0 technicalSource 0 Target *ield length Source 0 Target *ield type :apping +etails mplementation (omments

:apping.xls

14

RECONCI<IATION PROCED"RE! A A"DIT RE?"IRE(ENT!


Report n# [Please describe an! reporting that is e pected to be provided in support of this interface]

Approac% [&etail the method of data reconciliation e.g. reports produced in SAP]

(etr c' [Provide details on the metrics used to facilitate reconciliation e.g. Record 6ount]

Error 2an$l n# [4nclude potential errors% notification procedures% and contingenc! procedures.]

15

En%ancement' ASpecify the enhancement based on the proposed gap resolutions listed in the +etailed Requirements and +esign documents. $rovide as much detail on the requirements and design considerations as you can. f there is a large enhancement then consider detailing that in a separate design or functional spec. document. C EN2ANCE(ENT! 'R ( )*" + FF"xx" )@@/ +escription +ata 4bject ,Sales 4rder*unctional &ap 7lternative S7$ Standard Reason 4!ner

F"NCTIONA< DE!I.N / F<O*, 9A<IDATION AND 9ARIANT! Flo[Please provide the flow of ob.ect to be enhanced. 8or e ample in the program :;<=> go to screen7Sub screen ?@? there modif!7add a field]

De' #n 1o! should the data be processed in the program I functional logicH

16

Output (e,#, )orm'& A dentify outputs and formsC O"TP"T 'R ( )*" + FF"xx" 4@@/ PROCE!! F<O* DIA.RA( [Please insert a flow diagram describing the form output procedure e.g. Purchase 5rder input using transaction *,A?B" save Purchase 5rder automaticall! generates Purchase 5rder 8orm printout] +escription +ata 4bject ,Sales 4rder4utput Type ,*orm, )+ , etc.*requency Golumes 4!ner

FOR( <A@O"T [Please provide a sample la!out for first% subsequent and last pages% detailing actual positions of output fields% fonts% font si-es] Please indicate if there is pre2printed stoc' and which portions are on the pre2printed stoc' )xample8

Form Title ser: xxxxx


2

Date: xxxxx

ID xxxxx xxxxx xxxxx xxxxx


3

Value xxxxx xxxxx xxxxx xxxxx


4

Description xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx


5

17

PRINTER RE?"IRE(ENT! +uplex $rinting, label printing, label dimensions, standard, etc.

<E.A< RE?"IRE(ENT! +etermine if there is any text that is required legally on the form, including font si9e, text to be printed on the bac5 of documents,

ECI!TIN. !A(P<E FOR(! [4f an e isting program is available to be enhanced% provide details in this section] $rogram ;ame :enu 0 Transaction ?egacy *orm name ?egacy $rogram Title ?egacy *orm ;umber Related Transactions

18

*or:)loA dentify !or5flo! requirements for this process. $rovide detailed requirements for the !or5flo!. e.g., purchase order approval process and authority levels etc.C *ORDF<O* 'R ( )*" + FF"xx" '@@/ +escription Business 0 +ata 4bject ,Sales 4rder)ngaged $arties 4!ner

PROCE!! F<O* DIA.RA( [Please insert a flow diagram of the wor'flow]

TRI..ER E9ENT! Tran'act on' an$ Batc% Pro#ram' t%at tr ##er t%e -or:)lo-

!tart Con$ t on'

R"<E! AND DETER(INATION !tan$ar$ Rule' <ate't En$, <ate't !tart Requested )nd , Requested start

19

Test Co'%$t$o's
B"!INE!! TE!T CONDITION! (TO BE F"RNI!2ED B@ T2E F"NCTIONA< CON!"<TANT&
[Please indicate the business level test conditions that should be used to verif! successful operations of the Report] [&ocument all technical scenarios associated with this development. , amples would include ?# testing an error2free run" A# testing the e ception processes" C# testing the error handling.] [&ocument all control scenarios associated with this development. , amples would include ?# Rounding of dollars and cents" A# Audit trail processing" C# Reconciliation reporting] Scenario L nput Selection (riteria )xpected Result

20

,o&ume't H$sto".
A"T2OR! A PARTICIPANT! Role Business System 7nalyst $roject $rocess 4!ner Business Jnit $rocess 4!ner (onsultant 'or5shop $articipant ;ame

RE9I!ION 2I!TOR@ +ate AA +ate CC

+ocument Gersion /.@

+ocument Revision +escription +raft for customer revie!

7uthor AA ;ame CC

RE9IE*ED AND APPRO9ED B@ ;ame Title AA;7:)CC AA;7:)CC AA;7:)CC AA;7:)CC AA;7:)CC Business System 7nalyst $roject $rocess 4!ner Business Jnit $rocess 4!ner (orporate $rocess 4!ner nternal 7udit

+ate

7pproved

21