FDD Customer Account Statement

8/11/2019 FDD Customer Account Statement

1/14

1.1.1.1.1 GE Industrial Solutions

GEIS Functional

Design SpecifcationDocumentFDD--

Srinivas saride, Hns

[2013/06/18]

This document is used to detail the business requirements and sstemdesign !or G"#s identifed in the S"# I$%C &est #ractices' " FunctionalSpecifcation Document (ill be created !or each gap identifed'

GEIS Functional Specification Document Page 0of


2/14

Purpose and Guidelines

This document is used to capture the detailed requirements and!unctioanl design !or gaps identifed during the S"# blueprintsessions' For each )ICEF gap a separate Functional Design

Specifcation should be created' This means !or each &lueprintDesign Document there (ill be se*eral Functional DesignSpecifcation Documents'

This document is o(ned b the Solutions "rchitect team' &usiness#rocess +(ners (ill support and (or, closel (ith the architects increating this document'

Business Process Owners

&usiness #rocess leads (ill support the Solution "rchitects to fll insection to illustrate the fnal To-&e process and detail therequirements !or the gaps being addressed in the !unctionalspecifcation'

In flling out this section the team should re!er to and cop content!rom the &lueprint Design Document'

&usiness #rocess +(ner should gi*e detailed requirements !or thegap so that solution architects can complete solution design'

Soluion !rc"iecs

Solution "rchitects should !ollo( the guidelines belo( to completesection . and ensure all S"# !unctional design details arecompleted' In designing and defning the #$%&'solution/ thesolution architects should (or, closel (ith the Integration andTechnical teams to complete analsis and !easibilit o! solutions'

+nce the !unctional design document has been completed/ it (ill gothrough a re*ie( and appro*al process' +nce appro*ed/ theIntegration team (ill create a technical design document'

This document (ill 0+T be flled in !or gaps (hich can be resol*edthrough S"# confguration' These gaps (ill be described in theConfguration Specifcation Document'

For each )ICEF categor the rele*ant sub sections should beincluded as per the guidelines' This (ill ensure the technical teamcan build a robust solution'



3/14

Guidelines (or #$%&' )*pes

#epors1' )eport design/ 2aout and Sorting )equirements.' Selection screen/ de!ault entries/ user inputs/3' Sstem chec,s/4' )estrictions/5' 6ariant Selections7' $ode !or running 8batch/ batch 9ob requirements and !requenc/ on-line

including transactions !or running on-line:

$ner(aces +' Diagram sho(ing ;o( o! data bet(een sstems

.' Tpe o! Inter!ace Inbound/ +utbound/ &i-Directional3' $ode and !requenc o! running4' Input and +utput fle !ormats and laouts including feld names/ length/

tpe and usage5' Input 6alidation7' =pdates 8Field =pdates/ transaction creation/ transactional or master data

updates must be auditable/ i'e' no direct updates to S"# tables'' Error ?andling/ reporting and alerts@' Changes required to satellite sstems

%onversions +

' Input fle !ormats and laouts including feld names/ length/ tpe and usage.' Tpe o! Inter!ace Inbound/ +utbound/ &i-Directional

3' Con*ersionA=pdate )equired 8"ll master data and transactional datacreation or updates must be auditable' 0o direct updates to S"# Tables:

4' $ode and !requenc o! running5' Error ?andling/ reporting and alerts

&ension +' "dditional ;o( Diagram to sho( detailed logic/ inputs/ conditions and

outputs.' 6alidation/ Substitution rules3' For ne( felds include !ormat/ tpe/ length/ usage/ de!ault *alues'4' For table or screen eBtensions include dnpro/ table name5' For ne( screensAtransactionsAtables include laout/ feld !ormats/ length/

usage/ dnpros7' $ode and !requenc o! running' Error ?andling/ reporting and alerts

'or-s +

' 2aout/ sorting requirements.' Fields/ tables3' 2anguages4' +utput Tpes5' )unning mode/ !requenc7' "rchi*ing implications



4/14

G&$S Ownin. Business 'uncion+ ames 2in

'uncional !u"or Srini*as saride/ ?nsSoluion !rc"iec/%onsulan 6onteddu/ )amalinga

!pproved *

Posiion a-e Si.naure ae

)egional #rocesso(ner

ames 2in

Global #rocess o(ner Iorgu/ Salma

ersion ana.e-en

ersion

%"an.e$

ae %"an.ed * #e-ar4

' [email protected]

Srini*as saride/ ?ns Initial 6ersion

#elaed Business Blueprin ocu-ens

BP#e(erence

BP a-e H*per5in4



5/14

%onen1 eailed Business #e7uire-ens and Soluion esi.n..........42. Solution Design Reports, Interface, Conversion, Extension, Fors................4

3. !ec"nical #$Functional Ipact Consi%erations....................................................5

&. 're$ Re(uisites..........................................................................................................6

). Constraints................................................................................................................7

*. )ec"nical Per(or-ance %onsideraions..............................................8+. ser / O9ec !u"ori:aion consideraions....................................9. %onsideraions (or esi.n Gaps / ;or4 around..........................10-. )es Scenarios.................................................................................................11

GEIS Functional Specification Document Page &of


6/14

1 eailed Business #e7uire-ens and Soluion esi.n

In this section include the detailed business requirements including

detailed process maps/ report laout/ screen laout

Customer account statement is a tpe o! correspondence that compan(ill send to customer !or the open balance and due date/ a!ter in*oice andclearing posted'

To trigger customer account statement printing/ compan code/ customer8paer: and ,e date are to be selected on F'.-#eriodic accountstatement' "s a result/ the selected data is mapped to the specifc S"#!orm and print out'

" ne( Customer account statement is to be de*eloped in S"# to meet the

requirements o! rest o! "sia 8"ustralia/ Singapore and Indonesia: bmodi!ing the eBisting )eport being used !or China 82ogic and designchanges are pro*ided in the neBt section:

2. Solution Design Reports, Interface, Conversion, Extension, FormsIn this section include the detailed sstem design and sub-sectionsdescribed abo*e !or the )ICEF categor

' 2aout/ sorting requirements o! the eBisting report'The !orm laout (ill be consisted b header/ open item list and due date

buc,et'The compan code/ paer/ and ,e date (hich are selected b user aresho( up on the header' The customer open item and due date analsis (illbe sho( up on the details'

The 2aout sample is attached belo(1

(Next page)

GEIS Functional Specification Document Page )of


7/14

(Next page)

Follo(ing changes are to be done to the abo*e laout to meet the requirements o!rest o! "sia

- "dd !ollo(ing felds to the eBisting laout 18a: Document currenc code8b: "mount in document currenc 2ocal currenc code8c: "mount in 2ocal currenc

- "ging buc,ets displaed at the bottom o! st page should be in compancodes 2+C"2 C=))E0C

- &ill o! eBchange details are to be included in the ne( report 8&oE (as 0+Tdisplaed in China/ here (e should include it:' Currentl onl " and Fspecial G2 items are being displaed in china report in addition to thenormal items' For this ne( report the "/ F and H tpe o! special G2 tpesare to be displaed/ in addition to the normal records and aging buc,etsare to be displaed !or each o! this tpes 80ormal transactions/ "/ F and H:

EnsureA6alidate the !ollo(ing requirements are a*ailable in the ne( report- 2anguages1 should be the communication language as described in

customer master'- I! currenc is not C0/ the descriptions in C0 should not be displaed

8&illing document number/ Doc Tpe etc'/ in Chinese:- Displa on the header/ currenc o! the sales area !rom customer master- "ll special indicators should be displaed on separate pages1 do(n

pament requests/ do(n paments recei*ed &ill o! eBchange details''

Details o! 4 ne( table felds to be added are encircled in the belo( screen shot

GEIS Functional Specification Document Page *of


8/14

.' Fields/ tablesThe felds on the !orm are eBplained here1 "ging buc,ets are modifed !rom thecurrent China report and the updated feld list is gi*en belo(1

The ne( line le*el displa o! felds positions is pro*ided in the attached eBcel fle

2ine 2e*el Fieldpositioning !ormat !or

8The structure FAGL_S_RFDEPL00_LIST1 is proposed.:

For Fiel% Fiel% DescriptionGE legal entity name ompany o!e "ame

GE legal entity a!!#e$$

ompany o!e %!!#e$$

&$t#eet'#oom'count#y'po$tal co!e etc.(

S%P Paye# num)e# Paye# u$tome# no

S%P paye# name Paye# u$tome# name

S%P paye# a!!#e$$ a$pe# cu$tome# ma$te#

Paye# u$tome# a!!#e$$&$t#eet'#oom'count#y'po$tal co!e etc.(

*epo#t u##ency u##ency on u$tome# Sale$ %#ea

Date &of t+e $tatement( Date of $tatement

Doc Date In,oice !ocument !ate

-illing !oc num)e# -illing !ocument no

Doc type -illing !ocument type

GEIS Functional Specification Document Page +of


9/14

Due !ate In,oice net !ue !ate

#iginal in,oice amount In,oice po$te! amount

pen in,oice amount In,oice open amount

Document u##ency u##ency u$e! fo# po$ting !ocument

%mount in Document

cu##encyDocument cu##ency amount

/ocal u##ency ompany co!e cu##ency

%mount in /ocal

cu##ency%mount in company co!e cu##ency

Sale$ #!e# num)e# Sale$ !ocument num)e#

P#oect "ame P#oect "ame

-S element -S element no

2otal #iginal amount Sum up of t+e 3#iginal in,oice amount

2otal open amount Sum up of t+e 3pen in,oice amount

"ot !ue 02otal open amount +e#e

Date of $tatementDue !ate0

"ot !ue 02otal open amount +e#e0Date of $tatementDue !ate0

Pa$$ !ue 10 2otal open amount +e#e1Date of $tatementDue !ate0

Pa$$ !ue 1602otal open amount +e#e

1Date of $tatementDue !ate60



Pa$$ !ue 911:02otal open amount +e#e91Date of $tatementDue !ate1:0

Pa$$ !ue 1:11802otal open amount +e#e

1:1Date of $tatementDue !ate180



Pa$$ !ue ;652otal open amount +e#e

65Date of $tatementDue !ate

2otal I"< 2otal open amount

3' Ensure A6alidate the EBisting logic in the ne( reporta' The open line items on the !orm need to be grouped b billing

document no'b' Special G2 indicator lines are handled on !ollo(ing rules1

" -Do(n pament recei*ed1 2isting on a separated table on a specifcpage/ (ithout impacting account statement balance'F- Do(n pament request1 2isting on a separated table on a specifcpage/ (ithout impacting account statement balance'H-&ill o! eBchange1 2isting on a separated table on a specifc page/(ithout impacting account statement balance

c' S"# paer name A S"# paer address are displaed based on

communication language'd' GE legal entit nameAaddress is to be in English'

4' +utput TpesThis is a stand output and its send to Spool/ and should be a*ailable !ordo(n load in to EBcel on the users des, top

5' )unning mode/ !requenc& request

3. Tecnical !"Functional Impact Consi#erations

GEIS Functional Specification Document Page of


10/14

)e!erence needs to be made to the technical impact !or aninterdependent processes' E'g' " change in order processing couldimpact the trans!er o! requirements to $)# or collection o! statisticaldata !or demand planning' These considerations need to bee*aluated and documented and included as part o! the post cuto*er

testing process

0o J-Functional impact !oresee

GEIS Functional Specification Document Page -of


11/14

$. %re" Re&uisites

K#lease indicate an dependencies that ma impact de*elopment or!unctionalit/ in terms o! requirements !rom internal or eBternalapplications or teams' For eBample/ S"# confguration/ changes toeBternal sstems/ master data setup

"lso/ please speci! an inter!ace or batch 9obs that must be runprior to eBecution and dependent 9obsA operations'L

The !ollo(ing pre-requisites In eBisting report are no applicale!or the

rest o! "sia report $ust to create customer onl in one currenc' For diMerent currenc/ another customer code created'

"s per the requirements in rest o! "sia/ in*oices can be posted in ")A #aer

account inmultiple currencies'

'. Constraints

K#lease indicate an constraints that ma impact the EnhancementDe*elopment/ such as limited access to legac sstem/ timeconstraints or data restrictions etcL

ou cannot create statements !or one time ship-to customers'

In the case o! customer head oNces (ith local branches/ Customer

statement contain the address o! the head oNce and not that o! thebranch 8?ead oNce/ branch !unctionalit is not enabled !or "sia: This is9ust !or in!ormation



12/14

6.Technical #er!ormance Considerations

Describe potential areas !or consideration that ma impact the

per!ormance o! de*elopments associated (ith this specifcation/ or aneBisting !unctionalit/ (hich (ould be impacted as part o! theprocessAde*elopment being proposed' Include in!ormation on Transactional*olumes/ print *olumes/ database updates etc'

Include in this section the CTOs !or per!ormance required b the &usiness'For eBample Criticalit o! Time !or running o! a report/ response time !ortransaction etc'

(. ser / O9ec !u"ori:aion consideraions

2ist impacts to "uthoriPation concepts and rules (ith regard to thespecifcation' This should include ne( or changed authoriPations toob9ects' "n ne( roles (ill need to be signed oM and *alidated bthe business compliance leader to ensure no con;icts o! interest arecreated'



13/14

). %onsideraions (or esi.n Gaps / ;or4 around

Document specifc areas o! !unctionalit !or (hich the Specifcationcan not address the requirement' Gi*e the reasons and thesuggested (or, around A alternati*e solution !or meeting the need'



14/14

*. )es Scenarios

Include test scenarios that should be completed both positi*e and

negati*e tests (ith input data and eBpected results !or unit testing

&usiness #rocess 2eads should (or, (ith the solution architects toprepare this'

)es scenarios+

- customer in SG (ith customer master on sales areas Q SGD currenc/but (ith 3 diMerent DC billing documents on posted in ") 8 &illingdocuments !rom SD/ and not FI postings onl:

- customer in "= (ith customer master on sales area Q "=D currenc/ but(ith . currencies on ") 8"=D/ E=):R

- customer in I0D (ith customer master on sales area Q =SD/ but (ith .currencies =SD and I0D on customer account

- customer in each 2E-s 8SG/ "=/ I0: (ith do(n paments posted on thecustomer account D# (ith Special Ind " in SG and "=/ Indonesia a Do(n#ament )equest 8F: and one &oE (ith indicator H in Singapore

TEST 1)un statements !or SGA "=A I0 customers mentioned abo*e' EBpect results1 allopen items in DC and 2C Q F&250 amounts' "ging buc,ets Q total 2C in F&l50 baging buc,et'Special indicator items and their aging should appear on subsequent pages2anguage o! the statement should be the same language as set-up in customermaster

TEST.1)un statements !or China 8on the same E)# plat!orm and client: logic !or Chinastatements should not be aMected' For eBample items (ith special G2 indicator Hposted in China should 0+T be included in China statements'
