EN_C429 Functional Design Specification v1 0

8/11/2019 EN_C429 Functional Design Specification v1 0

http://slidepdf.com/reader/full/enc429-functional-design-specification-v1-0 1/18



Table of Contents

1 OVERVE! SECTO"#########################################################################################################################$

1.1 Document Change History................................................................................................................................................. ....3

1.2 Document Sign Off..................................................................................................................................................................3

1.3 Open Items...............................................................................................................................................................................5

1.4 Relate RIC!"# O$%ects......................................................................................................................................................5

1.5 Contact &ist................................................................................................................................................................... ..........5

% F&"CTO"'( RE)&RE*E"TS########################################################################################################6

2.1 Description...............................................................................................................................................................................'

2.2 ()o *e+ Re,uirements........................................................................................................................................................... .-

2.3 *usiness *enefits.....................................................................................................................................................................

2.4 Scope / Selection Criteria.......................................................................................................................................................

2.5 0ssumptions.............................................................................................................................................................................

2.' Riss / itigations.............................................................................................................................................................. ....

2.- Security / SO.........................................................................................................................................................................

2. Depenencies / Concerns / Other Re,uirements......................................................................................................... ........

2. Integration oints....................................................................................................................................................................

2.16 0itional 7otes......................................................................................................................................................................

$ +&S"ESS R&(ES############################################################################################################################ 1,

3.1 Data "lo8 Diagram...............................................................................................................................................................16

3.2 *usiness Rules for !nhancement.........................................................................................................................................12

3.3 &ist of Stanar )a$les 9se for !:tension............................................................................................................. ......... .12

3.4 &ist of Custom S0 Data O$%ects 9se......................................................................................................................... .....12

- &"T TEST .ET'(S########################################################################################################################1-

/ SEC&RT0 CO"TRO( RE)&RE*E"TS######################################################################################1/

5.1 Security Consierations........................................................................................................................................................15

5.2 Control Consierations.........................................................................................................................................................15

246670381.doc 2 of 18



Reviewed By:

7e 8Revie$ed B: signat"re indicates te individ"al;s $o revie$ed tis doc"ment =or content andclarit! and to te 'est o= teir no$ledge! tis doc"ment satis=actoril acieves te 3"r3ose and sco3ede=ined erein%

"ame TitleRole <*esignation! *e3artment>

Revie$ed B

Signat"re *ate

Revie$ed B

Signat"re *ate

Revie$ed B

Signat"re *ate

Approved By:

7e 8,33roved B: signat"re indicates te individ"al;s $o a33roved tis doc"ment =or content andclarit! and to te 'est o= teir no$ledge! tis doc"ment com3lies $it cor3orate 3olicies and3roced"res%

"ame TitleRole <*esignation! *e3artment>

,33roved B

Signat"re *ate

,33roved B

Signat"re *ate

,33roved B

Signat"re *ate

,33roved B

Signat"re *ate

Impact Approval

7e 8,33roved B: signat"re indicates te individ"al;s $o a33roved tis doc"ment =or content and clarit! and tote 'est o= teir no$ledge! tis doc"ment ="l=ills te design s3eci=ications o= te e/isting and ="t"re sstems%

