Professional Documents
Culture Documents
FISDIntegrationI|SCN
GettingStarted Newsletters
Hi,Guest
LogOn
JoinUs
Store
SearchtheCommunity
Products
Services&Support
AboutSCN
Downloads
Industries
Training&Education
Partnership
DeveloperCenter
Activity
LinesofBusiness
UniversityAlliances
Events&Webinars
Innovation
Browse
FISDIntegrationI
Communications
Actions
Version6
createdbySowmyaTiwaryonSep26,201310:29AM,lastmodifiedbySowmyaTiwaryonMar21,201411:50AM
Share
Tweet
Like
24
ThisseriesofdocumentsforFISDintegrationisdividedinto4parts.Thisdocumentisthesecondpartoftheseries.
AddinglinksforotherpartsbeforeIstartwiththecontent.
EventhoughthedocumenttitlesaysFISDIntegrationI,itisthesecondpartbecausepartIwastheprerequisites
requiredfortheintegration.
PartI: PrerequisitesforFISDIntegration
PartIII: FISDIntegrationII
PartIV: FISDIntegrationIII
AutomaticAccountDetermination
Theaccountingentrieswithrespecttothebillingwillgenerallyresultin
DebitCustomeraccount
DebitFreightoutaccount
CreditRevenueaccount
CreditExciseDutyPayableaccount
CreditSalesTaxPayableaccount
Hence, primarily, one side of the account is a Customer and the other is a revenue account. The customer
accountgetspickedupfromthecustomermasterdataandtherevenueaccountisconfiguredbasedoncertain
inputs so that correct account is hit during FI posting. This automatic account determination is configured not
onlyforrevenue,butalso,otherelementslikeFreight,surcharges,salesdeductionsetc.
Theaccountdeterminationcanbedonetobebasedonthefollowingcriteria:
Application
ConditionType
ChartofAccountsofCompanyCode
SalesOrganization
CustomerAccountAssignmentGroup
MaterialAccountAssignmentGroup
AccountKey
Note:Theabovementionedfieldsarestandardfieldsincludedbydefault.Morefieldscanbeaddedascriteria.
ConfigurationSteps
The configuration steps required for this activity can be found by following path SPRO > IMG > Sales and
Distribution>BasicFunctions>AccountAssignment/Costing>RevenueAccountDetermination
Asseeninthescreenshotabove,thereare6configurationsteps.
http://scn.sap.com/docs/DOC46903
1/15
09/08/2015
FISDIntegrationI|SCN
CheckMasterDataRelevantForAccountAssignment
Thefirststepissettingupthemasterdatarelevantforaccountassignment.ThemenupathisSPRO>IMG>
SalesandDistribution>BasicFunctions>AccountAssignment/Costing>RevenueAccountDetermination>
CheckMasterDataRelevantForAccountAssignment
There are two activities to be done in this step material account assignment groups and customer account
assignmentgroups.
Thefirstactivityismaterialaccountassignmentgroupsmaintenance.Fromthescreen,doubleclickonMaterials:
AccountAssignmentGroups.Thescreenformaintainingmaterialgroupswillappear.
UsetheNewEntriesbuttontocreatenewgroups.Therearedifferentmaterialgroupscreatedasinthescreen
above which ensures that, for example, all the trading goods (Group 01) can be posted to different accounts
thanthatofalltheservices(Group20).
Asalreadyseenbefore,thesematerialgroupsareassignedtomaterialsintheviewSales:SalesOrg.Data2of
the material master. The system automatically proposes the account assignment group for the material in the
Salesdocumentsfromthematerialmaster.
The second activity in this step is customer account assignment groups maintenance. From the screen, double
clickonCustomers:AccountAssignmentGroups.Thescreenformaintainingcustomergroupswillappear.
UsetheNewEntriesbuttontocreatenewgroups.Therearedifferentcustomergroupscreatedasinthescreen
above which ensures that, for example, all the domestic revenues (Group 01) can be posted to different
accountsthanthatofalltheforeignrevenues(Group02)ortheaffiliatedcompaniesrevenue(Group03).
As already seen before, these customer groups are assigned to customers in the tab Billing Documents of the
Sales Area data in the customer master. The system automatically proposes the account assignment group for
thecustomerintheSalesorBillingdocumentsfromthecustomermaster.
DefineDependenciesofRevenueAccountDetermination
The next step is defining the dependencies for revenue account determination defining fields as well as
http://scn.sap.com/docs/DOC46903
2/15
09/08/2015
FISDIntegrationI|SCN
condition tables. The menu path is SPRO > IMG > Sales and Distribution > Basic Functions > Account
Assignment/Costing > Revenue Account Determination > Define Dependencies Of Revenue Account
Determination
Asalreadymentioned,thepurposeofsettingupaccountdeterminationistobeabletodifferentiateaccountsfor
posting according to certain criteria like customer account assignment group, account key, material account
assignment group etc. Hence, the first activity here in this step is to decide which all criteria will be used for
suchdifferentiation.Thefieldcatalogcontainsfieldsthatcanbeselectedwhenwecreateormaintainacondition
Table. These decided criteria are to be added by double clicking on the Field Catalog: Allowed fields for the
tablesoption.
As seen in the screen shot above, the some of the required criteria are already present. If new ones are to be
added, click on new entries and press F4. A list of all the fields in the tables that can be added as criteria is
listedasshownbelow.
As shown above, if we want to add Payment cards: Card type as a criteria, double click on the entry and then
presssave.Asseenbelow,thiscriterionhasbeenaddedtothealreadyexistinglistofcriteria.
Oncethefieldshavebeenselected,thesefieldshavetobeaddedtoconditiontables.Therecanbemanytables,
eachwithdifferentcombinationofcriteriathatwillbeusedforaccountdetermination.Theexistingtablescanbe
http://scn.sap.com/docs/DOC46903
3/15
09/08/2015
FISDIntegrationI|SCN
displayedusingAccountDetermination:DisplayTablesoption.
Enterthetablenumberforwhichweneedtoseethetabledetailsandpressenter.
As seen in the screen above, table 9 uses Sales Organization, Distribution Channel and Division as criteria for
accountdetermination.Theleftpaneshowsthefieldsselectedascriteriaforthistableandtherightpaneshows
thefieldcatalogi.e.thefieldsavailablefromwhichthecriteriacanbeaddedtothetable.
The system already contains standard tables like the one shown above. Most of the times, these standard
condition tables are sufficient. However, we can also create custom condition tables for specific requirements.
Thesecustomtablescanrangefrom501to999.Someofthestandardtablesare
Table001Customergroup/Materialgroup/Accountingkey
Table002Customergroup/Accountingkey
Table003Materialgroup/Accountingkey
Table004General
Table005Accountingkey
Tocreateanewtable,doubleclickonAccountDetermination:CreateTablesoption.Here,acustomtable501is
beingcreatedwiththePaymentCardtypefieldascriterion.
Entertablenumber501andpressenter.Ifthetableistobecopiedfromanotherexistingconditiontablewecan
entertheexistingtablenumberinthefieldbelowthenewtablenumber.
SelectthefieldpaymentcardtypeandchoosetheSelectfieldbutton.
http://scn.sap.com/docs/DOC46903
4/15
09/08/2015
FISDIntegrationI|SCN
As seen, now this field has been added to the table as criterion as it can be seen in the left pane. The
description of the table can be changed using the highlighted button in the screen shot. Add all the required
fieldsandpresssave.Thenewconditiontablehasbeencreated.
Note : The Field Catalog table is crossclient. Therefore, any changes done to this table will have effects in all
clientsonaserver.
DefineAccessSequencesandAccountDeterminationTypes
Thenextstepisdefiningaccountdeterminationtypesandaccesssequences.ThemenupathisSPRO>IMG>
SalesandDistribution>BasicFunctions>AccountAssignment/Costing>RevenueAccountDetermination>
DefineAccessSequencesAndAccountDeterminationTypes
The first activity, Maintain access sequences for account determination is used to setup access sequences.
Accesssequencesstoreinformationaboutwhichconditiontableswillbeaccessedforaccountdetermination,the
sequenceinwhichthesetableswillbeaccessedandthefieldcontentsoftheseconditiontables.Doubleclickon
theoption.
http://scn.sap.com/docs/DOC46903
5/15
09/08/2015
FISDIntegrationI|SCN
As seen, there are two standard access sequences defined in the system KOFI and KOFR. To create new
access sequences use the new entries button. To view an already existing one, click on the entry and double
clickontheAccessesfolderashighlightedonthelefthandside.
The above screen shows the condition tables and the sequence in which they are accessed in the access
sequence KOFI. The No. column gives the order in which the tables are accessed i.e. the one with the lowest
number is accessed first. As shown in the above screen shot, system will access table 953 first during
determination procedure as that is first in sequence. If system is able to find out necessary information in this
table it will not access table 496 but otherwise it will access table 496 next. Usually, the sequencing of the
tablesisconfiguredsuchthat,themorespecifictablesareaccessedfirstfortheinformationandthentheless
specificonesfollow.TheTabcolumncontainstheconditiontablenumberandtheDescriptionfieldcontainsthe
tabledescription.Toseethefieldscontainedintheconditiontable,clickontherespectiverowanddoubleclick
ontheFieldsfolderashighlightedonthelefthandside.Toaddnewtablestotheaccesssequenceusethenew
entriesbutton,enterthevaluesintheNo.andTabcolumnandsave.
Thescreenshotaboveshowsthefieldsintable496ConditionType/AccountKey.
http://scn.sap.com/docs/DOC46903
6/15
09/08/2015
FISDIntegrationI|SCN
Thescreenshotaboveshowsthatthetable501PaymentCardTypehasbeenaddedtoaccesssequenceKOFI.
As seen, there is a column called Requirement. A requirement, simply put, is a routine or a small program,
which one can specify as a precondition to decide that the access sequence is to be activated if that condition
fulfilled.Say,forinstance,anaccessisapplicableonlyforexportbusiness,then,arequirement,say8isused.
This requirement number checks if the order is of export business. If yes, then only the access is read.
Otherwiseitisnot.So,itsavesalotoftimeforthesystem,improvingtheresponsetime.Therequirementsfor
thevariousapplicationareassuchaspricing,materialdetermination,accountdeterminationetc.aremaintained
usingtransactioncodeVOFM.Oncethecreated,theycanbeassignedasrequiredtoaccesssequence's/pricing
procedures,etc.
Note:TheAccessSequencestableiscrossclient.Therefore,anychangesdonetoaccesssequenceswillhave
effectsinallclientsonaserver.
The second activity in this step is Define account determination types. The account determination type is used
for defining the control data for access sequence and the validity date. Double click on this option from the
menu.
As seen in the screen shot, in this step, condition types are defined and then access sequences assigned to
them. It is to be noted that these condition types are different from the condition types used in pricing
proceduresasdiscussedintheprerequisitessection.Theseconditiontypesareusedinaccountdetermination
procedure.TherearetwostandardconditiontypesinthesystemKOFI(foraccountdeterminationwithoutCO)
andKOFK(foraccountdeterminationwithCO).
Note : Custom condition types and access sequences can be defined, but, it is recommended that these start
withZ.
42536Views
Tasks:integrationTags:sap,billing,fico,reconciliation,financials,fisd
AverageUserRating
(40ratings)
Share
Tweet
2 Like
24
67Comments
RanuEugeneSep26,201311:22AM
Hi SowmyaTiwary,
NiceDoc.
Veryuseful.
Thanksforsharing.
Keepupthegoodwork.
BestofLuck.
Regards
Eugene
Like(2)
SampatKumkarSep26,201311:30AM
Hi
ItsreallygooddocsandusefulforclearingtheintegrationofFISD
thanksfornicedocument...
http://scn.sap.com/docs/DOC46903
7/15
09/08/2015
FISDIntegrationI|SCN
Regards
Sampath
Like(1)
pankajlabhasetwarSep26,20131:58PM
Hi,
Verynicedocumentandnicepresentationtoo.
Keepitup.
Regards,
Pankaj
Like(1)
RaviSankarVennaSep26,20132:00PM
GoodjobSowmya,keepitup.
BestRegards,
Ravi
Like(2)
DHANAPRABUMSep26,20133:31PM
hisowmya
grtworkkeepgoing..allthebest..
Regards,
Dhanaprabu
Like(1)
SumanSardarSep26,20134:04PM
Hi SowmyadeepthiKVN,
Ireallyappreciateyourefforttosharesuchnicedocument.
AlsoIthinkyouhaveplanforPartII.
Keepitup.
Waitingforthenextdoc.
Thanks,
Suman$
Like(1)
NishanDevSSep26,20135:21PM
GreatworkSowymadeepth:
ItrequirelotofpatienceandlotofpassionforSAPtomakethiskindofcompletedocument,andit
seemsyouhavegreatpassionforSAP,thanksforsharingmoretocomefromyourlibrary.
Thanksagainforsharing,
Nishan
Like(1)
AIMMSep27,20136:48AM
Hi
Sowmyadeepthi.....
GoodDocument...........Greatwork..........Keepitup.
Thanks&Regards,
Aish.
Like(1)
NareshKrishnamoorthySep27,20136:58AM
Usefulone...Thanks.
BestRegards,
NareshK.
Like(1)
krishSSep27,20138:35AM
Nicework..keeptopostsomeotherdocumentsalso..thankyousomuch.
Like(1)
SrinivasSalpalaSep27,20139:00AM
Sowmya,
Goodwork!!Integrationpartisalwaysakeyareatolearn.Keepupthebesteffort..
http://scn.sap.com/docs/DOC46903
8/15
09/08/2015
FISDIntegrationI|SCN
BR,SrinivasSalpala
Like(1)
AkberhusainAjmeriSep27,201311:48AM
GoodJob
Thanksforsharing
Like(1)
SudhirKrishnaKumarSinghSep27,201311:53AM
nicedocument.....
allthebest,
Thanks
SudhirKrishnaKumarSingh
Like(1)
VenkateshBSep30,20133:30PM
Nicedocument.
Like(1)
ErwinLeitnerSep30,20133:55PM
Hello,
ManyThanksforsharingverygoodinformation.
allthebestErwin
Like(1)
MuthukumareshanvijayanOct4,20134:56PM
Hi,
NiceDoc.
Veryuseful.
Thanksforsharing..
Thanks
Muthu
Like(1)
ShrikantSapaligaOct4,20136:50PM
Hi,
Thanks.Veryusefuldoc.
regards
ShrikantSapaliga
Like(2)
SrinuSOct15,20132:40PM
GoodjobSowmya,Veryusefuldocumentandnicelypresented.
Keeponsharingthiskindofusefuldocument.
Thanksforsharing.
Srinu.
Like(1)
JandovalNascimentoSilvaJuniorOct15,20132:49PM
Hi SowmyadeepthiKVN,
Thanksforshareyourknowledgewithus.
Regrads.
JandovalNascimento
Like(1)
NishuShahOct15,20132:55PM
Keepupthespirit
Thanks
Like(1)
SatyaYenumulaOct18,20137:45AM
http://scn.sap.com/docs/DOC46903
9/15
09/08/2015
FISDIntegrationI|SCN
HiSowmya
Nicepresentation..Veryuseful...
Thanks
Satya
Like(1)
prasannadashOct18,20138:20AM(inresponsetoSatyaYenumula)
DearSowmya,
Manymanythanksforsharingvaluableknowledgewithus.Pleasesharemoredocument.
Regards
Prasanna
Like(1)
sanjeevSinghOct19,20132:50PM
GoodJob
Thanksforsharing
Like(1)
rohitsinghOct23,20135:40PM
HiSowmya,
it'savaluableinformationtounderstandingtheconceptofFISDIntergation.
Iappreciateyourjob
Thanks
Like(1)
GowthaamiMogantiOct24,20133:14PM
Hisowmya,
Thankuforsharingtheinformation.
Goodwork.
Like(1)
ShokatAliOct25,20139:50AM
Veryuseful.
Thanksforsharing.
Like(1)
Mariks.Oct25,20132:59PM
Thanksforsharingvaluableinformation..
Like(1)
SAQMDOct28,20136:01AM
DearSowmya,
Thanksamillion.....
Regards,
Like(1)
EmilioRoldanCosanoOct29,20134:23PM
Hello,
Veryuseful.
Thanksforsharing
Like(1)
RamanjaneyuluKorrapatiOct30,20136:53AM
Goodjob.Usefuldoc.Thanksforsharing
Like(1)
LakshmiSamaOct30,20139:44AM
HiSowmya,
NiceDoc
Regards,
LakshmiS
http://scn.sap.com/docs/DOC46903
10/15
09/08/2015
FISDIntegrationI|SCN
Like(1)
GauravTibrewalOct31,20132:54PM
HiSowmya,
Thanksforsharingsuchanicedocumentwithdetailedexplanation.Veryuseful.
Regards,
Gaurav
Like(1)
SrideviBNov4,20133:14PM
Thanksforsharingverygooddocument...
Regards,
Sridevi
Like(1)
BalajiMNov5,201311:03AM
GoodJobSowmya...
Like(1)
RamaChandraNov6,20131:23PM
Thanksforsharingforgooddocument..............
Like(1)
VenkateswarluRavulaNov7,201310:37AM
Greatjob!.Thankyouforsharingsuchanicedoc.
Like(1)
SwapnoneelMukherjeeNov12,20135:27AM
Greatjob..verypreciseandtothepointdocument.Thanks
Like(1)
KaranamMadhavaRajNov15,20137:14AM
Goodjob.VeryUsefulDoc.Thanksforsharing.
MadhavaRaj
Like(1)
MuraliBabuNallamothuNov17,20133:37AM
HiDeepthi,
ImjealousaboutyourSDknowledge
areyouaSDconsultantorFI
Thanksforsharingyourintegartionknowledge.
Rgds
Murali.N
Like(1)
DanielCarvalhoNov18,201312:04PM
Verygoodtips!
IwouldalsoaddthattheAccountDetermination(VKOAtransaction)canalsobefoundontheFIPath,
underIMG>FinancialAccounting>GeneralLedgerAccounting>BusinessTransactions>
Integration>SalesandDistribution>PrepareRevenueAccountDetermination.
Regards,
Daniel
Like(1)
pulaksamantarayNov18,20134:13PM
Nicedocumentsowmaya,Thanksforsharing.
Regards
Pulak
Like(1)
MuthukumareshanvijayanNov19,20137:23AM
Hi,
http://scn.sap.com/docs/DOC46903
11/15
09/08/2015
FISDIntegrationI|SCN
Verynicedocumentandnicepresentationtoo.
Keepitup.
Regards,
Muthu
Like(1)
pranavkumarNov21,20136:42AM
NiceoneFISDintegration.
thanksalott.
Kindregards
PranavKr.Gupta
SAPFICOConsultant
Like(1)
ShankarKazaNov25,201312:26PM
NiceDocumentSoumya...Goodeffort..Keepitup
Regards
Shankar
Like(1)
DavidElviraNov29,20133:58PM
Gooddocument
InmycompanyI'vetriedtoavoidcomplication,sowehaveonly3tablesofconditionswithdifferent
degreesofcolumnsonit.Itrytoaddasmuchaspossibleontheglobaltablesandonlyusethe
preciseonesforprecisecases.
However,I'veseenalotofcompanieswhereallthecustomizingisontheprecisetables.Thatmeans
thatwhencreatingaglobalcondition,youneedyoumodifyalotofrowswichistimeconsumingand
sourceoferrors.
So,keepitsimple.
Like(1)
RAJAGOPALREDDYVEERIAGARIDec19,201310:46AM
Thanksforsharingvaluableknowledge,Itisveryclear&simple.pleasesahrethepartIIaswell.
Regards
Raj.
Like(1)
JoshuaMuthyalaMar5,20143:26PM
Hello,
Thankyouforthebrilliantexplanation.
Ifollowedeverythinguntilthelastpart,WhereKOFI,KOFKcomesintopicture.Idounderstandthe
purposeoftheseconditiontypes,butIamveryconfusedwiththewaythesearemappedtoSD
conditionTypes.
Ithought,theSDPricingPrcodure+conditiontypesismappedtoAccountKey,whichinturnis
mappedtotheG/Laccount.SohowdoesKOFI/KoFKcomeintopicture.
Doesitmeanthat,thisisasecondarysegregationoncetheflowreachesFI?
SDPricingProcedure+conditionTypemappedtoAccountKey.AccountKey+salesorg+KOFIor
KOFKdeterminesthefinalG/LaccountIsthislineofthoughtcorrect?
Anyhelpisappreciated.
Thankyou
Regards,
Joshua
Like(0)
DavidElviraMar5,20144:09PM(inresponsetoJoshuaMuthyala)
Hello
KOFI/KOFKallowsthedeterminationoftheP/LaccountandProvisionaccountassociated
toaconbinationofseveralparameters.Theseparameterscanbetheaccountkey,thesales
org,charofaccounts,etc.KOFImeansFIAccountdeterminationandKOFKCOaccount
determination.
These"conditiontypes"areonlyusedtodeterminetheparametersusedonVKOA
transaction.TheseparametershelpdetermingtheGLaccountwithmoreorlesscomplexity.
KOFI/KOFKhavenothingtodowiththeconditiontypeslikePR00usedonthedocument
itselftodetermineprices.
David
Like(1)
JoshuaMuthyalaMar5,20144:28PM(inresponsetoDavidElvira)
DearDavid,
Thankyouforyourreply.
http://scn.sap.com/docs/DOC46903
12/15
09/08/2015
FISDIntegrationI|SCN
Basically,IamtryingtodeterminetheconceptassociateswithSDFlowintoFI.Or
rather,whatisthebasisonwhichanSDTransactionflows,eventuallytoaG/L
account.
WhatIunderstandisthat,thepricingprocedureandSDconditionType,determine
theAccountKey.ThisaccountkeyinturnisONEofthemanyparameters,that
alongwithKOFI/KOFK,leadtotheeventualG/LAccount.
Isthisright?
Regards,
Joshua
Like(0)
DavidElviraMar5,20144:37PM(inresponsetoJoshuaMuthyala)
That'sright!
Like(0)
JoshuaMuthyalaMar5,20144:46PM(inresponsetoDavidElvira)
ThankyouDavid.
Regards,
Joshua
Like(0)
AMOLMARATHEMar26,20148:11AM
Hello,
exceptionaldocument.thankyouforsharingit.
regards,
amol
Like(1)
SowmyaTiwaryMar26,201412:10PM(inresponsetoAMOLMARATHE)
ThankyouAmol
Like(0)
BalajiMApr2,201410:45AM
HiSowmyaDeepthi,
Itsgooddocumentation,ihopeucanpostlotofnewtopicsinFICOareaslikeNewGL,Reportpainter
etc...
ThanksonceagainforyourvaluableposttoSCN.
Regards,
M.Balaji
Like(1)
SowmyaTiwaryApr2,20142:14PM(inresponsetoBalajiM)
ThanksBalaji.Iwilltry.
Like(0)
pranavkumarApr2,20145:54PM(inresponsetoSowmyaTiwary)
HiSowmya,
Ryt,IhopenexttimeyouwillprovideNEWGLconceptalongwithDocument
SplittingStepbystep.andReportPainterforforProfitCenteraswellCostCenter
aswellProductCosting.
Advancethanks.
PranavKr.Gupta
SAPFICOConsultant
Like(1)
HansrajBansalApr22,20145:22PM
exceptionalandexcellentsharing.....
Like(1)
SowmyaTiwaryApr23,20147:33AM(inresponsetoHansrajBansal)
ThankyouHansraj
Like(0)
Jul23,20144:17PM
Thankyouverymuchforthedocument.Thisisareallywellstructuredandnicedocument.
http://scn.sap.com/docs/DOC46903
13/15
09/08/2015
FISDIntegrationI|SCN
Like(0)
JandovalNascimentoSilvaJuniorJul24,20141:29PM
Sowmya
Thankyoutosharethisdocumentwithus.Thisisveryuseful.
Like(0)
BasappaAllannavarAug22,201411:14AM
Hello,
Itsveryusefuldocument,thankuforsharing.
Regards,
Basappa
Like(0)
Bose.Aug24,20145:41PM
HiSowmya,
YourbloggivesaverygoodideaonFISDintegration.HoweverIfeelsomecontinuityismissingon
Pricingproceduretobilling!!
AccountingKeyspecifiedinconditiontypelinkedtoPricingprocedure(hereIamnotunderstanding
clearly,whathappensafterPricingprocedure?bysearchinginthewebireadinsomeposts,as
PricingprocedurewillbeassignedtoBillingdoctype,customer,SalesOrg)...
Canyoupleasegivesomedetailonthisinyourwayofexplanation(hopethatgoesaeasy
understanding),howpricingprocedureisdeterminedbysystemwhenbillingdocumentisprocessed
PS:Ithoughttopostthisinthediscussions,butifeltitsclosetoyourblogpostsopostinghere
Thanks,
Bose
Like(0)
RamMandalaneniAug24,20146:07PM
ReallyGodjobsowmyaiamstudyurblog
Itsveryusefuldocument,thankuforsharing
Regards,
Ram
Like(0)
DeclanBolgerAug27,20144:06PM
VeryUseful.Thanksandgreatwork.
Like(0)
MichaelTurnerAug29,20147:34AM
Gooddocumentinfo.Thanks.
Like(0)
bhawnasajwaniSep13,20148:26PM
HiSowmya,
Quiteastructuredblog
AverygoodandmustreadforFIconsultants.
Thanksforsharingtheknowledge.
Regards,
Bhawna
Like(0)
PankajBholeJul23,201511:47AM
thanksSowmyaforSharing!NicelyExplained
Regards
Pankajb
Like(0)
SiteIndex
Privacy
ContactUs
TermsofUse
http://scn.sap.com/docs/DOC46903
SAPHelpPortal
LegalDisclosure
Copyright
FollowSCN
14/15
09/08/2015
http://scn.sap.com/docs/DOC46903
FISDIntegrationI|SCN
15/15