PROJECTIDENTIFICATION

FUNCTIONAL
SPECIFICATION
ProjectName
CPI/ProjectNumber

ProjectType

CustomerName

PlannedStart/Finish

Scenario (Business Area): <Name>

Business Process: < Name >

CustomerNumber

(CBI,Implementation,CSS,Upgrade,Internal,other)

SAPCustomerPartner

ProjectSponsor

ProgramManager

SAPProjectManager

CustomerProjectManager

PartnerProjectManager

How to use the Template

[Thischaptergivesonlyexplanationsonthetemplate.Removeitbeforecompletingthetemplate.]
ThisdocumentisintendedtospecifyRICEFWobjectfromafunctionalperspective.Itwillbefollowedbya
technicalspecification.Thisdocumenthasthreemainsections
x GeneralObjectinformation,tobefilledinforallRICEFWobjects
x Objectspecificsection,onlyrelevantsectionsneedtobefilledin,e.g.ifthisdocumentspecifiesa
reportfilloutthegeneralinformation,thereportspecificandthetestconditionsectionattheend.
Thisdocumentbuildsandreferstotwoprecedingdocuments
x RequirementsBPR
x SolutiondesignBPD
Inaddition,allRICEFWobjectareconsolidatedintheRICEFWlist
Theprojectmanagerandthequalitymanagerhavetorevisethistemplatebeforeitisusedfortheprojectand
especiallybeforeitisgiventothecustomer.Sometimesinstructions,guidelines,explanations,hints,andtipsare
provided.Itshouldalwaysberemovedfromthetemplatefortheproject.
Toplevelchaptersmaynotbedeletedorinsertedrequiredadditionsshouldbemadeassubchapterstoexisting
chapterstoprovideaconsistentrepresentationofthisdocumenttothecustomer.]

TABLE OF CONTENTS
HowtousetheTemplate1
Purposeofthisdocument
3
GeneralObjectOverview
4
ProcessRequirementsReference
GenericWRICEFDescriptions
ObjectSpecificDesign 7
Reporting(operationalandanalytical)
Interfaces
DataConversion/HistoricalData
Enhancements
Output(e.g.forms)
Workflow
TestConditions 20
DocumentHistory 21

5
5
7
11
14
16
17
19

Purpose of this document

TheSpecificationisthebasisforthedevelopmentsthatwillbedoneinSAP.CustomerNamehastoverifyand
approveitformally.Realizationstartsonlyafterapproval.
WithintheSAPCustomDevelopmentMethodology,theSpecificationisthelinkbetweenthebusinessrequirements
(normallygiveninthesolutionproposal)andthetechnicaldesign(aseparatedocument).Ithasthefollowinggoals:
x Referencetothebusinessrequirements(customerrequirements)giveninthesolutionproposal.
x ShowthemappingintostandardSAPproducts.
x Describethesolutionfromanexternal(userorcustomer)pointofview.
Implementationdetails(databasemodel,reportnames,andsoon)aregenerallyNOTpartoftheSpecification.
[Customersshallbeenabledtorecognizethatalltheirrequirementsaretakenintoconsideration.Forapprovalofthe
Specificationtheyhavetounderstandthesolution.]

General Object Overview

OBJECTOVERVIEW
ObjectID

Business
Process

SAPRelease

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

ObjectType

ObjectTitle
ObjectDescription
MockUpID/Name
CycleofTesting/
SprintCycle
ComplexityofObject
SAPTransaction
Name

C1/C2/C3/C4
Simple/Medium/Complex
(followingnaming
conventionguidelines)

SimilarSAP
Transaction

Required
Development
CompletionDate

DDMONYY

Priority

Low/Medium/High

SAPProgram
Name
SimilarSAP
Program

FSCONTROL
FunctionalConsultant
AuthorandPhone
Number
PlannedDateofFS
Completion
FSApprovedBy
OtherContactand
PhoneNumber

LastName,FirstName

DDMONYY
LastName,FirstName

<Customer>
ProcessOwner
andPhone
Number

LastName,FirstName

ActualDateofFS
Completion

DDMONYY

FSApprovaldate

DDMONYY

OtherContactand
PhoneNumber