(m3act on B(! ?es ! No ! B( a33roved ' __6irt"al 7eam_____! *ate __10)0)2010__

(m3act on ,rcitect"re! ?es ! No ! ,rcitect"re a33roved ' __6irt"al 7eam_____! *ate __10)0)2010__

(m3act on -ortal! ?es ! No ! -ortal a33roved ' __6irt"al 7eam_____! *ate __10)0)2010__

(m3act on #egac! ?es ! No ! #egac a33roved ' __6irt"al 7eam_____! *ate __10)0)2010__

Quality Control

7e 8Revie$ B: signat"re indicates te individ"al;s $o revie$ed tis doc"ment =or @"alit sam3ling! and to te'est o= teir no$ledge! tis doc"ment meets te @"alit s3eci=ication o= com3leteness! acc"rac! validit andtimeliness%

*oc"mentation revie$ed ' 7ec A,! ?es ! No ! A, revie$ed '_____________________! *ate___________

246670381.doc 4 of 18



1#$ Open tems

'ssi3ned To<Name>

.ateOpened

.ue .ate Status .escription

1#- Related RCEF! Objects

.oc . "ame'ssociation 7.escribe ho2these objects are related8 .ocument name 7if 9no2n8

FR_C401

FR_C402

FR_C404

FR_C40

FR_C40

1#/ Contact (ist"ame TeamOr3ani:ation Email 'ddress

?vonne #in SCE ?vonne5linDsce5com

N5S$aminatan SCE S$ami5s$aminatanDsce5com

Mir ,med SCE Mir5,medDsce5com

#ionel *eso"a SCE #ionel5deso"aDsce5com

Micael Hsie SCE [email protected]

Ricard +seg"ra SCE [email protected]

246670381.doc 5 of 18

mailto:[email protected]















at te transaction data level5

S"'ect #ine and te/t 'od% 7is $ill 'e determined ' te 3rogram (*! a33roac 73e and action de=initionrelated to service transaction as $ell as te t3e o= letter selected ' CRM "ser5 S"'ect line and 'od te/ttem3lates =or eac 3rogram (*)t3e o= letter com'o $ill 'e created and in=ormation $ill 'e stored in c"stom ta'le5Note% (n ="t"re! ma re@"ire m"ltisite variation5

,ttaced -*F doc"ment% 7is $ill 'e determined ' =orm selected ' CRM "ser "3on triggering emailgeneration5 (= '"ndled! ten m"lti3le =orms ma 'e re@"ired to generate5 7e logic to '"ndle or to attac m"lti3le=orms $ill 'e determined ' C"stom con=ig"ration ta'le5

7ransaction Histor% 7ransaction Histor $ill 'e "3dated a=ter email is sent o"t5 7is transaction istor $illdis3la email content and attacments5

246670381.doc 7 of 18



%#% =To +e> Re;uirements

Describe the SAP Transaction or BRF Object in detail. Please describe the “To Be” vision inbusiness terms main! sure to hi!hli!ht e" di##erences #rom the “As $s” a%%lication. For BRFonl"& %rovide the eli!ibilit" rules that 'ill be enabled b" this enhancement.

7e =ollo$ing re@"irements $ill 'e met ' tis enancement%

Requirement #

Requirement Description BPD

1501Sstem $ill allo$ "ser to generate a =orm into email =ormat on demand5

1502 ,'ilit to 3re3o3"late te =orm $it in=ormation tat is availa'le in te sstem

1504 ,'ilit to generate m"lti3le =orms at one time5

150 ,'ilit to restrict te creation o= te =orm i= criteria as not 'een met5

150 ,'ilit to create 3acets ;i5e B"ndle 2 or more =orms togeter

2501Restriction o= Emails to certain 3rograms and a33roac t3e to 'e 'ased onc"stom ta'le

2502 ,ttacment details s"c as attacment names! ,ttacment =orm name to 'econ=ig"red in te C"stom ta'le

250 ,'ilit to '"ndle t$o or more =orms $ill 'e con=ig"red in c"stom ta'le

2504(ncase o= m"lti3le 7+G addresses or CCG $ill 'e con=ig"red in te c"stomta'le

501 ,'ilit to 3revie$ e/actl te attacment)=orm reci3ients $ill 'e receiving

502 ,'ilit to 3revie$ e/actl te email reci3ients $ill 'e receiving

50 .enerated email $ill a"to 3o3"late a33ro3riate 3artiesG emails involved ona33lication de3ending on 3rogram and letter5

50Sstem $ill allo$ "ser to edit email reci3ients $en generating =orm to email5

50 ,'ilit to send as an attacment $it a generic email 'od tem3late

510 ,'ilit to $arn te "ser $en tere are some reci3ients tat do not ave anemail address

511 ,'ilit to noti= te "ser $en tere are no reci3ients $it an email address

4501 BS- 3age $ill 'e created to ena'le "sers to reIsend emails

246670381.doc 8 of 18



501 Batc 3rogram to 'e created to send email in nigtl o's

501

Bod o= email is con=ig"red eiter as standard te/t or smart =orm5 Email="nctionalit so"ld a"tomaticall dis3la eiter 3lain te/t or H7M# =ormatde3ending on $ic te/t is con=ig"red in c"stom ta'le5

Note% 7e re@"irements listed a'ove are te onl re@"irements in sco3e as 3art o= te 8Base: 3acage o=re@"irements5 +"t o= sco3e are te re@"irements listed "nder 8Base Enanced:5 -lease re=erence doc"mentCRM CR Electronic comm"nication v151 in section 25115

7is enancement is to generate an email =rom CRM service transaction $it 3o3"lated reci3ients! s"'ect line!te/t 'od! and attaced -*F doc"ments5

, Send Email action '"tton $ill 'e created at te service transaction to generate email5

Send Email action '"tton $ill availa'le at transaction men" tool 'ar5Note% 7e Follo$ U3 transaction men" is =or ill"stration 3"r3roses and sall not 'e 3o3 "3 $en Send Email'"tton is slected5

Note% ,t tis time! creation o= te =orm can 'e generated at an 3roect stat"s For ="t"re re@"irements! tesstem sall allo$ te a'ilit to restrict creation o= te =orm i= start condition as not 'een met5

246670381.doc 9 of 18



+nce te Send Email '"tton is selected! a slection men" $ill dis3la and "ser $ill vie$ Email selection o3tions5

,ction to '"tton to 'e con=ig"red ;Note% ,ction $ill 'e sim"lar to te selection screen dis3laed $en "ser selects-rint -revie$ as so$n in screen sot

+nl te emails tat eligi'le to 'e sent $ill 'e so$n in te selection men"5 (t $ill 'e ass"med tat eligi'ilit $ill'e determined "sing te sced"ling condition o= an action and onl i= te action as 'een sced"led so"ld ita33ear in te 'o/5 +nl email selection o3tions so"ld a33ear in 'o/ not 3rint 3revie$ selections5

&en email is created te =ollo$ing =ields so"ld 'e 3o3"lated5

Email

From%SCE gro"3 email ;*e3endent on Contract 73e!-rogram (* and #etter t3e5 Con=ig"red in c"stom7a'le

7o%Sold to -art contactGs email address entered ontransaction or contact at a"toried agent5 Based on3artner ="nction con=ig"red in te c"stom ta'le5

CC% ,dditional 3arties involved email addresses;*e3endent on -rogram (* and #etter 73e

,ttacments%Form)B"ndle identi=ied =or te selection t3e 'ased onc"stom ta'le

7e/t 'od

*e3endent on letter selection 'ased on c"stom ta'le5Bod $ill 'e eiter a =orm or a standard te/t5 (n caseo= =orm convert =orm to H7M# =ormat and in case o=standard te/t 'od so"ld 'e dis3laed as 3lain te/t

For S"'ect line 7e/t in c"stom ta'le needs to 'e concatenated $it%

246670381.doc 10 of 18



Variable Description Technical VariableName

Program ID* &PGM_ID&Contract description &CNTRACT_D!C&

Pro"ect ID &PR#$_ID&CRM Contract ID &C#NTRACT_ID&

C%stomer Name &!#D_T#_NAM&C%stom Acco%nt Name &CA_NAM&

Selection +3tion val"es 3lease see ta'les in =ollo$ing s3read seet5 7is $ill c"stom con=ig"ration ta'le5

'or(sheet inN_C)*+,-%nctional

"ote< For test purposes# P' 'c9no2led3ement letter 2ill not be sent out as attachment in a real businessscenario#

"ote< ?To<?@ ?CC<? and ?Re;uired CC<? fields should allo2 n number of values to be maintained 2ithinone entr5

+nce te email is generated! te "ser so"ld 'e a'le to revie$ te attaced doc"ment tat $as generated5 (= teemail is not sent! te sstem so"ld not re=erence te email to te Service Contract)+rder5

+nce te email is re=erenced on te Service Contract)+rder! "sers so"ld ave access to te email to revie$ notonl te attacments o= te email! '"t also te email 'od as $ell as te reci3ients tat te email $as sent to5

Note3 mail addresses to be %sed 4or the recipients in the email need to be the ones on

the transaction5 not the ones on the b%siness partner record, It might be that the6 are thesame5 ho7e/er the6 co%ld be di8erent,

246670381.doc 11 of 18



• ,"toriation o'ect K_SEN*_EM#G to 'e created to restrict sending o= emails

SO<Re=er to Section 52 =or controls considerations5

%#D .ependencies Concerns Other Re;uirements

Are there any $A! dependencies before this enhancement can be completed#

15 7e Con=ig"ration o= ,ctions -ro=ile to manage te email creation 3rocess525 Start condition to 'e 3rovided ' '"siness 3er =orm55 Correctness o= =orm de3endent on meas"re name cange enancement =or =orms tat incl"de

meas"res545 Email addresses are correct55 C"stom ta'le to 'e con=ig"red5 ,"toriation o'ects to 'e created

Related +'ects are mentioned in Section 154

%#1, nte3ration Points

Are there any other processes+obects impacted by this enhancement# "hich module#

7is enancement is triggered man"all ' "ser5 ,lso in some cases $ill 'e Man"al57ere is a nigtl 'atc o' =or 'atc emails5

%#11 'dditional "otes

'f you have additional information+notes about this enhancement please document it here.

7is enancement $as $ritten $it te =ollo$ing re=erence doc"ments%

.oc . .ocument "ame VersionRe@"irements doc"ments CRM CR Electronic comm"nication 1515/ls/ 151-rocess Flo$ ,"tomatic email o= doc"ment I Conce3t"al v51505vsd 150

CRM CR 99:lectronic comm%nica

A%tomatic email o4doc%ment ; Concept%

246670381.doc 13 of 18



$#% +usiness Rules for Enhancement

ocument the detail processing area requirements as well as business rules related to this enhancement.

N/

$#$ (ist of Standard Tables &sed for E4tension

A list of all standard $A! tables used for this extension should be given here.

O Table "ame Table .escription

N, N, N,

$#- (ist of Custom S'P .ata Objects &sed

!rovide data definitions for custom $A! ata bects to be referenced by the program 1e.g. custom /iewcreated to lin% to $A! database tables, custom tables, etc.2. 'f this is a custom table, be sure to indicate

the functional area and individual person who will own this table and the table contained in the table. 'nthe description include how the table will be populated along with how the table contents will bemaintained.

246670381.doc 15 of 18



- &nit Test .etails (ist the test scenarios and data to be used to validate the development wor%.

Note:Test Conditions The 4ollo7ing table de.nes the test conditions,

; )est Conition !:pecte Results )este $y/Signoff Date

1 7rigger email to 'e sent =rom te service contract)order #ist o= emails $ere te start condition is met)notmaintained are listed

2 Select email to 'e sent $ere all 3artner ="nctions aremaintained $it email addresses

Email reci3ients! sender! email 'od! s"'ect line andattacment are 3re3o3"lated

Select email to 'e sent $ere some 3artner ="nctions are notmaintained $it email addresses ,33lica'le $arning messages are triggered

4 Select email to 'e sent $ere all o= te 3artner ="nctions arenot maintained $it email addresses

,33lica'le error message is triggered

Send email and navigate 'ac to te Service Contract)+rderto revie$ te re=erenced email

7e email is re=erenced =rom te Service Contract)+rder eader and te email 'od can 'e revie$ed incl"dingemail reci3ients te email $as sent to as $ell as tecontents o= te attacments

Select attacments tat ave 'een 3re3o3"lated onto teemail 'e=ore sending

7e attacment can 'e revie$ed and te contentanaled

246670381.doc 16 of 18



/ Securit5 Control Re;uirements

/#1 Securit5 Considerations

oes this enhancement require a custom 3ransaction Code to enable end user execution in !roduction# 'f so, please wor% with the $ecurity 3eam to determine an appropriate 3ransaction Code

and enter it below

All CRM %sers 7ill re<%ire access to /ie7 all historical emails located in Transaction =istor6assignment bloc( 4rom ser/ice contract transaction screen,

A restricted list o4 roles 7ill ha/e a%thori>ation to generate and send emails o%t o4 CRM,

Ne7 A%thori>ation ob"ect ?@_!ND_M 7ill be created, This ne7 A%thori>ation ob"ect along 7ithe2isting a%th ob"ect CRM_#RD_PR 7ill be %sed to restrict %sers a%thorit6 to send email,

Roles 7ill be modi.ed to incl%de tcode to con.g%re c%stom table,

!lease provide a general description of the enhancement4s data restriction requirements.

<*ata Restriction>

/#% Control Considerations

"inancial/SO Impact

oes the enhancement have any impact to financial reporting# 'f yes, is the amount significant 1i.e. greater than 567 million annually2# !lease provide an estimate.

No Financial)S+L im3acts $ere identi=ied =or tis enancement5

Regulatory Impact

oes the enhancement have any impact to regulatory compliance 1i.e. 0)*C, C!8C, etc2# 'f yes, please provide a reference to the rule and describe the impact.

Re=er to 8Financial)S+L (m3act: a'ove5 Operational Impact

's the enhancement relied upon for a mission critical process or providing services to customers# 'f yes, please identify the mission critical process and describe how this enhancement is used in thecontext of this process.

No +3erational im3acts $ere identi=ied =or tis enancement5

246670381.doc 17 of 18



6 'uditin3 and Error andlin3 Re;uirements

6#1 Postin3 Errors Re;uirements

(hat inds o# errors are antici%ated) (hat needs to be done 'hen there are errors) $sthere a rule that can be used to re*run transactions 'ith error) +o' should errors in data

trans#ormation,ma%%in! be handled) Does the %rocess team need to revie' ever" error %rior to re*run) Do records 'ith %ostin! errors have to be %rocessed manuall")

7e =ollo$ing is a list o= 3otential errors tat ma 'e enco"ntered $en creating +"tgoing Email transaction5

N_C)*+_errormatri2,2ls2

6#% Error "otification Re;uirements

(hat error noti#ication is re-uired #or each t"%e o# error identi#ied) (hat deliver" mechanismis used #or error re%ortin!,noti#ication) (ho needs to be noti#ied) (hen)

N),

6#$ +.C Session Re;uirements

Should transactions in error be saved in a BD session in SAP) an the sessions bedeleted a#ter success#ul %rocessin! or should the" be retained #or audit,reconciliation %ur%oses)

No B*C session re@"irements are identi=ied at tis time5

6#- Reconciliation Re;uirements

+o' 'ould "ou reconcile data a#ter runnin! the inter#ace) Document all reconciliationre-uirements here.

N),

6#/ Email Reports Re;uirements

Do re%orts need to be emailed , #a/ed to users) (h") Document the re%ort details alon!'ith the list o# users 'ho 'ould need them.

No re3orts are re@"ired at tis time5

6#6 ReRun Re;uirements

Document ho' the inter#ace should be re*tri!!ered in the event o# #ailure or abend in themiddle o# %rocessin!& i.e. Manuall" re*run inter#ace 'ith same data or re*run 'ith onl"un%rocessed data)

BS- 3age $ill 'e created to ena'le "sers to reIsend email ="nctionalit5

246670381 d 18 f 18

EN_C429 Functional Design Specification v1 0

Documents

Transcript of EN_C429 Functional Design Specification v1 0