1.1.1.1.

1 GE Industrial Solutions
GEIS Functional
Design Specifcation
Document
FDD-<>-<Customer account
statement>
Srinivas saride, Hns
[2013/06/18]
This document is used to detail the business requirements and sstem
design !or G"#s identifed in the S"# I$%C &est #ractices' " Functional
Specifcation Document (ill be created !or each gap identifed'
GEIS Functional Specification Document Page 0 of
Purpose and Guidelines
This document is used to capture the detailed requirements and
!unctioanl design !or gaps identifed during the S"# blueprint
sessions' For each )ICEF gap a separate Functional Design
Specifcation should be created' This means !or each &lueprint
Design Document there (ill be se*eral Functional Design
Specifcation Documents'
This document is o(ned b the Solutions "rchitect team' &usiness
#rocess +(ners (ill support and (or, closel (ith the architects in
creating this document'
Business Process Owners
&usiness #rocess leads (ill support the Solution "rchitects to fll in
section - to illustrate the fnal To-&e process and detail the
requirements !or the gaps being addressed in the !unctional
specifcation'
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 the
gap so that solution architects can complete solution design'
Soluion !rc"iecs
Solution "rchitects should !ollo( the guidelines belo( to complete
section . and ensure all S"# !unctional design details are
completed' In designing and defning the #$%&' solution/ the
solution architects should (or, closel (ith the Integration and
Technical teams to complete analsis and !easibilit o! solutions'
+nce the !unctional design document has been completed/ it (ill go
through a re*ie( and appro*al process' +nce appro*ed/ the
Integration team (ill create a technical design document'
This document (ill 0+T be flled in !or gaps (hich can be resol*ed
through S"# confguration' These gaps (ill be described in the
Confguration Specifcation Document'
For each )ICEF categor the rele*ant sub sections should be
included as per the guidelines' This (ill ensure the technical team
can build a robust solution'
GEIS Functional Specification Document Page 1 of
Guidelines (or #$%&' )*pes
#epors 1
-' )eport design/ 2aout and Sorting )equirements
.' Selection screen/ de!ault entries/ user inputs/
3' Sstem chec,s/
4' )estrictions/
5' 6ariant Selections
7' $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-Directional
3' $ode and !requenc o! running
4' Input and +utput fle !ormats and laouts including feld names/ length/
tpe and usage
5' Input 6alidation
7' =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 data
creation or updates must be auditable' 0o direct updates to S"# Tables:
4' $ode and !requenc o! running
5' Error ?andling/ reporting and alerts
&,ension +
-' "dditional ;o( Diagram to sho( detailed logic/ inputs/ conditions and
outputs
.' 6alidation/ Substitution rules
3' For ne( felds include !ormat/ tpe/ length/ usage/ de!ault *alues'
4' For table or screen eBtensions include dnpro/ table name
5' For ne( screensAtransactionsAtables include laout/ feld !ormats/ length/
usage/ dnpros
7' $ode and !requenc o! running
>' Error ?andling/ reporting and alerts
'or-s +
-' 2aout/ sorting requirements
.' Fields/ tables
3' 2anguages
4' +utput Tpes
5' )unning mode/ !requenc
7' "rchi*ing implications
GEIS Functional Specification Document Page 2 of
G&$S Ownin. Business 'uncion+ Cames 2in
'uncional !u"or Srini*as saride/ ?ns
Soluion !rc"iec/%onsulan 6onteddu/ )amalinga
!pproved /*
Posiion 0a-e Si.naure 1ae
)egional #rocess
o(ner
Cames 2in
Global #rocess o(ner Iorgu/ Salma
2ersion 3ana.e-en
2ersio
n
%"an.e
$1
1ae %"an.ed /* #e-ar4
-'D [email protected]
-3
Srini*as saride/ ?ns Initial 6ersion
#elaed Business Blueprin 1ocu-ens
BP1
#e(erence
BP1 0a-e H*per5in4
GEIS Functional Specification Document Page 3 of
%onen
16 1eailed Business #e7uire-ens and Soluion 1esi.n..........4
2. 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
+. 8ser / O/9ec !u"ori:aion consideraions....................................9
,. %onsideraions (or 1esi.n Gaps / ;or4 around..........................10
-. )es Scenarios.................................................................................................11
GEIS Functional Specification Document Page & of
16 1eailed Business #e7uire-ens and Soluion 1esi.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 and
clearing posted'
To trigger customer account statement printing/ compan code/ customer
8paer: and ,e date are to be selected on F'.>-#eriodic account
statement' "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: b
modi!ing the eBisting )eport being used !or China 82ogic and design
changes are pro*ided in the neBt section:
2. Solution Design Reports, Interface, Conversion, Extension, Forms
In this section include the detailed sstem design and sub-sections
described 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 are
sho( up on the header' The customer open item and due date analsis (ill
be sho( up on the details'
The 2aout sample is attached belo(1
(Next page)
GEIS Functional Specification Document Page ) of
(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 1
8a: Document currenc code
8b: "mount in document currenc
E 2ocal currenc code
8c: "mount in 2ocal currenc
- "ging buc,ets displaed at the bottom o! -st page should be in compan
codeFs 2+C"2 C=))E0CG
- &ill o! eBchange details are to be included in the ne( report 8&oE (as 0+T
displaed in China/ here (e should include it:' Currentl onl " and F
special G2 items are being displaed in china report in addition to the
normal items' For this ne( report the "/ F and H tpe o! special G2 tpes
are to be displaed/ in addition to the normal records and aging buc,ets
are 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 C0G/ the descriptions in C0G 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
I
.' Fields/ tables
The felds on the !orm are eBplained here1 "ging buc,ets are modifed !rom the
current 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 Field
positioning !ormat !or Customer statement'BlsB
8The structure FAGL_S_RFDEPL00_LIST1 is proposed.:
For Fiel% Fiel% Description
GE 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
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##ency
Document 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#o0ect "ame P#o0ect "ame
1-S element 1-S element no
2otal .#iginal amount Sum up of t+e 3.#iginal in,oice amount4
2otal open amount Sum up of t+e 3.pen in,oice amount4
"ot !ue 5670
2otal open amount 8+e#e
Date of $tatement6Due !ate5670
"ot !ue 670
2otal open amount 8+e#e
67095Date of $tatement6Due !ate50
Pa$$ !ue 1670
2otal open amount 8+e#e
195Date of $tatement6Due !ate9570
Pa$$ !ue 71660
2otal open amount 8+e#e
7195Date of $tatement6Due !ate9560
Pa$$ !ue 61690
2otal open amount 8+e#e
6195Date of $tatement6Due !ate9590
Pa$$ !ue 9161:0
2otal open amount 8+e#e
9195Date of $tatement6Due !ate951:0
Pa$$ !ue 1:16180
2otal open amount 8+e#e
1:195Date of $tatement6Due !ate95180
Pa$$ !ue 1816765
2otal open amount 8+e#e
1815Date of $tatement6Due !ate95765
Pa$$ !ue ;765
2otal open amount 8+e#e
7655Date of $tatement6Due !ate
2otal I"< 2otal open amount
3' Ensure A6alidate the EBisting logic in the ne( report
a' 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 specifc
page/ (ithout impacting account statement balance'
F- Do(n pament request1 2isting on a separated table on a specifc
page/ (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 Tpes
This is a stand output and itFs send to Spool/ and should be a*ailable !or
do(n load in to EBcel on the userFs des, top
5' )unning mode/ !requenc
& request
3. Tecnical !"Functional Impact Consi#erations
GEIS Functional Specification Document Page , of
)e!erence needs to be made to the technical impact !or an
interdependent processes' E'g' " change in order processing could
impact the trans!er o! requirements to $)# or collection o! statistical
data !or demand planning' These considerations need to be
e*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
$. %re" Re&uisites
K#lease indicate an dependencies that ma impact de*elopment or
!unctionalit/ in terms o! requirements !rom internal or eBternal
applications or teams' For eBample/ S"# confguration/ changes to
eBternal sstems/ master data setup
"lso/ please speci! an inter!ace or batch 9obs that must be run
prior to eBecution and dependent 9obsA operations'L
The !ollo(ing pre-requisites In eBisting report are no applica/le !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 in
multiple currencies'
'. Constraints
K#lease indicate an constraints that ma impact the Enhancement
De*elopment/ such as limited access to legac sstem/ time
constraints or data restrictions etcL
Gou 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! the
branch 8?ead oNce/ branch !unctionalit is not enabled !or "sia: This is
9ust !or in!ormation
GEIS Functional Specification Document Page 10 of
6. Technical #er!ormance Considerations
Describe potential areas !or consideration that ma impact the
per!ormance o! de*elopments associated (ith this specifcation/ or an
eBisting !unctionalit/ (hich (ould be impacted as part o! the
processAde*elopment being proposed' Include in!ormation on Transactional
*olumes/ print *olumes/ database updates etc'
Include in this section the CTOFs !or per!ormance required b the &usiness'
For eBample Criticalit o! Time !or running o! a report/ response time !or
transaction etc'
(. 8ser / O/9ec !u"ori:aion consideraions
2ist impacts to "uthoriPation concepts and rules (ith regard to the
specifcation' This should include ne( or changed authoriPations to
ob9ects' "n ne( roles (ill need to be signed oM and *alidated b
the business compliance leader to ensure no con;icts o! interest are
created'
GEIS Functional Specification Document Page 11 of
). %onsideraions (or 1esi.n Gaps / ;or4 around
Document specifc areas o! !unctionalit !or (hich the Specifcation
can not address the requirement' Gi*e the reasons and the
suggested (or, around A alternati*e solution !or meeting the need'
GEIS Functional Specification Document Page 12 of
*. )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 to
prepare 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 &illing
documents !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 the
customer account SD# (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 all
open items in DC and 2C Q F&250 amounts' "ging buc,ets Q total 2C in F&l50 b
aging buc,et'
Special indicator items and their aging should appear on subsequent pages
2anguage o! the statement should be the same language as set-up in customer
master
TEST.1
)un statements !or China 8on the same E)# plat!orm and client: Slogic !or China
statements should not be aMected' For eBample items (ith special G2 indicator H
posted in China should 0+T be included in China statements'
GEIS Functional Specification Document Page 13 of