ProcessRequirementsReference
PROCESSREFERENCE
RequirementID
Requirement
Description
Gaptobeaddressed
AlternativeSAP
StandardSolution
GenericWRICEFDescriptions
JUSTIFICATION
[ProvideahighleveldescriptionreasonfromdeviationfromstandardSAPreportsorBWreports.

FUNCTIONALDESCRIPTION/DESIGN

[ProvideahighleveldescriptionoftheReportandthebusinessrequirementthatwillbeaddressed.]
Example:
Thereportwillallowuserstodisplaycontractsthatareduetoexpireandtoviewthedetailsofthese
contracts

TRANSACTIONVOLUME

[Pleaseprovideanindicationoftheexpectednumberofrecordsthatwillneedtobereadanddisplayed
usingthisreport]
Example:
Theexpectednumberofrecordstobedisplayedonthisreportisbetween10and30from
approximately200currentcontracts

FREQUENCY&TIMING

[Pleaseindicatethefrequencythatthereportshouldruni.e.)AdHoc,Daily,Weekly,Quarterlyetc,
andanytimingconsiderationsthatshouldbeappliedi.e.)mustberunbefore7amMondaymorning]
Example:
Thereportwillberunonamonthlybasisonthelastdayworkingdayofthemonth.

DEPENDENCIES

[Predecessorsandsuccessors]

AUTHORIZATIONREQUIREMENTS

<Everyauthorizationobjectneedstobedocumentedtoprovidethesecurityadministratorinformation
onthepurposeanduseoftheobject.Thefollowingsectionsaretheminimaldocumentation
requirements.>

RELATEDDOCUMENTATION(ATTACHOSSNOTES,EMAILS,DOWNLOADOFEXISTINGREPORT,ETC)

Object Specific Design

Reporting(operationalandanalytical)
<referencetotheRICEFWsectionintheBPD.>
REPORTING
WRICEF
ID

Description

ReportType
(ABAP,BI,
BOBJ)

DataElements

RelevantKPI

Owner

XXxx
R001
SELECTIONCRITERIA
[Pleaseentertheselectioncriteriathatshouldbeavailabletousersbeforerunningthereport.Indicate
ifthecriteriaareoptionalormandatoryandifanydatarestrictionsshouldapply]

Table/
FieldName
Structure
Name

Format

Default Table
Value
Value/
Checkbox/
Radio
Button/
Radio
Button
Group

Select
Optionor
Parameter

Mandatory Field
or
Labels
Optional

Anygroupingofselectionscreenfieldsintoblocks?TitleofSelectionScreenBlock?
AnypreferredlayoutoftheSelectionScreen?

FUNCTIONALDESIGN,VALIDATIONANDVARIANTS
Whatisthedatatobeextracted?DoestheSelectionCriteriaincludethefullprimarykeysofthetables
fromwhichdataistobeextracted?

Howshouldthedatabeprocessedintheprogramfunctionallogic?

REPORTOUTPUT
OutputMethod
[Pleaseindicatetheexpectedoutputmethod(s)forthereport]
Example:
SavedtoFile/Senttoprint/Sendtoemailaccount/Downloadtoexcel

MainHeading
[Providethemainheadingfieldforthereport]
Example:
Themainreportheadingwillbe:ContractsNearingExpiry

SubHeading
[Provideanyrequiredsubheadingsandbreaksrequiredinthereport]
Example:
Therewillbeasubsectionunderthemaincontractinformationdetailingthedateandtimethereport
wasexecutedandtheusersusername

LAYOUT
Table/Structure
Name

Field
Name

Format DefaultValue
(ie
decimal
places)

ColumnName

TranslationRule

Pleaselistthesequenceofthefields(SAPFieldnames)inwhichtheoutputmustbedisplayed?

DRILLDOWNREQUIREMENTS

TOTALING
[Listanytotalingorothercalculationrequirementsforthereport]
Example:
Numberofcontractsmatchinguserselectioncriteriatobedisplayedatthebottomofthereport
Anypagebreakrequirements?

SORTING
[Listanysortingrequirementsforthereport]
Example:
Userswillbeabletosortoncontracttypeandvendor.Defaultsortsequencewillbebycontracttype.
Anypagebreakrequirements?

PAGEBREAK
[Providedetailsofanypagebreakingrequirementsthatshouldbeusedinadditiontofieldbreaks]
Example:
Pagebreakswillbeusedwherenecessarytopreventoverflowofretrieveddata

ERRORHANDLING
[Includepotentialerrors,notificationprocedures,andcontingencyprocedures.]
Typicalerrorsinclude:Nodatafoundforgivenselectioncriteria.

10

