SAP SIMPLE FINANCE -ANALYZING THE CENTRAL FINANCE OPTION.pdf
.
All About finanace and its uses..Very good material to have abasic idea of finanace and maoney.
dscg2Description complète
Sur les marchés de capitaux, on échange des capitaux, c'est-à-dire de l'argent matérialisé par des titres ou des devises. Un continuum d'échéances, du très court terme au long terme, lie au…Description complète
SAP S_4HANA Cookbook_ SAP Simple Finance, On-Pr...pdf
Descripción: Applied Quantitative Finance is a new series developed to bring readers the very latest market tested tools, techniques and developments in quantitative finance. Written for practitioners who nee...
Finance Standard Operating ProceduresFull description
ST5-FinanceFull description
La Finance Islamique au Maroc entre réticence de la demande et perspectives de développement ( réalisé par Bouthir )Full description
A great book describing the finance models and models that shochatic mathematical calculations
$4%&'& )eneft )us!ness beneft *+ )eneft ,ess comple- data structure ,ess data oot pr!nt ,ess sstem to be ma!nta!n ,+ and ,& !n one +echn!cal chanes alculat!on use to happen !n &ppl!cat!on laer no# sh!ted to database laer hat !s 'e#
Single source of truth Total tables and index tables eliminated better product!!t
educed data and !ncreased speed
Management Ledger on top of other ledger *nternal report!n and e-ternal report!n !s urther harmon!ed annot hae a separate fscal ear ar!ant entr had to be posted b 9 &!n o data eep the data re;u!rement and push rest o the data to old storae )etter report!n &ll releant d!mens!ons aa!lable )etter speed
,!ne !tem leel dr!ll do#n < 9arl =* and document #ere l!n>ed at header leel onl !t ma>es econc!l!at!on and report compleu!c> and @e-!ble )etter Aser e-per!ence 'o need to remember +codes ,ess number o cl!c>s ole based screens 9nhenced !nterat!on bet#een 9 and ) B B B B B B
lann!n lass!c =!nanc!al lann!n lann!n s!los #!th separate data stores ,on runn!n batch Cobs eerDtoDpeer transer prorams umbersome process Ean manual steps D ault prone s!mulat!on capab!l!t!es $!mulat!on !mposs!ble
Overview Classic GL Migration Changes in features Preparation for Classic GL Conguration for ew GL Prior to !nstallation " Technical Chec# $ Preparation "%unctional wor#$
Post !nstallation Migration
Go&live
Post Migration
Single source of truth SAP Accounting powered by SAP HANA rests on a uniform data model for all accounting areas. The universal data table ACDCA contains all of the line item documents from !"# !"$AA and C. All postings of these applications are written to the new table after the installation and migration are complete.
Total tables and !ndex tables eliminated
Management ledger on top of other ledger &ppend!- leder G *nher!tence the alue rom ma!n leder but post!n made to th!s leder !s not re@ected to other leder #h!ch drast!call reduces the dupl!cat!on o records
Overview
The %igration Process The migration of e&isting system configurations# master data# and application data is closely connected to the process for installing the SAP Simple !inance# on$premise edition. 'ou cannot consider the installation and migration in isolation from each other.
This graphic shows the process steps that are relevant for the installation of the SAP Simple Finance, on-premise edition and the migration of the accounting and Controlling data.
Prior to !nstallation 2176077 D hec> report or $& $/4%&'& =!nance Technical Prere'uisites =!rst letHs run throuh some !mportant notes ouHll need to read pr!or to the *nstallat!on. *deall our unct!onal team !s complet!n the preparat!on tas>s #h!le the techn!cal team ensures that ou hae eerth!n re;u!red to perorm the !nstallat!on. $& 'ote 2103558 $& $!mple =!nance nDrem!se 9d!t!on: ompat!ble &ddDns $& 'ote 2117481 elease *normat!on 'ote: $& $!mple =!nance nDrem!se 9d!t!on 1503 +h!s note !s er !mportant because !t l!sts the prere;u!s!te notes to be !nstalled pr!or to the techn!cal !nstallat!on !a $AE. *t also l!sts the $& 'otes to be !nstalled pr!or to the m!rat!on to $& $/4%&'& =!nance. $& 'ote 2100133 $& $!mple =!nance nDrem!se 9d!t!on: ompat!ble artner roducts _ $& 'ote 2035II4 $& $!mple =!nance nDrem!se 9d!t!on: *nstallat!on #!th omponents/roD ducts 'ot Jet eleased or $& $!mple =!nance &s a start!n release or $& 9 6 9%7 on $& %&'& ou need the m!n!mum component ers!ons !nd!cated !n +able 13.1. *deall #hen ou e-ecuted the $& )us!ness $u!te on $& %&'& m!rat!on us!n the $AE Katabase E!rat!on pt!on
M in i mu m S o u r ce 740 740 617 617 617
(e l e a s e S u p p or t Pa c # a g e $&)74010 $&74010 $&%61707 $&D61707*'9&&, $&D61707*'9&=*'$M
$& component compat!b!l!t and &dd G on compat!b!l!t &)& remed!at!on $ecur!t =or an upDtoDdate oer!e# o the compat!ble enterpr!se e-tens!ons !ndustr solut!ons and $& 9 addDons released or usae toether #!th the $!mple =!nance addDon see $& 'ote 1I68568 and addDon $& 'ote
.
1I76158
Preparation )*+,+) %unctional (e'uirements
$& 'ote 1I46054 G $& $!mple =!nance nDrem!se 9d!t!on: +ransact!on odes and rorams G ompar!son to 9%7 or $& 9 6.0 _ $& 'ote 211I188 G elease $cope *normat!on: $& $!mple =!nance nDrem!se 9d!t!on 1503
'ou have to perform preparatory steps before you install the on$premise edition. These include the following application$specific preparations( •
Ea>!n a prel!m!nar chec> that ascerta!ns #hether the onDprem!se ed!t!on
•
can be !nstalled #!th the current sstem sett!ns or #hether add!t!onal act!!t!es are re;u!red. Ea>!n cons!stenc chec>s that chec> the correctness o the account!n data
•
rom a techn!cal po!nt o !e# and l!st an !ncons!stenc!es erorm!n reconc!l!at!on bet#een the account!n appl!cat!ons to enable the
•
data to be mered correctl !n the un!ersal Cournal entr arr!n out per!odDend clos!n !nclud!n the storae o report!n >e fures and clos!n the post!n per!ods
nce you have carried out the preparatory steps# and have met the prere)uisites for implementing the SAP Simple !inance add$on# you can proceed to install it.
Classic GL " Start of Classic GL $
'ote
•
&ter the m!rat!on ou can cont!nue to use class!c roft enter &ccount!n !n parallel. %o#eer th!s enta!ls !nest!n t!me and eNort !n reconc!l!at!on and add!t!onal data olume. lease ta>e the ollo#!n aspects !nto cons!derat!on: * the currenc!es that ou use !n roft enter &ccount!n d!Ner rom
o
those used !n Feneral ,eder &ccount!n ou need to add the d!Ner!n currenc or roft enter &ccount!n as local or parallel currenc !n =* beore ou m!rate to ne# Feneral ,eder &ccount!n. =or th!s see $& 'ote 3II1I . *n class!c roft enter &ccount!n there can be local documentsO these
o
are documents that are entered us!n spec!al post!n transact!ons !n class!c roft enter &ccount!n. &s such documents are not transerred to $& &ccount!n po#ered b $& %&'& th!s #!ll result !n d!Nerences or the reconc!l!at!on bet#een roft enter &ccount!n and class!c Feneral ,eder &ccount!n. •
* ou also use the proft center !n class!c Feneral ,eder &ccount!n on balance sheet !tems
•
onstra!nts o the ne# F, m!rat!on o
E!rat!on to ne# Feneral ,eder &ccount!n as part o the m!rat!on to the $!mple =!nance addDon does not support the ollo#!n scenar!os: B *mplementat!on o Kocument $pl!tt!n B )alance $heets at the roft enter ,eel B E!rat!on rom $pec!al urpose ,eder to 'e# Feneral ,eder &ccount!n B 'e# *mplementat!on o arallel &ccount!n B 'e# *mplementat!on o $ement eport!n B *mplementat!on o the ,eder &pproach or arallel &ccount!n B hane !n hart o &ccounts and oners!on o hart o &ccounts B *nclus!on o ustomer =!elds B
+ranser o uant!t!es to 'e# Feneral ,eder &ccount!n
Features hanes to =unct!ons +he ollo#!n processes and unct!ons are be!n chaned !n $& &ccount!n
=ore!n urrenc Maluat!on +he #a ore!n currenc !s aluated !n the un!ersal Cournal entr corresponds to the ore!n currenc aluat!on !n ne# Feneral ,eder &ccount!n. *t d!Ners rom the ho# ore!n currenc #as aluated !n class!c Feneral ,eder &ccount!n. =or more !normat!on see =ore!n urrenc Maluat!on.
•
ost o $ales <$L &ccount!n Jou can store the data rom the $ leder !n the lead!n leder. =or more !normat!on seeost o $ales &ccount!n.
•
reparat!ons or onsol!dat!on +he character!st!cs compan *K and consol!dat!on transact!on tpe are !n the l!ne !tem table o $& &ccount!n po#ered b $& %&'& b deault and can be updated. lease note that !n th!s case ou also spec! the consol!dat!on sta!n leder as the source leder or the transer o data. +o ensure data cons!stenc !n the eneral leder ou st!ll need to ull reconc!le the consol!dat!on sta!n leder #!th the leder !n class!c Feneral ,eder &ccount!n
•
arallel Maluat!on * ou use the accounts approach !n class!c Feneral ,eder &ccount!n or parallel aluat!on us!n d!Nerent account!n pr!nc!ples ou can reta!n th!s aluat!on approach. *n th!s #a ou portra all aluat!ons us!n parallel accounts !n the lead!n leder.
roram hanes +he ollo#!n prorams !n class!c Feneral ,eder &ccount!n are replaced b other prorams !n ne# Feneral ,eder &ccount!n:
%unction
Transaction or program in classic
Transaction in General Ledger -ccounting
General Ledger -ccounting
in S-P -ccounting powered b. S-P /--
=ore!n urrenc Maluat!on
+ransact!ons F04N
urrenc +ranslat!on or )alances
roram
)alance arror#ard
+ransact!on
F.16
+ransact!on
FAGLGVTR
)alance K!spla
+ransact!on
FS10N
+ransact!on
FAGLB03
,!ne *tem K!spla
+ransact!on
FBL3N
+ransact!on
FAGLL03
F101
+ransact!on
FAGLF101
SAPF100
)/$ $upplement * +ransact!on &nals!s
F05N F06N
< FASB52L
+ransact!on
+ransact!on
FAGL_FCV
FAGL_FC_TRANS
+he dr!lldo#n reports !n ne# Feneral ,eder &ccount!n d!Ner rom those !n class!c Feneral ,eder &ccount!n. =or more !normat!on on the dr!lldo#n reports !n ne# Feneral ,eder &ccount!n see the documentat!on !n ne# Feneral ,eder &ccount!n on the $& %elp ortal under http://help.sap.com/erp $& 9 entral omponent &ccount!n =!nanc!al &ccount!n <=*L Feneral ,eder &ccount!n <=*DF,L <'e#L eport!n Kr!lldo#n eports .
Preparations for classic General Ledger -ccounting +o ensure that the data !n class!c Feneral ,eder &ccount!n #!ll be transerred correctl to the ne# $& &ccount!n po#ered b $& %&'& and can correspond!nl be correctl reproduced there ou need to perorm a number o preparator steps.
Process +o prepare or the m!rat!on complete the ollo#!n steps: * ou hae used !nteraces to connect our sstem to e-ternal sstems that
•
ma>e post!ns to Feneral ,eder &ccount!n #hether adCustments need to be made to the !nteraces: o
hec> #hether the !nteraces use the ent!t!es or ne# Feneral ,eder &ccount!n. * th!s !s not the case enhance the !nteraces accord!nl.
o
hec> #hether ou can adCust the process!n lo!c used b the !nteraces so that the document olume !s reduced.
o
Jou can no loner use the pre!ous &,9 d!str!but!on scenar!os or =!nanc!al &ccount!n. ) act!at!n the bus!ness unct!on =*'D F,_K*$+_$9'_1 ou can replace the old &,9 d!str!but!on scenar!os #!th a ne# one. =or more !normat!on see the documentat!on on the releant bus!ness unct!on as #ell as the documentat!on !n $& ,!brar under Kocument +ranser As!n &,9 <=*DF, <'e#LL.
•
* ou use ore!n currenc aluat!on reset the aluat!ons or all per!ods !n the current fscal ear so that the aluat!on d!Nerences !n the open !tems are set to ero. eset the aluat!ons us!n proram $&=100. +h!s step !s necessar because ore!n currenc aluat!on !n ne# Feneral ,eder &ccount!n does not cons!der the results o the Maluat!on or )alance $heet reparat!on unct!on !n class!c Feneral ,eder &ccount!nO conse;uentl !ncorrect alues m!ht be the result o not !n!t!al!!n the aluat!on d!Nerences.
* ou do not et use an aluat!on areas s#!tch to us!n aluat!on areas and
•
accounts dependent on aluat!on areas to ensure the correct appl!cat!on o the ull automat!c ore!n currenc aluat!on #!th parallel accounts. Jou ma>e the necessar sett!ns !n ustom!!n
er!od!c rocess!n Maluate .
&ccount!n po#ered b $& %&'& and hae to date been us!n the unct!on $elect &dd!t!onal )alance $heet and roft and ,oss &ccountse the necessar sett!ns !n ustom!!n o Feneral ,eder &ccount!n <'e#L under Easter Kata roft enter &ss!n Keault roft enter to &ccounts . lose all pre!ous per!ods and fscal ears.
•
+o ensure the cons!stenc o data ahead o the m!rat!on perorm
•
reconc!l!at!ons !n class!c Feneral ,eder &ccount!n #!th other appl!cat!on components !n part!cular reconc!l!at!on o the subleders #!th class!c Feneral ,eder &ccount!n. Jou are recommended to perorm the ollo#!n chec>s onl or fscal ears #!th a complete dataset
o
o
•
=!nanc!al &ccount!n omparat!e &nals!s
Feneral ,eder &ccount!n. Jou can use these fnanc!al statements ater the m!rat!on to chec> the cons!stenc o the m!rated data. •
onfure the $& &ccount!n po#ered b $& %&'& that cont!nues to use confurat!ons or the ne# Feneral ,eder &ccount!n. =or more !normat!on see onfur!n 'e# Feneral ,eder &ccount!n.
Kefne the lead!n leder under =!nanc!al &ccount!n Flobal $ett!ns <'e#L ,eders ,eder Kefne ,eders or Feneral ,eder &ccount!n . &ss!n totals !e# =&F,=,9P+ to the lead!n leder.
2.
&ss!n update scenar!os and opt!onal felds to the lead!n leder under =!nanc!al &ccount!n Flobal $ett!ns <'e#L ,eders ,eder &ss!n $cenar!os and ustomer =!elds to ,eders : •
* ou hae pre!ousl used roft enter &ccount!n !n class!c Feneral ,eder &ccount!n ass!n the standard scenar!o =*'_& !n th!s act!!t.
•
* ou hae pre!ousl used the preparat!ons or consol!dat!on !n class!c Feneral ,eder &ccount!n ass!n the standard scenar!o =*'_'$ !n th!s act!!t.
•
&ss!n all other re;u!red update scenar!os.
'ote *mplement!n an update scenar!o subse;uentl !noles cons!derable eNort. onse;uentl #e recommend that ou ass!n all potent!all re;u!red scenar!os to the lead!n leder dur!n the m!rat!on and not ater !t. 'ote ho#eer that ass!n!n a lare number o update scenar!os can !ncrease the data olume cons!derabl and thereb hae a neat!e !mpact on perormance. 3.
*n $ect!on 13.2.2 #eHll tal> about the techn!cal components and ers!ons needed to !nstall $& $/4%&'& =!nance.!n this section1 we want to give an overview of the functional tas#s to be completed b. the business anal.sts "or %! conguration resource$ prior to the technical team performing an. installations. *tHs !mportant to note that ou can m!rate to $& $/4%&'& =!nance rom an ers!on o F,. Jou can m!rate rom an comb!nat!on o class!c F, ne# F, old && or ne# && to $& $/4%&'& =!nance !n one step us!n the m!rat!on tools pro!ded b $& #h!ch are accessed !a the *mplementat!on Easter Fu!de <*EFL us!n +ransacD t!on $. +he ollo#!n !s a l!st o tas>s to be completed b the unct!onal teams beore the techn!cal teams can moe or#ard #!th the techn!cal !nstallat!on ! ne# asset deprec!at!on !s act!e. * not then ou need to act!ate. 3. *mplement roram Q=*'$_E*F_9%_A$+_$9++'F$ rom $& 'ote 212I306 to chec> the cons!stenc o sett!ns bet#een F, and . 4. hec> cons!stenc bet#een documents and reports us!n eport =*'K9P_ '&. 5. econc!le && #!th F, us!n +ransact!on &)$+ and +ransact!on &)$+2. 6. econc!le &ccounts aable/&ccounts ece!able <&/&L subleders #!th!n F, us!n eport $&=1I0 or eport =&F,=03. 7. econc!le the Eater!als ,eder no#n rom the ne# F, m!rat!onL. 13. 9nsure all balances hae carr!ed or#ard !n the F, and sub leders.
&ter those tas>s are complete our team m!ht #ant to e-ecute some standard reD port!n or al!dat!on purposes ater the m!rat!on. $ome e-ample reports ollo#: _ =!nanc!al statement _ &sset h!stor sheet _ ustomer and endor sales l!st and open !tem l!sts _ +otals or cost centers ,astl our team #!ll #ant to ensure an delta e-tracts related to =* or the $& )us!ness arehouse <$& )L sstem hae been processed completel. &s part o the techn!cal uprade and !nstallat!on act!!t!es the techn!cal team #!ll hold all bac>round Cobs and !nteraces.
Activities 'ou perform the following activities in your test system and if you are using classic Asset Accounting# new Asset Accounting or the Simple !inance add$on *.+.
•
=rom $& 'ote 1I3I5I2
!mplement report &$=*'_E*F_9%9 and
test #hether the necessar prere;u!s!tes or ne# &sset &ccount!n hae been ulflled us!n report &$=*'_E*F_9%9 <hec> on rere;u!s!tes )eore =*D&& E!rat!onL. •
* ou d!scoer #hen e-ecut!n report &$=*'_E*F_9%9 that currenc areas are m!ss!n ou hae to create these frst !n a separate proCect and hae the sstem determ!ne the alues.
•
Jou need the ne# deprec!at!on calculat!on rom the 9nterpr!se 9-tens!on =!nanc!als 9-tens!on <9&D=*'L. hec> ! the ne# deprec!at!on calculat!on !s act!e <$& 'ote I65032 L. * necessar !mplement the ne# deprec!at!on calculat!on as part o a separate proCect.
The following contain all further steps and activities that you have to perform before installation can ta,e place. •
•
•
ons!stenc hec>s )eore *nstallat!on and E!rat!on hec> ustomerDKefned od!n %andl!n ustomerDKefned =!elds and *nteraces
•
er!odD9nd los!n &ct!!t!es
'ote * ou do not #ant to use &sset &ccount!n and are also not plann!n on us!n !t !n uture then note the ollo#!n: Jou arenot allo#ed to act!ate &sset &ccount!n dur!n the m!rat!on. Jou must deact!ate &sset &ccount!n !nstead b deact!at!n the component &*' <&sset &ccount!nL !n our sstem/cl!ents !n table+&.
'ote E!rat!on to $& &ccount!n po#ered b $& %&'& leads to chanes compared to class!c Feneral ,eder &ccount!n. Jou need to be a#are o these chanes beore ou perorm the !nstallat!on and m!rat!on. =or more !normat!on see:
Consistenc. Chec#s 2efore !nstallation and Migration Procedure )eore !nstall!n ou chec> the cons!stenc o our =* data. erorm the ollo#!n cons!stenc chec>s !n our test sstem and product!on sstem: •
9-ecute report =*'K9P_'& #!th the opt!on *nde-es s Kocuments. Jou perorm th!s act!!t ! ou are us!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0.
•
hec> documents aa!nst transact!on fures or all fscal ears !n #h!ch arch!!n has not et ta>en place.
aut!on
* ou canRt perorm cons!stenc chec>s o documents aa!nst transact!on fures us!n report =*'K9P_'& due to runt!me !ssues perorm the cons!stenc chec>s ater the !nstallat!on !nstead. +o do so !n ustom!!n choose E!rat!on rom $& 9 to $& &ccount!n po#ered b $& %&'& E!rat!on +echn!cal hec> o +ransact!on Kata &nale +ransact!onal Kata . hec> the result !n the K!spla $tatus o &nals!s o +ransact!on Kata ustom!!n act!!t. +hen carr out the econc!le +ransact!onal Kata act!!t and chec> the result !n the K!spla $tatus o +echn!cal econc!l!at!on o +ransact!onal Kata act!!t. &ll o these act!!t!es are aa!lable to ou !n our test sstem ater ou hae !nstalled $& $!mple =!nance onDprem!se ed!t!on. * ou are us!n class!c Feneral ,eder &ccount!n e-ecute the
o
reconc!l!at!on or the eneral leder and the &/& subleders. Ase report $&=1I0 to do th!s. * ou are us!n ne# Feneral ,eder &ccount!n e-ecute the
o
reconc!l!at!on or the eneral leder and the subleders. Ase report +=_E&9_MQ to do th!s or choose transact!on =&F,=03. •
econc!le the eneral leder #!th &sset &ccount!n or the lead!n aluat!on and parallel aluat!on. Ase the ollo#!n reports !n se;uence: o
Jou use th!s report ! ou are us!n class!c and ne# &sset &ccount!n. o
* the report econc!l!at!on roram =*D&& SDT Feneral ,eder: ,!st #!th K!Nerence &ccounts or =*D&& <'e#L and =*DF, <'e#L
Jou use th!s report ! ou are us!n class!c &sset &ccount!n. 2. ompare the leders ! ou are us!n ne# Feneral ,eder &ccount!n. Ase report FAE4 to do th!s or choose transact!on F&. Jou perorm th!s step ! ou are us!n ne# Feneral ,eder &ccount!n. 3. econc!le Eater!als Eanaement
Chec# Customer&3ened Coding +he m!rat!on to $& &ccount!n po#ered b $& %&'& enerates ne# data structures !n &ccount!n and replaces e-!st!n tables #!th sameDnamed !e#s. Jou must thereore perorm the ollo#!n chec>s and act!!t!es !n the test sstem: •
hec> ! ou hae #r!te accesses to the tables !n our o#n customer obCects !n our customer namespace. Jou hae to replace these accesses s!nce the !e#s #!th same names allo# onl read access.
•
hec> ! ou hae our o#n customerDspec!fc !e#s !n our o#n obCects !n our customer namespace or the tables that no loner e-!st. Jou hae to replace these !e#s #!th an openD$, $9,9+ or the call o a read module s!nce the Kata K!ct!onar does not support database !e#s that are based on other !e#s.
'ote =or more !normat!on about deal!n #!th customerDspec!fc cod!n see $& 'ote 1I76487
$!mple =!nance addDon 1.0: *normat!on about adCust!n
customerDspec!fc prorams to the s!mpl!fed data model !n $& $!mple =!nance. •
* ou are m!rat!n rom class!c &sset &ccount!n note the ollo#!n: )atch !nput prorams or &)01 are no loner supported !n ne# &sset &ccount!n. * ou are us!n customerDdefned prorams ou must conert these to )&*s.
/andling Customer&3ened %ields and !nterfaces Procedure •
* ou are us!n ne# Feneral ,eder &ccount!n and also us!n customerD defned felds these felds are enerated to the appropr!ate compat!b!l!t !e#s.
•
=or customer felds !n )$9F and the !nde- tables note the ollo#!n or the creat!on o the !e#s #!th the same names: * a customer feld e-!sts !n both the )$9F and !n the !nde-es !t !s automat!call enerated !nto the !e# #!th the same name. *t !s not transerred !nto a !e# #!th the same name ! the customer feld onl e-!sts !n the !nde-. *n th!s case the feld must frst be !ncluded !n the )$9F and flled us!n a customer proram.
•
* ou transerred data rom our Q tables to ne# Feneral ,eder &ccount!n dur!n the m!rat!on to the =!nanc!al &ccount!n addDon 1.0 ou hae to delete the data o these Q tables beore the m!rat!on to $& $!mple =!nance onDprem!se ed!t!on. * ou do not delete the data the data o the Q tables !s m!rated aa!n and transerred to the ne# table structure. +he alues #ould then be dupl!cated.
•
* ou hae used !nteraces to connect our sstem to e-ternal sstems that ma>e post!ns to Feneral ,eder &ccount!n #hether adCustments need to be made to the !nteraces. =or more !normat!on see =*DF, <'e#L +ranser o +otals and $!nle Kocuments !n K!str!buted $stems .
•
*n $& $!mple =!nance onDprem!se ed!t!on 1503 &,9 scenar!os are onl part!all supported. &n $& $!mple =!nance onDprem!se ed!t!on 1503 sstem cannot sere as an &,9 rece!er or l!ne !tems. +he reason !s that !n $!mple =!nance onDprem!se ed!t!on 1503 =* and l!ne !tems use the same pers!stence table. +hereore the l!ne !tems cannot be posted alone #!thout the =* l!ne !tems the belon to. $& does not pro!de a chec> to determ!ne ! th!s scenar!o !s used !n the sstem. Jou hae to chec> th!s manuall. &,9 scenar!os or the d!str!but!on o master data such as cost centers cont!nue to be supported.
Period&0nd Closing -ctivities Procedure Anless d!rected other#!se perorm the ollo#!n act!!t!es !n our test sstem and product!on sstem and document the results. 1.
,oc> the current and pre!ous per!ods !n Eater!als Eanaement
2.
Ea>e sure that all held documents hae e!ther been posted or deleted. •
+o post held documents use transact!on =)50 or e-ample. *n the menu or the transact!on choose
•
9d!t $elect %eld Kocument .
+o delete held documents ou can use proram =+E),K. Jou can delete !nd!!dual held documents !n transact!on =)50. *n the menu or the transact!on choose 9d!t Kelete %eld Kocument .
•
* ou donRt hae an held documents !n our sstem no act!on !s re;u!red.
6.
* ou are alread us!n accountDbased proftab!l!t anals!s perorm a delta upload to $& ) or all accountDbased D& Kata$ources or #h!ch ou use the delta method. Jou perorm th!s act!!t ! ou are us!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0.
7.
Ea>e sure that ou hae carr!ed or#ard all o the balances !n all appl!cat!ons to the current fscal ear. +h!s also appl!es to the subleders. Ase the ollo#!n transact!ons: •
FAGLGVTR
! ou are us!n ne# Feneral ,eder &ccount!n
•
F.16
! ou are us!n class!c Feneral ,eder &ccount!n
•
AJRW
! ou are us!n &sset &ccount!n
•
F.07
! ou are us!n &ccounts ece!able and &ccounts aable
8.
+he ollo#!n appl!es or &sset &ccount!n: lose all fscal ears e-cept the current fscal ear. Ase proram&&)$00 to do th!s.
I.
Jou perorm th!s step ! ou hae been us!n class!c Feneral ,eder &ccount!n and used the ore!n currenc aluat!on #!th unct!on Maluat!on or )alance $heet reparat!on there. *n th!s case ou hae to set the aluat!on d!Nerences !n the open !tems to eroO th!s means ou reset the aluat!ons or all per!ods !n the current fscal ear. eset the aluat!ons us!n proram $&=100. +h!s step !s re;u!red because the ore!n currenc aluat!on !n ne# Feneral ,eder &ccount!n does not ta>e !nto account the results o the unct!on Maluat!on or )alance $heet reparat!on !n class!c Feneral ,eder &ccount!n. * ou do not reset the aluat!ons th!s could result !n !ncorrect alues.
10.
9-ecute all scheduled Cobs and do not schedule an ne# Cobs.
11.
,oc> the per!ods !n =!nanc!al &ccount!n
12.
9-ecute proam &$=*'_E*F_9%9 aa!n to ma>e sure that the prere;u!s!tes or &sset &ccount!n hae been met.
13.
,oc> all users !n the sstem that do not hae an tas>s assoc!ated #!th the !nstallat!on or the m!rat!on.
'ote Ko not loc> the users !n the test sstem.
aut!on Jou can start the !nstallat!on onl ater ou hae perormed all act!!t!es and steps outl!ned !n the ollo#!n sect!ons and corrected all errors and remoed all !ncons!stenc!es. r!or to *nstall!n
•
ons!stenc hec>s )eore *nstallat!on and E!rat!on
•
hec> ustomerDKefned od!n
•
%andl!n ustomerDKefned =!elds and *nteraces
•
3ocumentation for 3ataset 2efore !nstallation und Migration Procedure Jou perorm the ollo#!n act!!t!es !n our test sstem and product!on sstem. Jou al#as perorm the ollo#!n act!!t!es unless d!rected other#!se. 1.
Ea>e sure that all balance carror#ards are complete and cons!stent. +o ensure th!s carr or#ard the balances or all currenc!es and all leders aa!n.
2.
reate the documentat!on or the clos!n to compare the data #!th data ater the m!rat!on. $& recommends the ollo#!n reports or th!s: •
•
•
•
+he fnanc!al statements
•
+he eneral leder l!ne !tems l!st
•
+he compact document Cournal
•
+he asset h!stor sheet
•
+he deprec!at!on run or planned deprec!at!on <&%&=&_&,M01L
•
+he endor sales
•
+he endor open !tem l!st
•
•
+he customer open !tem l!st
•
+he customer recurr!n entr or!!nal documents
'ote +he reports that are l!sted or cost centers and orders are onl e-amples. * ou use other obCects such as proCects or product!on orders ou hae to run the appropr!ate reports and document the results.
Preparing for Migration +o prepare the data o =!nanc!al &ccount!n ontroll!n and &sset &ccount!n or m!rat!on !mmed!atel ater !nstall!n $& $!mple =!nance onDprem!se ed!t!on perorm the ustom!!n act!!t!es under E!rat!on rom $& 9 to $& &ccount!n po#ered b $& %&'& reparat!ons and E!rat!on o ustom!!n . Jou should perorm the act!!t!es ound !n the ollo#!n sect!ons o ustom!!n: •
hec> ustom!!n $ett!ns r!or to E!rat!on
•
Kefne Eessae +pes or ost!n )eore and Kur!n E!rat!on
•
reparat!ons and E!rat!on o ustom!!n or the Feneral ,eder
•
reparat!ons and E!rat!on o ustom!!n or &sset &ccount!n
•
reparat!ons and E!rat!on o ustom!!n or ontroll!n
=or more !normat!on see the documentat!on o the ustom!!n act!!t.
Preparations and Customi4ing Migration in the General Ledger )eore m!rat!n ou must perorm the necessar preparat!ons and correspond!n act!!t!es !n ustom!!n. +he steps or th!s can be ound !n the $& eerence *EF !n sect!on $& $!mple =!nance &ddDn or $& )us!ness $u!te po#ered b $& %&'& ustom!!n: reparat!ons and E!rat!on ustom!!n or the Feneral ,eder: reparat!ons and E!rat!on . =or more deta!ls on these steps see the documentat!on o the !nd!!dual steps !n the $& eerence *EF.
Process erorm the steps !n the spec!fed se;uence. 1.
&ct!ate !n the $& eerence *EF. =or more !normat!on see the $& eerence *EF sect!on &ct!ate the $& eerence *EF or =!nanc!al &ccount!n <'e#L.
2.
9-ecute act!!t hec> and &dopt =!scal Jear Mar!ants !n the $& eerence *EF.
'ote &ct!!t!es 1 and 2 are onl re;u!red ! ou #ere us!n roftab!l!t &nals!s beore m!rat!on. * ou #ere not us!n roftab!l!t &nals!s or are a ne# customer these act!!t!es not releant.
&ct!!t!es 3 to 6 are re;u!red ! ou #ant to use roftab!l!t &nals!s. eep !n m!nd ho#eer that these are notthe onl ustom!!n act!!t!es ou need to carr out !n order to use roftab!l!t &nals!s.
9Nect o the &dapt $ett!ns or roftab!l!t $ement haracter!st!cs act!!t +he &dapt $ett!ns or roftab!l!t $ement haracter!st!cs act!!t e!ther m!rates or deletes the summar!at!on sett!ns depend!n on the ollo#!n: •
•
hether account&based or costing&based proftab!l!t anals!s !s act!e hether ou carr out the act!!t before or after ou select the tpe o proftab!l!t anals!s
+here are three cases:
Se'uence
Cas 1. e)
2.
Cas 1. e,
ost!nDbased but not&ccountDbased !s selected under +pe o $ummar!at!on roftab!l!t &nals!s !n the defn!t!on o the operat!n concern
&ccountDbased !s selected under +pe o roftab!l!t &nals!s !n the defn!t!on o the operat!n concern
2.
Jou carr out the &dapt $ett!ns or roftab!l!t $ement haracter!st!cs act!!t.
Cas 1.
Jou carr out the &dapt $ett!ns or roftab!l!t $ement haracter!st!cs act!!t.
e*
2.
05ect
$ummar!at!on sett!ns are deleted.
$ummar!at!on sett!ns are deleted.
Jou select &ccountDbasedunder +pe o roftab!l!t &nals!s !n the defn!t!on o the operat!n concern
Customi4ing in the Production S.stem Procedure erorm the ollo#!n steps !n our test sstem and product!on sstem. 1.
*mport the ustom!!n sett!ns rom our confurat!on / test sstem to the product!on sstem and chec> #hether the sett!ns hae arr!ed completel.
2.
* ou hae made customerDspec!fc chanes !n our deelopment or test sstem and hae tested these successull then !mport them to the product!on sstem.
Migration Prerequisites Jou hae perormed all act!!t!es and preparator steps that are e-pla!ned !n
•
the ollo#!n: o
o
o
o
o
o
o
r!or to *nstall!n ons!stenc hec>s )eore *nstallat!on and E!rat!on hec> ustomerDKefned od!n %andl!n ustomerDKefned =!elds and *nteraces er!odD9nd los!n &ct!!t!es )us!ness econc!l!at!on )eore E!rat!on ustom!!n *mport !nto the roduct!on $stem
•
Jou hae remoed all !ncons!stenc!es and errors.
•
Jou !nstalled $& $!mple =!nance onDprem!se ed!t!on. =or more !normat!on about !nstall!n the sot#are see the *nstallat!on Fu!de at help.sap.com $& )us!ness $u!te $& %&'& *nnoat!ons or $& )us!ness $u!te roducts o#ered b $& %&'& $& $!mple =!nance &ddDn $& )us!ness $u!te po#ered b $& %&'& 2.0 *nstallat!on and Aprade *normat!on E!rat!on Fu!de
•
Jou hae cop!ed our ustom!!n sett!ns rom the confurat!on/test sstem to our product!on sstem.
•
Jou hae tested our customerDspec!fc chanes !n the test or deelopment sstem and corrected an errors. Jou then cop!ed the chanes to our product!on sstem.
Activities Jou can no# e-ecute the m!rat!on. &ter ou !nstall $& $!mple =!nance onDprem!se ed!t!on ou can fnd all m!rat!on steps !n ustom!!n !n the sect!on E!rat!on to $& 9 au $& &ccount!n po#ered b $& %&'& *nstallat!on . 1.
art!t!on the table or the Cournal entr. +o do so perorm the ustom!!n act!!t art!t!on!n o An!ersal ournal 9ntr ,!ne *tems +able. =or more !normat!on see the documentat!on o the act!!t.
2.
erorm the ustom!!n act!!t eenerate K$ M!e#s and =!eld Eapp!n.
3.
'o# e-ecute all act!!t!es !n the order the are l!sted !n the ollo#!n sect!ons.
Migration of Cost 0lements and Customi4ing &s o $& $!mple =!nance addDon 2.0 $$00 or $& )us!ness $u!te po#ered b $& %&'& the ontroll!n<L and =!nanc!al &ccount!n <=*L components hae been mered. &ll bus!ness transact!ons G both e-ternal and !nternal G are recorded on F/, accounts. ost elements are no loner ma!nta!ned separatel !n but as a spec!al tpe o F/, account. &s a result o the mere o and =* ou need to do the ollo#!n: •
•
E!rate our secondar cost elements to the chart o accounts +ranser the account ass!nments o our cost elements to the deault account ass!nment
•
&dopt the author!at!ons s!nce the author!at!ons or cost element master data ma!ntenance hae been superseded b the author!at!ons or F/, account master data ma!ntenance
Process +o perorm these steps carr out the ollo#!n act!!t!es !n ustom!!n under $& $!mple =!nance &ddDn or $& )us!ness $u!te po#ered b $& %&'& E!rat!on E!rat!on o ost 9lements and ustom!!n : 1.
hec> ons!stenc o F/, &ccounts and ost 9lements )eore start!n the actual m!rat!on ou need to carr out th!s step to chec> #hether the F/, accounts and cost elements are cons!stent #!th each other.
'ote Ea>e sure to correct an !ncons!stenc!es bet#een F/, accounts and cost elements other#!se the F/, account master records #!ll hae the #ron account tpes ater m!rat!on. 2.
E!rate $econdar ost 9lements to hart o &ccounts
Migration of Cost 0lements and Customi4ing &s o $& $!mple =!nance addDon 2.0 $$00 or $& )us!ness $u!te po#ered b $& %&'& the ontroll!n<L and =!nanc!al &ccount!n <=*L components hae been mered. &ll bus!ness transact!ons G both e-ternal and !nternal G are recorded on F/, accounts. ost elements are no loner ma!nta!ned separatel !n but as a spec!al tpe o F/, account. &s a result o the mere o and =* ou need to do the ollo#!n:
•
•
E!rate our secondar cost elements to the chart o accounts +ranser the account ass!nments o our cost elements to the deault account ass!nment
•
&dopt the author!at!ons s!nce the author!at!ons or cost element master data ma!ntenance hae been superseded b the author!at!ons or F/, account master data ma!ntenance
Process +o perorm these steps carr out the ollo#!n act!!t!es !n ustom!!n under $& $!mple =!nance &ddDn or $& )us!ness $u!te po#ered b $& %&'& E!rat!on E!rat!on o ost 9lements and ustom!!n : 1.
hec> ons!stenc o F/, &ccounts and ost 9lements )eore start!n the actual m!rat!on ou need to carr out th!s step to chec> #hether the F/, accounts and cost elements are cons!stent #!th each other.
'ote Ea>e sure to correct an !ncons!stenc!es bet#een F/, accounts and cost elements other#!se the F/, account master records #!ll hae the #ron account tpes ater m!rat!on. 2.
E!rate $econdar ost 9lements to hart o &ccounts
Technical Chec# of Transaction 3ata Procedure *n ustom!!n ou perorm all act!!t!es !n the sect!on E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on +echn!cal hec> o +ransact!on Kata . =or more !normat!on see the documentat!on o the ustom!!n act!!t.
'ote Jou perorm all o the steps !n our test sstem and product!on sstem. Jou perorm all o the steps ! ou are us!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. 1.
9-ecute the act!!t &nale +ransact!onal Kata.
2.
9-ecute the act!!t K!spla $tatus o &nals!s o +ransact!on Kata.
3.
9-ecute the act!!t econc!le +ransact!onal Kata.
+he mater!al leder !s re;u!red ! ou are us!n Eater!als Eanaement D *nentor Eanaement !n $& $/4%&'& onDprem!se ed!t!on.
•
Jou need to m!rate the mater!al leder een ! ou are alread us!n =!nance
•
Jou need to m!rate the mater!al leder een ! ou are alread us!n the mater!al leder !n our source sstem.
E!rate the mater!al leder b carr!n out the ustom!!n act!!t!es under E!rat!on rom $& 9 to $& &ccount!n po#ered b $& %&'& E!rat!on Eater!al ,eder E!rat!on .
Prerequisites Jou need to hae m!rated the mater!al leder ustom!!n sett!ns #!th the act!!t reparat!ons and E!rat!on o ustom!!n or Eater!al ,eder E!rate Eater!al ,eder ustom!!n . Jou need to hae perormed the ollo#!n act!!t!es under Kata E!rat!on: •
+echn!cal hec> o +ransact!on Kata
Process 9-ecute the ollo#!n act!!t!es !n the spec!fed se;uence: 1.
E!rate Eater!al ,eder
2.
K!spla $tatus o Eater!al ,eder E!rat!on
3.
hec> E!rat!on o Eater!al ,eder
4.
K!spla $tatus o Eater!al ,eder E!rat!on hec>
=or more !normat!on on each act!!t see the *EF documentat!on or the act!!t.
Migrate Material Ledger 'ote +h!s m!rat!on step uses d!alo processes #!th parallel process!n. lease ma>e sure that a h!h number o d!alo processes !s aa!lable beore start!n th!s step.
'ote •
+he mater!al leder !s re;u!red ! ou are us!n Eater!als Eanaement D *nentor Eanaement !n $& $/4%&'& onDprem!se ed!t!on.
•
Jou need to m!rate the mater!al leder een ! ou are alread us!n =!nance
•
Jou need to m!rate the mater!al leder een ! ou are alread us!n the mater!al leder !n our source sstem.
+h!s act!!t act!ates the mater!al leder or all aluat!on areas. +h!s creates mater!al leder master data and conerts !nentor alues and mater!al pr!ces !nto the mater!al leder currenc!es es place. *n postDm!rat!on m!ss!n h!stor table entr!es
Prerequisites erorm th!s act!!t after the ollo#!n ustom!!n act!!t!es under E!rat!on rom $& 9 to $& &ccount!n po#ered b $& %&'& hae been successull completed. Ander reparat!ons and E!rat!on o ustom!!n:
$elect all aluat!on areas b enter!n an aster!s>
round b select!n )ac>round rocess!n. =or test purposes ou ma run the proram !n test mode b select!n +est run. +he proram #!ll be e-ecuted !n parallel mode. *n order to control the parallel e-ecut!on ou ma spec! a spec!fc serer roup or chane the pac>ae s!e.
3.
hoose 9-ecute.
4.
hec> the results !n the lo #!th
$stem #n obs .
Jou can also see the m!rat!on status #!th the K!spla $tatus o Eater!al ,eder E!rat!on act!!t.
Result 9Nects on Eater!al Easter Kata •
+he mater!al leder !s act!ated !n all mater!al master records o the plant pro!ded that alue updat!n !s defned !n table +134E.
r!ce determ!nat!on !s set to 2 !n all mater!al master records.
•
* ou #ant to use pr!ce determ!nat!on 3 !nstead see the ollo#!n documentat!on !n the $& %elp ortal under &ctual ost!n/Eater!al ,eder <DD&+L: o
Eater!al leder master data !s created or all per!ods.
•
r!ces are calculated !n the other currenc!es or the mater!al leder data
9Nects on +ransact!on Kata •
*nentor ;uant!t!es !nentor alues and pr!ces are transerred rom mater!al master records to the mater!al leder data or all per!ods.
•
*nentor alues and pr!ces are calculated !n the currenc!es o the mater!al leder or the current date us!n the standard e-chane rate tpe.
•
urchase and product!on order h!stor!es are conerted !nto the second and th!rd mater!al leder currenc!es.
3ispla. Status of Material Ledger Migration +h!s act!!t allo#s ou to chec> the current status o mater!al leder m!rat!on ! ou e-ecuted the E!rate Eater!al ,eder act!!t !n the bac>round. Eater!al leder m!rat!on has been e-ecuted successull ! one o the ollo#!n !normat!on statuses !s sho#n or all aluat!on areas !n the cl!ent: •
E, l!e s!nce $/4 %&'& m!rat!on
•
E, l!e beore $/4%&'& m!rat!on and postDm!rat!on too> place
Eater!al leder m!rat!on !s st!ll !n process ! the ollo#!n status !s sho#n: •
•
E, not l!e E, l!e beore $/4%&'& m!rat!on. %o#eer postDm!rat!on m!ss!n
Process Ase the eresh button to retr!ee ne# m!rat!on status data. hec> the ,os E, E!rat!on or l!ent tab reularl to determ!ne #hether errors occurred. * there #ere an errors contact $& support.
Chec# Migration of Material Ledger +h!s act!!t chec>s #hether the mater!al leder !s act!e !n all aluat!on areas and perorms ar!ous techn!cal chec>s.
Prerequisites erorm th!s act!!t after the E!rate Eater!al ,eder act!!t has been completed successull. erorm th!s act!!t onl. if all valuation areas are active in the client as determ!ned b the K!spla $tatus o Eater!al ,eder E!rat!on act!!t.
&n aluat!on areas !n #h!ch the mater!al leder !s not act!e * a aluat!on area !s not act!e no mater!al leder entr!es #ere created and no oods moements are poss!ble or that aluat!on area.
•
&n master records #h!ch do not hae a correspond!n E&& table entr * a master record does not hae a correspond!n E&& table entr no mater!al leder entr!es #ere created and no oods moements are poss!ble or that mater!al.
•
&n mother sements as part o spl!t aluat!on that do not hae an entr !n table E, *ncons!stenc!es #!ll ar!se ! an such mother sements e-!st.
•
&n records or #h!ch the E,E&& @a #as not set properl * an such records e-!st mater!al leder entr!es m!ht not hae been created. +h!s #ould mean that the mater!al cannot be used !n oods moements or the mater!al aluat!on record #!ll not be sho#n b -)9<9)9 9)9% E)9 E)9% )9 )9% )9 and )9%L pro- K$ !e#s.
•
&n cases #here the number o records !s not the same !n the old and ne# -)9<%L table * the number o records d!Ners !n the old and ne# table the mater!al aluat!on record !s not sho#n b-)9<%L pro- K$ !e#s.
•
&n cases #here the record and the correspond!n feld alues are not the same !n the old and ne# -)9<%Ltable.
+h!s represents a chec> o the m!rat!on o the -)9<%L local currenc entr!es to the mater!al leder. &n !ncons!stenc!es mean that the mater!al aluat!on record m!ht not be sho#n b -)9<%L pro- K$ !e#s. •
&n product!on order h!stor!es that #ere not conerted !nto the re;u!red currenc!es
•
&n purchase order h!stor!es that #ere not conerted !nto the re;u!red currenc!es
arn!n messaes and error messaes ma be !ssued. * an error messaes are l!sted contact $& support.
3ispla. Status of Material Ledger Migration Chec# +h!s act!!t d!splas the results o the hec> E!rat!on o Eater!al ,eder act!!t.
'ote erorm th!s act!!t after the hec> E!rat!on o Eater!al ,eder act!!t.
Process 9-ecute the proram or the re;u!red cl!ent. * an errors are l!sted contact $& support.
Migration & 0nrichment of 3ata Procedure erorm all o the act!!t!es !n ustom!!n !n the sect!on $& $!mple =!nance addD on or $& )us!ness $u!te po#ered b $& %&'& E!rat!on E!rat!on D 9nr!chment o Kata . =or more !normat!on see the documentat!on o theustom!!n act!!t.
'ote Jou perorm all o the steps !n our test sstem and product!on sstem. Jou perorm all o the steps ! ou are us!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. 1.
9-ecute the act!!t 9nr!ch +ransact!onal Kata.
2.
9-ecute the act!!t K!spla $tatus o 9nr!chment o +ransact!onal Kata.
3.
9-ecute the act!!t hec> o E!rated Kocuments.
4.
9-ecute the act!!t K!spla $tatus o hec> o E!rated Kocuments.
Migration of 3ocuments and Line !tems to the 3ata Structure Procedure *n ustom!!n ou perorm all act!!t!es !n the sect!on E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on E!rat!on o ,!ne *tems !nto 'e# Kata $tructure . =or more !normat!on see the documentat!on o the ustom!!n act!!t.
'ote
Jou perorm all o the steps !n our test sstem and product!on sstem. Jou perorm all o the steps ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. 1.
2.
9-ecute the act!!t E!rate &ccount!n Kocuments to An!ersal ournal 9ntr $tructure. 9-ecute the act!!t K!spla $tatus o Kocument E!rat!on to An!ersal ournal 9ntr.
3.
9-ecute the act!!t hec> E!rat!on o &ccount!n Kocuments to An!ersal ournal 9ntr.
* ou are us!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0 e-ecute the act!!tE!rate Feneral ,eder &llocat!ons
Migration of 2alances *n ustom!!n ou perorm all act!!t!es !n the sect!on E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on E!rat!on o )alances . =or more !normat!on see the documentat!on o the ustom!!n act!!t.
Process 'ote Jou perorm all o the steps !n our test sstem and product!on sstem.
Jou perorm all o the steps ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0.
1.
9-ecute the act!!t E!rate )alances.
2.
9-ecute the act!!t K!spla $tatus o )alance E!rat!on.
3.
9-ecute the act!!t alculate *n!t!al Keprec!at!on Malues.
4.
9-ecute the act!!t hec> E!rat!on o )alances.
5.
9-ecute the act!!t Eon!tor hec> o )alances.
Completing the Migration *n ustom!!n ou perorm all act!!t!es !n the sect!on E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on E!rat!on o )alances . =or more !normat!on see the documentat!on o the ustom!!n act!!t.
'ote Jou perorm all o the steps !n our test sstem and product!on sstem. Jou perorm all o the steps ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0.
Process Jou perorm all o the act!t!!es ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. Jou perorm all the ollo#!n act!!t!es !n our test sstem and product!on sstem. 1. 2.
9-ecute the act!!t alculate *n!t!al Keprec!at!on Malues. 9-ecute the act!!t econc!le Keprec!at!on Malues and +otals Malues !n &sset &ccount!n.
3.
9-ecute the act!!t econc!le and ompare E!rated Kata.
4.
9-ecute the act!!t $et E!rat!on to ompleted.
Migration of /ouse 2an# -ccounts 'ote •
* ou do not use $& ash Eanaement po#ered b $& %&'& erorm the ollo#!n steps !n our test sstem and product!on sstem.
•
* ou use $& ash Eanaement po#ered b $& %&'& Jou can s>!p th!s top!c and ollo# the !nstruct!ons !n the Kata $etup Fu!de or $& ash Eanaement po#ered b $& %&'& to m!rate house ban> accounts and set up the ban> account master data. +he u!de !s aa!lable on $& $er!ce Ear>etplace at http://ser!ce.sap.com/erpD!nst $& 9 &ddDns $& $!mple =!nance nDrem!se 9d!t!on $& $!mple =!nance nDrem!se 9d!t!on 1503 .
%ouse ban> accounts hae been mered !nto ban> account master data. &s a conse;uence ou need to m!rate house ban> accounts or!!nall stored !n database table +012 to table =,E_)&E_&,*'2. &ter the m!rat!on ou can use the house ban> accounts as usual. %o#eer to create and ma!nta!n house ban> accounts ou must do so b ed!t!n the ban> account master data. &ter ou m!rate e-!st!n house ban> accounts ou can create ne# house ban>s and house ban> accounts ! necessar. +o create house ban>s ou can use transact!on FI12_HBANK. =or more !normat!on see Kefn!n %ouse )an>s. +o create house ban> accounts ou can do so b ed!t!n the connect!!t path or ban> accounts. =or more !normat!on see Kefn!n %ouse )an> &ccounts.
'ote &ter the m!rat!on ou can onl #or> #!th house ban> accounts us!n the eb Knpro user !nteraces. +o be able to use the eb Knpro user !nteraces the ollo#!n must be confured !n the bac>Dend serer: $et up the $& 'eteaer )us!ness l!ent <')L.
K&_=,E_)&E_%*9&%J K&_=,E_)&E_&_E&$+9 K&_=,E_A,&K_K',&K &ss!n =F role $&_=*_),_)&'_E&$+9_K&+& to our users.
•
Prerequisites Ea>e sure ou hae confured the ollo#!n ustom!!n act!!t!es beore ou m!rate house ban> accounts. Jou can fnd them under =!nanc!al $uppl ha!n Eanaement ash and ,!;u!d!t Eanaement )an> &ccount Eanaement )as!c $ett!ns . 'umber ranes or ban> account *Ks
•
*n ban> account master data each ban> account !s ass!ned #!th a techn!cal *K #hen created. +o defne the techn!cal *K ass!nment rules confure the ollo#!n ustom!!n act!!t!es: 1.
*n the ustom!!n act!!t Kefne 'umber anes or )an> &ccount +echn!cal *Ks defne number ranes or ban> account techn!cal *Ks.
2.
*n the ustom!!n act!!t Kefne $ett!ns or )an> &ccount Easter Kata on the )an> &ccount Easter Kata $ett!n tab spec! a number rane or the +ech. *K 'o. an feld.
•
'umber ranes or chane re;uests
+he sstem automat!call ass!ns a number to a chane re;uest once !t !s created !n )an> &ccount Eanaement. +o confure the chane re;uest *K ass!nment rules confure the ollo#!n ustom!!n act!!t!es: 1.
*n the ustom!!n act!!t Kefne 'umber anes or or>@o# hane e;uests defne number ranes or chane re;uests.
2.
*n the ustom!!n act!!t Kefne $ett!ns or )an> &ccount Easter Kata on the )an> &ccount Easter Kata $ett!n tab spec! a number rane or the e;. 'o. an feld. )an> account tpes
•
)an> account tpe !s one o the attr!butes !n ban> account master data. Jou can defne d!Nerent tpes o accounts to su!t d!Nerent bus!ness purposes. &ccount tpes can be used as an anals!s d!mens!on !n report!n and plann!n. +o ma!nta!n ban> account tpes !n ustom!!n act!!t Kefne $ett!ns or )an> &ccount Easter Kata defne account tpes on the &ccount +pe Kefn!t!on tab.
Activities +o m!rate the house ban> accounts ou can use transact!on FCLM_BAM_MIGRATION . *t m!rates our house ban> accounts to )an> &ccount Eanaement ,!te and creates ban> account master data based on e-!st!n house ban> accounts #!th the most essent!al bus!ness data !nclud!n: e !normat!on such as ban> account number ban> >e ban> countr and
•
ban> name. +he connect!!t bet#een ban> accounts and house ban> accounts.
•
Kur!n the !mplementat!on phase ou ma #or> #!th seeral sstems such as the deelopment sstem the test!n sstem and the product!on sstem. Jou can perorm the m!rat!on !n e!ther o the ollo#!n #as. * the sstems ou #or> #!th store the same set o house ban> accounts
•
proceed as ollo#s: 1. 2.
*n one o our sstems perorm the m!rat!on. * necessar create ne# ban> account master data accountsL.
3.
+ranser all the ban> account master data to other sstems. * the sstems ou #or> #!th store d!Nerent sets o house ban> accounts
•
proceed as ollo#s: 1.
*n each o our sstems perorm the m!rat!on.
2.
* necessar !n one o the sstems create ne# ban> account master data accountsL.
3.
+ranser the ban> account master data select!el rom the sstem !n step 2 to other sstems accord!n to our bus!ness needs.
'ote •
reat!n or mod!!n ban> account master data accountsL does not tr!er transport to other sstems. +o mass!el transer the ban> account master data ou can use the tool*mport and 9-port )an> &ccounts. =or more !normat!on on the tool see *mport!n and 9-port!n )an> &ccounts.
•
&ter the oDl!e ou are recommended to ma!nta!n our ban> account master data !n our product!on sstem. Jou can transer the master data to other sstems such as test!n or deelopment sstems ! necessar.
=or more !normat!on on ho# to use th!s tool see the proram documentat!on o transact!on FCLM_BAM_MIGRATION .
-ctivities to be 0xecuted -fter the Migration *n ustom!!n ou perorm all act!!t!es !n the sect!on E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on &ct!!t!es &ter E!rat!on . =or more !normat!on see the documentat!on o the ustom!!n act!!t.
Process 'ote Jou perorm the ollo#!n steps !n our test sstem and product!on sstem. Jou perorm the ollo#!n act!!t!es ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n or ne# Feneral ,eder &ccount!n. 1.
9-ecute the act!!t +ranser &ppl!cat!on *nde-es.
2.
9-ecute the act!!t K!spla $tatus o +ranser o &ppl!cat!on *nde-es.
3.
9-ecute the act!!t =!ll Kue Kates !n =* Kocuments.
'ote Jou perorm all o the ollo#!n act!!t!es ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. Jou perorm all the ollo#!n act!!t!es !n our test sstem and product!on sstem. 1. 2.
3.
9-ecute the act!!t =!ll the Nsett!n &ccount !n =* Kocuments. 9-ecute the act!!t K!spla $tatus o =!ll!n the Nsett!n &ccount !n =* Kocuments. 9-ecute the act!!t E!rate %ouse )an> &ccounts.
-ctivities and 2usiness (econciliation -fter Migration
&ter the m!rat!on perorm the act!!t!es !n ustom!!n under E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on &ct!!t!es &ter E!rat!on . +hese steps are not absolutel necessar to ensure the data !s both complete and correct and can be perormed as needed and #!th!n the upt!me.
Process 1.
+o complete the m!rat!on o the data to the un!ersal Cournal entr structure and to chec> the m!rat!on !s correct e-ecute the reports aa!n that ou e-ecuted pr!or to the m!rat!on to compare the =* data and compare th!s data #!th the results ou had beore the m!rat!on. +h!s !noles the ollo#!n steps: •
9-ecute the per!od!c deprec!at!on post!n run <#!th proram &$+2000L.
•
•
•
hec> or update term!nat!ons !n our sstem and correct an ou fnd. ,oc> the per!ods !n =!nanc!al &ccount!n and ontroll!n <lan/&ctualL. =or customers #ho are alread us!n accountDbased proftab!l!t anals!s: erorm a delta upload or all o our accountDbased D& Kata$ources or #h!ch ou use the delta method.
•
Ea>e sure that all o the balances carr!ed or#ard to the current fscal ear are transerred.
Kocument the results. 2.
nce the compar!son o the data does not produce an errors ou hae completed the m!rat!on successull. $et the E!rat!on omplete !nd!cator !n ustom!!n under E!rat!on to $& &ccount!n po#ered b $& %&'& E!rat!on omplete E!rat!on $et E!rat!on to omplete .
Preparation for Productive Start Procedure Jou need to perorm the ollo#!n act!!t!es beore ou use the sstem aa!n l!e.
'ote Jou perorm the ollo#!n steps !n our test sstem and product!on sstem. Jou perorm the ollo#!n act!!t!es ! ou are us!n class!c &sset &ccount!n ne# &sset &ccount!n class!c Feneral ,eder &ccount!n or ne# Feneral ,eder &ccount!n or the $& $!mple =!nance addDon 1.0. 1.
Anbloc> all users !n the sstem
2.
pen the per!ods !n =!nanc!al &ccount!n and !n ontroll!n <lan/&ctualL.
=!-ed &ssest
!nstallation "n the course of installing the on$premise edition# the following steps to prepare for the migration are automatically e&ecuted by the system( •
reat!n bac>up tables or the totals tables and !nde- tables !n the Kata K!ct!onar that are be!n done a#a #!th
•
$a!n the totals tables and !nde- tables !n bac>up tables
•
Kelet!n the or!!nal totals tables and !nde- tables
•
reat!n $& %&'& !e#s <#!th the same namesL or the totals !nde- and l!ne !tem tables
•
reat!n the ne# table or the un!ersal Cournal entr
'ou have to migrate the accounting and Controlling data immediately following the installation. To be able you to underta,e this data migration# specific configuration steps are necessary that have been summari-ed in the implementation guide. There are specific migration and chec, programs for the migration that have been included in the SAP eference "%/ in their correct order. All of the migration steps are described in the relevant sections included there. After the migration# you nonetheless have to reconcile the data and perform tests manually.
Post !nstallation
Migration to ew -sset -ccounting "%!&-- "ew$$ K!Nerent m!rat!on u!des are aa!lable and the one releant or ou depends on the source release o our &sset &ccount!nO see the table belo# or th!s.
'ote
&sset &ccount!n pr!or to th!s !s reerred to !n the ollo#!n as Vclass!c &sset &ccount!nV !n order to d!st!nu!sh the t#o. lass!c &sset &ccount!n !s no longer available !n $& &ccount!n po#ered b $& %&'&O th!s appl!es to all sstems. 'e# &sset &ccount!n !s no# aa!lable !n place o class!c &sset &ccount!n.
bus!ness unct!on =*D&& arallel Maluat!on<=*'_&&_&&,,9,_M&,L and #!th the ustom!!n s#!tch act!ated or ne# &sset &ccount!n or •
$& $!mple =!nance addDon 1.0
=!ure 13.4 omponents to )e *nstalled hen E!rat!n to $& $/4%&'& =!nance
*n =!ure 13.4 ou can see the spec!fc component ers!ons that our $& 9 ssD tem #!ll hae !nstalled ater ou complete the $& $/4%&'& =!nance !nstallat!on us!n the $AE.
er;u!s!te %&'& Katabase 9 9%7 )us!ness unct!on 9& G =!n act!ated un m!rat!on prechec> proram based on note &$=*'_E*F_9%9 roram =&F,_$#ap_*EF_ne# th!s step !s to ma>e sure onl =!nanc!al account!n 'e# *EF node !s aa!lable and no class!c F, < =!nance account!n L
$tep 1: rechec> G note 212I306 / 1I3I5I2 $tep 2: lose fnance per!od act!!t!es $tep 3: $creen shot and do#nload >e report or compar!s!on post m!rat!on $tep 4: *nstallat!on < )ac>up o total !e#s tcode upradeL $tep 5 : ustom!!n Gl 6 -ccounting principles1 Ledgers1 valuation areas ompan code ass!nment currenc fscal ear ar!ant open per!ods sett!n real t!me =*D ,eder are defne and account!n pr!nc!ples are ass!ned Maluat!on areas are defned as there m!ht be d!Nerence bet#een currenc!es -sset accounting7 7 3epreciation areas1 and activate E!rat!on node !n preparat!on ne# asset account!n &ss!n compan code to hart o deprec!at!on G under oran!at!on o asset account!n reate deprec!at!on area $pec! transer o & Kefne reconc!l!at!on account G reat!on o techn!cal clear!n account <ernat!e document or d!Nerent account!n pr!nc!ple uant!t update or deprec!at!on area <pt!onalL &ct!ate
SAP Note 211!"!provides the details !or more information# see SAP Note0*12*13. 4SAP Note 0*52062provides
hints to further special e&ceptions
!urther useful notes(
*367+26provides a list of reports amdtransactions replaced in comparison to 8P 8hP1.
elease restr!ct!ons are l!sted !n $& notes 1I77782<1.0L and 2127080<2.0L.
To chec, whether the add$on installation will be possible# verify the currently installed software components in regards to their compatibility with SAP Simple !inance. ead SAP note *317*259*.+: ; 0*+<22590.+: 9compatible add$ons: and compare with the content of database table C=8S>.
Ko#nload tables M9$ and &+07 and as> our $& contact / deelopment anel to arrane or the chec>.
9 must-knows before starting your Simple Finance implementation: The finance add-on replaces the classic Financials applications in your SAP ERP system. In contrast
to accounting in SAP enhancement package 7 for SAP ERP 6.0, Simple Finance comes with a simplified data model. Totals tables and application index tables have been removed and replaced with HANA views with the same
2
3
4
5
technical A fullThis list means can be the found at the bottom ofnames. this article. impact needs to be assessed on your interfaces, your data warehouse, your authorization profiles, and potentially your monitoring tools; Some industry solutions and SAP ERP add-ons are not fully compatible with SAP Simple Finance, like Asset Accounting (FI-AA). Carefully assess compatibility with other components in your landscape; The user experience is likely to change. Assess the impact on the required skill-set in your teams and the potential need to rewrite documentation and/or training materials; Handle the required SP levels for SAP ERP 6.0 EHP7 and for SAP NetWeaver 7.40 with the utmost caution and as described in the administrator’s guide; Before you install the Finance add-on, you must prepare the migration of application data. These
6
7
8 9
•
steps require specific financials application knowledge; Install the finance add-on using the Software Update Manager (SUM). Ensure that you have downloaded the latest version of it from the SAP Service addition,using you must install two SAPMarketplace. HANA LiveIn packages the HANA Lifecycle Manager (HLM); To run the financials applications, you must migrate the application data first. For SPS 02, SPS 03, and SP04, some additional configuration is required. For more information, see Installation of and Migration to the SAP Simple Finance Add-On for SAP Business Suite powered by SAP HANA; Read the Release Information for SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA (note 1925902), and; To conclude, make sure your team reads the Release Scope Information (note 1968568). The following tables were replaced by SAP HANA views with the same names: The line item, totals tables and application index tables of General Ledger Accounting (GLT0, BSIS, BSAS and FAGLFLEXA, FAGLFLEXT, FAGLBSIS, FAGLBSAS)
•
• •
•
The totals tables and application index tables of Accounts Receivable and Accounts Payable (KNC1, KNC3, LFC1, LFC3, BSID, BSIK, BSAD, BSAK) The line item and totals tables of Controlling (COEP for certain COSP valuations and COSS) The material ledgervalue tablestypes, for parallel (MLIT, MLPP, MLPPF, MLCR, MLCD, CKMI1, BSIM) The Asset Accounting tables (ANEK, ANEP, ANEA, ANLP, ANLC)
Account #ased C$PA - Simplification with Simple Finance
created by Sanil handari on Aug 1# 0+*2 *+(6< A%# last modified bySanil handari on Aug 1# 0+*2 *0(+7 P% =ersion * in
Share 1!%
2
+#eet 3 2
Li ke
BDocumentodyStart(dc<7dcc*$+2c6$65c3$a3b2$c tables. This essentially used to map the accounts such as revenue and sales deductions to value fields in costing based CPA. Additionally there were restrictions on the no of value fields in costing based copa with around 0++ fields 9SAP SS Note *+03<3*:. The account based CPA on the other hand uses cost elements to store the same values for various attributes li,e revenue# cost of goods sold# and so on. However# the posting logic in traditional account based CPA was such that cost of goods sold and variances could only be mapped to a single /? Account;Cost element. This was one of the basic reasons why most SAP customers preferred using Costing based CPA over Account based CPA. Another maor challenge with using Costing based CPA was the fre)uent reconciliation issues between CPA and /?. !or eg# typically# the C/S was boo,ed in the /? at the time of utbound delivery and the same value flowed into Costing ased CPA at the time of billing. So if the P/" and illing were far apart in two different posting periods# you typically had challenges in reconciliation of differences. Fith SAP Simple !inance# life has been simplified for the !inance fol,s. SAP mandates the use of Account based CPA with Simple !inance and does away with the limitations of traditional account based CPA providing the same detailed information for Cost of /oods Sold# Production =ariances E invoice )uantities which till now e&isted only with costing based CPA. f course# the costing based CPA can continue to co e&ist with the new Account based CPA
The traditional way of storing the characteristics in CPA irrespective of using Costing based CPA or Account based CPA was to store the data in a row in a data base structure. 8very time the typical CPA reports were run# the system would )uery each data record and than aggregate to arrive at values which had been )ueried. Fith HANA# the data is stored in columns and so only the relevant column is )ueried# This brings in tremendous performance improvement. ne of the ways in which SAP Customers used to tide over the performance related issues with CPA eports was to create secondary inde&es on the way in which reports were done. So this is some thing which is not re)uired with the capabilities of HANA. Fith Simple !inance# comes a new posting capability that allow SAP Customers to report the Cost of /oods Sold at the same level of details as available in Costing based CPA. Typically# the postings on the /? used to happen at the standard price at which the material was valuated and the brea, up of the standard cost was available through Costing basedCPA. Fith Simple !inance comes the capability to lin, the cost components in the standard cost estimate to individual /? Accounts for each cost component. There is no restriction now on the no of accounts and the level of detail can be the same as the one available in cost component structure. The configuration path for the same in Simple !inance environment is( "%/G !inancial Accounting 9New:G/eneral ?edger Accounting 9New:GPeriodic ProcessingG "ntegrationG%aterials %anagementGDefine Accounts for Splitting the cost of goods sold
Another maor reason with SAP Customers preferring Costing based CPA over Account based CPA was the ability of costing CPA to provide the brea, up of Production =ariances# which posted to a based single /? Account. However# with Simple !inance comes the ability to assign a /? Account for each variance category and you can have the same brea, up in Account based CPA on Simple !inance. The re)uired configuration path for the same is(
Here in similar to CS/ split you have to define a Schema and assign a /? Account for each =ariance category.
%ost of SAP customers using costing base CPA choose not to report the )uantity in logistics# but convert them into their own reporting units. This was typically done through an enhancement to record this ,ind of conversion. CPA+++2 was the enhancement which has been used in most customers. However# with Simple !inance# the C8P table has additional )uantity columns which can be used for these ,ind of reporting re)uirements. The "%/ path for the same is( ControllingG/eneral ControllingGAdditional uantitiesG Define additional )uantities
The usage of Account based CPA in Simple !inance ensures that there are no more time consuming painful reconciliation re)uired to be done anymore. Additionally# the customers get the same ,ind of reporting capabilities hitherto seen with costing based CPA ma,ing life simpler for !inance users.