Interfaces
<Identifyallinterfacesrequiredtoprovideinputstooroutputsfromthispartoftheprocess.Provideafunctional
descriptionoftheinterfacesincludingthesourceandtypeofdata.>
INTERFACE
WRIC
EFID
XXxx
I001

Description

Interface
Method

Applications

DataElements

Frequency/
Volumes

Owner

INTERFACEPROCESSFLOWDIAGRAM,INCL.TRANSFERMETHOD/NETWORKINTEGRATION
[Pleaseinsertaninterfaceflowdiagramshowingsourceandtargetsystemswithdirections]
Thiswillincludethescreenflowdiagram,specifytheproposedloadmethod(e.g.IDOC,batch
transactionprocessing),andtheproposedtransferprogramnameandtheinbound/outboundfileformat
(e.g..txt,.xls)]

FILESPECIFICS
[Filenames,deliverymethod,filetype(ascii,commadelimited,etc)

MAPPINGSAPFIELDSTOSOURCE/TARGET

11

[PleaseprovidedetailsoftheexpectedmappingbetweentheSource/TargetsystemandSAPfields.
ThiscaneitherbedonewithinatableinthisdocumentorasanattachedMappingDocument.
SpecificationsforthefollowingelementsshouldbepresentontheMappingdocument(where
applicable):
x
x
x
x
x
x
x
x
x
x
x
x
x
x

SAPTransaction
SAPScreennumber
SAPTablename
SAPFieldname(functional)
SAPFieldname(technical)
SAPfieldlength
SAPfieldtype
Mandatory/Optionalflag
Source/TargetFieldID
Source/TargetFieldName(functional/technical)
Source/TargetFieldlength
Source/TargetFieldtype
MappingDetails
ImplementationComments

Mapping.xls

RECONCILIATIONPROCEDURES&AUDITREQUIREMENTS

12

Reporting
[Pleasedescribeanyreportingthatisexpectedtobeprovidedinsupportofthisinterface]

Approach
[Detailthemethodofdatareconciliatione.g.reportsproducedinSAP]

Metrics
[Providedetailsonthemetricsusedtofacilitatereconciliatione.g.RecordCount]

ErrorHandling
[Includepotentialerrors,notificationprocedures,andcontingencyprocedures.]

13

DataConversion/HistoricalData
<Noteallmasterandtransactionaldataconversionrequirements.Pleasenotespecificfieldsthatareuniquetothis
designandthebusinessrequirementthatdrivesthatdesign.Notewhethermanualandautomateddataconversion
requirements.ProvidedetailsofalldatarequiredfromLegacySystems(ConsiderSystemname,levelofdetail,time
dimension).Identifyrequirementsforhistoricaldataconversionmandatoryfortheprocess.Thisisnotmeanttobean
exhaustivefunctionalspecbutaplacetolistconversionsrelatedtothisprocess.>
CONVERSIONS
WWRICE
FID

Conversion Source
Object

Conversion
Activities
(e.g.
cleansing)

Conversion
#ofObjects
Method(manual tobe
/automated)
converted

Owner

XXxx
C001
1MAPPINGSAPFIELDSTOSOURCE/TARGET

[PleaseprovidedetailsoftheexpectedmappingbetweentheSource/TargetsystemandSAPfields.
ThiscaneitherbedonewithinatableinthisdocumentorasanattachedMappingDocument.
SpecificationsforthefollowingelementsshouldbepresentontheMappingdocument(where
applicable):
x
x
x
x
x
x
x
x
x
x
x
x
x
x

SAPTransaction
SAPScreennumber
SAPTablename
SAPFieldname(functional)
SAPFieldname(technical)
SAPfieldlength
SAPfieldtype
Mandatory/Optionalflag
Source/TargetFieldID
Source/TargetFieldName(functional/technical)
Source/TargetFieldlength
Source/TargetFieldtype
MappingDetails
ImplementationComments

Mapping.xls

RECONCILIATIONPROCEDURES&AUDITREQUIREMENTS

14

Reporting
[Pleasedescribeanyreportingthatisexpectedtobeprovidedinsupportofthisinterface]

Approach
[Detailthemethodofdatareconciliatione.g.reportsproducedinSAP]

Metrics
[Providedetailsonthemetricsusedtofacilitatereconciliatione.g.RecordCount]

ErrorHandling
[Includepotentialerrors,notificationprocedures,andcontingencyprocedures.]

15

Enhancements
<SpecifytheenhancementbasedontheproposedgapresolutionslistedintheDetailedRequirementsandDesign
documents.Provideasmuchdetailontherequirementsanddesignconsiderationsasyoucan.Ifthereisalarge
enhancementthenconsiderdetailingthatinaseparatedesignorfunctionalspec.document.>
ENHANCEMENTS
WRIC
EFID
XXxx
E001

Description

DataObject
(SalesOrder)

Functional
Gap

AlternativeSAP
Standard

Reason

Owner

FUNCTIONALDESIGN/FLOW,VALIDATIONANDVARIANTS
Flow
[Pleaseprovidetheflowofobjecttobeenhanced.ForexampleintheprogramXYZgotoscreen/Sub
screen101theremodify/addafield]

Design
Howshouldthedatabeprocessedintheprogramfunctionallogic?

16

Output(e.g.forms)
<Identifyoutputsandforms>
OUTPUT
WRIC
Description
EFID

DataObject
(Sales
Order)

OutputType
(Form,EDI,etc.)

Frequency

Volumes

Owner

XXxx
O001
PROCESSFLOWDIAGRAM
[Pleaseinsertaflowdiagramdescribingtheformoutputproceduree.g.PurchaseOrderinputusing
transactionME21NsavePurchaseOrderautomaticallygeneratesPurchaseOrderFormprintout]

FORMLAYOUT
[Pleaseprovideasamplelayoutforfirst,subsequentandlastpages,detailingactualpositionsof
outputfields,fonts,fontsizes]
Pleaseindicateifthereispreprintedstockandwhichportionsareonthepreprintedstock
Example:

FormTitle

Date:xxxxx

User:xxxxx

ID
xxxxx
xxxxx
xxxxx
xxxxx

17

Value
3

xxxxx
xxxxx
xxxxx
xxxxx

Description
4

xxxxxxxxxx
xxxxxxxxxx
xxxxxxxxxx
xxxxxxxxxx

PRINTERREQUIREMENTS
DuplexPrinting,labelprinting,labeldimensions,standard,etc.

LEGALREQUIREMENTS
Determineifthereisanytextthatisrequiredlegallyontheform,includingfontsize,texttobeprinted
onthebackofdocuments,

EXISTINGSAMPLEFORMS
[Ifanexistingprogramisavailabletobeenhanced,providedetailsinthissection]
x

ProgramName

Menu/Transaction

LegacyFormname

LegacyProgramTitle

LegacyFormNumber

RelatedTransactions

18

Workflow
<Identifyworkflowrequirementsforthisprocess.Providedetailedrequirementsfortheworkflow.e.g.,purchaseorder
approvalprocessandauthoritylevelsetc.>
WORKFLOW
WRIC
Description
EFID
XXxx
W001

Business/DataObject(Sales EngagedParties
Order)

PROCESSFLOWDIAGRAM
[Pleaseinsertaflowdiagramoftheworkflow]

TRIGGEREVENTS
TransactionsandBatchProgramsthattriggertheworkflow

StartConditions

RULESANDDETERMINATION
StandardRules
LatestEnd,LatestStart
RequestedEnd,Requestedstart

19

Owner

Test Conditions
BUSINESSTESTCONDITIONS(TOBEFURNISHEDBYTHEFUNCTIONALCONSULTANT)

[Pleaseindicatethebusinessleveltestconditionsthatshouldbeusedtoverifysuccessfuloperations
oftheReport]
[Documentalltechnicalscenariosassociatedwiththisdevelopment.Exampleswouldinclude1)
testinganerrorfreerun2)testingtheexceptionprocesses3)testingtheerrorhandling.]
[Documentallcontrolscenariosassociatedwiththisdevelopment.Exampleswouldinclude1)
Roundingofdollarsandcents2)Audittrailprocessing3)Reconciliationreporting]
Scenario#

InputSelectionCriteria

20

ExpectedResult

Document History
AUTHORS&PARTICIPANTS
Role

Name

BusinessSystemAnalyst
ProjectProcessOwner
BusinessUnitProcessOwner
Consultant
WorkshopParticipant

REVISIONHISTORY
Date

DocumentVersion

<<Date>>

1.0

DocumentRevision
Description
Draftforcustomer
review

REVIEWEDANDAPPROVEDBY
Name
Title
<<NAME>>

BusinessSystemAnalyst

<<NAME>>

ProjectProcessOwner

<<NAME>>
<<NAME>>

BusinessUnitProcess
Owner
CorporateProcessOwner

<<NAME>>

InternalAudit

21

Date

Author
<<Name>>

Approved