fi-sd integration - i _ scn.pdf
TRANSCRIPT
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 1/17
Getting Started Newsletters Store
Products Services & Support About SCN Downloads
Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join UsHi, Guest Search the Community
Activity Communications Actions
Browse
6 Tweet
created by Sowmya Tiwary on 26Sep2013 10:29, last modified by Sowmya Tiwary on 21Mar2014 11:50
This series of documents for FISD integration is divided into 4 parts. This document is the second part of the series.Adding links for other parts before I start with the content. Even though the document title says FISD Integration I, it is the second part because part I was the prerequisitesrequired for the integration. PartI : Prerequisites for FISD IntegrationPartIII : FISD Integration IIPartIV : FISD Integration III
Automatic Account Determination
The accounting entries with respect to the billing will generally result in
Debit Customer account
Debit Freightout account
Credit Revenue account
Credit Excise Duty Payable account
Credit Sales Tax Payable account
Hence, primarily, one side of the account is a Customer and the other is a revenue account. The customeraccount gets picked up from the customer master data and the revenue account is configured based on certaininputs so that correct account is hit during FI posting. This automatic account determination is configured notonly for revenue, but also, other elements like Freight, surcharges, sales deductions etc.The account determination can be done to be based on the following criteria:
Application
Condition Type
Chart of Accounts of Company Code
Sales Organization
Customer Account Assignment Group
Material Account Assignment Group
Account Key
Note: The above mentioned fields are standard fields included by default. More fields can be added as criteria.
Configuration Steps
The configuration steps required for this activity can be found by following path SPRO > IMG > Sales andDistribution > Basic Functions > Account Assignment/Costing > Revenue Account Determination
FISD Integration I
Share
Version 6
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 2/17
As seen in the screen shot above, there are 6 configuration steps.
Check Master Data Relevant For Account Assignment
The first step is setting up the master data relevant for account assignment. The menu path is SPRO > IMG >Sales and Distribution > Basic Functions > Account Assignment/Costing > Revenue Account Determination >Check Master Data Relevant For Account Assignment
There are two activities to be done in this step – material account assignment groups and customer accountassignment groups.
The first activity is material account assignment groups maintenance. From the screen, double click on Materials:Account Assignment Groups. The screen for maintaining material groups will appear.
Use the New Entries button to create new groups. There are different material groups created as in the screenabove which ensures that, for example, all the trading goods (Group 01) can be posted to different accountsthan that of all the services (Group 20).
As already seen before, these material groups are assigned to materials in the view Sales: Sales Org. Data 2 ofthe material master. The system automatically proposes the account assignment group for the material in theSales documents from the material master.
The second activity in this step is customer account assignment groups maintenance. From the screen, doubleclick on Customers: Account Assignment Groups. The screen for maintaining customer groups will appear.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 3/17
Use the New Entries button to create new groups. There are different customer groups created as in the screenabove which ensures that, for example, all the domestic revenues (Group 01) can be posted to differentaccounts than that of all the foreign revenues (Group 02) or the affiliated companies’ revenue (Group 03).
As already seen before, these customer groups are assigned to customers in the tab Billing Documents of theSales Area data in the customer master. The system automatically proposes the account assignment group forthe customer in the Sales or Billing documents from the customer master.
Define Dependencies of Revenue Account Determination
The next step is defining the dependencies for revenue account determination – defining fields as well ascondition tables. The menu path is SPRO > IMG > Sales and Distribution > Basic Functions > AccountAssignment/Costing > Revenue Account Determination > Define Dependencies Of Revenue AccountDetermination
As already mentioned, the purpose of setting up account determination is to be able to differentiate accounts forposting according to certain criteria like customer account assignment group, account key, material accountassignment group etc. Hence, the first activity here in this step is to decide which all criteria will be used forsuch differentiation. The field catalog contains fields that can be selected when we create or maintain a conditionTable. These decided criteria are to be added by double clicking on the Field Catalog: Allowed fields for thetables option.
As seen in the screen shot above, the some of the required criteria are already present. If new ones are to beadded, click on new entries and press F4. A list of all the fields in the tables that can be added as criteria islisted as shown below.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 4/17
As shown above, if we want to add Payment cards: Card type as a criteria, double click on the entry and thenpress save. As seen below, this criterion has been added to the already existing list of criteria.
Once the fields have been selected, these fields have to be added to condition tables. There can be many tables,each with different combination of criteria that will be used for account determination. The existing tables can bedisplayed using Account Determination: Display Tables option.
Enter the table number for which we need to see the table details and press enter.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 5/17
As seen in the screen above, table 9 uses Sales Organization, Distribution Channel and Division as criteria foraccount determination. The left pane shows the fields selected as criteria for this table and the right pane showsthe field catalog i.e. the fields available from which the criteria can be added to the table.
The system already contains standard tables like the one shown above. Most of the times, these standardcondition tables are sufficient. However, we can also create custom condition tables for specific requirements.These custom tables can range from 501 to 999. Some of the standard tables are
Table 001 Customer group/ Material group/ Accounting key
Table 002 Customer group/ Accounting key
Table 003 Material group/ Accounting key
Table 004 General
Table 005 Accounting key
To create a new table, double click on Account Determination: Create Tables option. Here, a custom table 501 isbeing created with the Payment Card type field as criterion.
Enter table number 501 and press enter. If the table is to be copied from another existing condition table we canenter the existing table number in the field below the new table number.
Select the field payment card type and choose the Select field button.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 6/17
As seen, now this field has been added to the table as criterion as it can be seen in the left pane. Thedescription of the table can be changed using the highlighted button in the screen shot. Add all the requiredfields and press save. The new condition table has been created.
Note : The Field Catalog table is crossclient. Therefore, any changes done to this table will have effects in allclients on a server.
Define Access Sequences and Account Determination Types
The next step is defining account determination types and access sequences. The menu path is SPRO > IMG >Sales and Distribution > Basic Functions > Account Assignment/Costing > Revenue Account Determination >Define Access Sequences And Account Determination Types
The first activity, Maintain access sequences for account determination is used to setup access sequences.Access sequences store information about which condition tables will be accessed for account determination, thesequence in which these tables will be accessed and the field contents of these condition tables. Double click onthe option.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 7/17
As seen, there are two standard access sequences defined in the system – KOFI and KOFR. To create newaccess sequences use the new entries button. To view an already existing one, click on the entry and doubleclick on the Accesses folder as highlighted on the left hand side.
The above screen shows the condition tables and the sequence in which they are accessed in the accesssequence KOFI. The No. column gives the order in which the tables are accessed i.e. the one with the lowestnumber is accessed first. As shown in the above screen shot, system will access table 953 first duringdetermination procedure as that is first in sequence. If system is able to find out necessary information in thistable it will not access table 496 but otherwise it will access table 496 next. Usually, the sequencing of thetables is configured such that, the more specific tables are accessed first for the information and then the lessspecific ones follow. The Tab column contains the condition table number and the Description field contains thetable description. To see the fields contained in the condition table, click on the respective row and double clickon the Fields folder as highlighted on the left hand side. To add new tables to the access sequence use the newentries button, enter the values in the No. and Tab column and save.
The screen shot above shows the fields in table 496 – Condition Type/Account Key.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 8/17
Average User Rating
(41 ratings)
Tweet6
The screen shot above shows that the table 501 – Payment Card Type has been added to access sequence KOFI.
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 conditionfulfilled. Say, for instance, an access is applicable only for export business, then, a requirement, say 8 is used.This requirement number checks if the order is of export business. If yes, then only the access is read.Otherwise it is not. So, it saves a lot of time for the system, improving the response time. The requirements forthe various application areas such as pricing, material determination, account determination etc. are maintainedusing transaction code VOFM. Once the created, they can be assigned as required to access sequence's / pricingprocedures, etc.
Note : The Access Sequences table is crossclient. Therefore, any changes done to access sequences will haveeffects in all clients on a server.
The second activity in this step is Define account determination types. The account determination type is usedfor defining the control data for access sequence and the validity date. Double click on this option from themenu.
As seen in the screen shot, in this step, condition types are defined and then access sequences assigned tothem. It is to be noted that these condition types are different from the condition types used in pricingprocedures as discussed in the prerequisites section. These condition types are used in account determinationprocedure. There are two standard condition types in the system – KOFI (for account determination without CO)and KOFK (for account determination with CO).
Note : Custom condition types and access sequences can be defined, but, it is recommended that these startwith Z.
49972 Views Tasks: integration Tags: sap, billing, fico, reconciliation, financials, fisd
Share
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 9/17
67 Comments
Like (2)
Ranu Eugene 26Sep2013 11:22
Hi Sowmya Tiwary,Nice Doc.Very useful.Thanks for sharing. Keep up the good work. Best of Luck. RegardsEugene
Like (1)
Sampat Kumkar 26Sep2013 11:30
Hi Its really good docs and useful for clearing the integration of FISD thanks for nice document... RegardsSampath
Like (1)
pankaj labhasetwar 26Sep2013 13:58
Hi, Very nice document and nice presentation too.Keep it up. Regards, Pankaj
Like (2)
Ravi Sankar Venna 26Sep2013 14:00
Good job Sowmya, keep it up. Best Regards,Ravi
Like (1)
DHANAPRABU M 26Sep2013 15:31
hi sowmya grt work keep going..all the best.. Regards,Dhanaprabu
Like (1)
Suman Sardar 26Sep2013 16:04
Hi Sowmyadeepthi KVN , I really appreciate your effort to share such nice document.Also I think you have plan for Part II.Keep it up. Waiting for the next doc. Thanks,Suman$
Nishan Dev S 26Sep2013 17:21
Great work Sowymadeepth: It require lot of patience and lot of passion for SAP to make this kind of complete document, and itseems you have great passion for SAP, thanks for sharing more to come from your library.
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 10/17
Like (1)
Thanks again for sharing,Nishan
Like (1)
AIM M 27Sep2013 06:48
Hi
Sowmyadeepthi..... Good Document...........Great work..........Keep it up. Thanks & Regards, Aish.
Like (1)
Naresh Krishnamoorthy 27Sep2013 06:58
Useful one...Thanks. Best Regards,Naresh K.
Like (1)
krish S 27Sep2013 08:35
Nice work.. keep to post some other documents also.. thank you so much.
Like (1)
Srinivas Salpala 27Sep2013 09:00
Sowmya, Good work!! Integration part is always a key area to learn. Keep up the best effort.. BR, Srinivas Salpala
Like (1)
Akberhusain Ajmeri 27Sep2013 11:48
Good Job Thanks for sharing
Like (1)
Sudhir Krishna Kumar Singh 27Sep2013 11:53
nice document .....all the best, ThanksSudhir Krishna Kumar Singh
Like (1)
Venkatesh B 30Sep2013 15:30
Nice document.
Like (1)
Erwin Leitner 30Sep2013 15:55
Hello, Many Thanks for sharing very good information. all the best Erwin
Muthukumareshan vijayan 04Oct2013 16:56
Hi, Nice Doc.Very useful.Thanks for sharing.. Thanks
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 11/17
Like (1)
Muthu
Like (2)
Shrikant Sapaliga 04Oct2013 18:50
Hi, Thanks. Very useful doc. regardsShrikant Sapaliga
Like (1)
Srinu S 15Oct2013 14:40
Good job Sowmya,Very useful document and nicely presented. Keep on sharing this kind of useful document. Thanks for sharing. Srinu.
Like (1)
Jandoval Nascimento Silva Junior 15Oct2013 14:49
Hi Sowmyadeepthi KVN, Thanks for share your knowledge with us. Regrads. Jandoval Nascimento
Like (1)
Nishu Shah 15Oct2013 14:55
Keep up the spirit Thanks
Like (1)
Satya Yenumula 18Oct2013 07:45
Hi Sowmya Nice presentation.. Very useful... ThanksSatya
Like (1)
prasanna dash 18Oct2013 08:20 (in response to Satya Yenumula)
Dear Sowmya, Many many thanks for sharing valuable knowledge with us. Please share more document. RegardsPrasanna
Like (1)
sanjeev Singh 19Oct2013 14:50
Good JobThanks for sharing
Like (1)
rohit singh 23Oct2013 17:40
Hi Sowmya, it's a valuable information to understanding the concept of FISD Intergation. I appreciate your job Thanks
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 12/17
Like (1)
Gowthaami Moganti 24Oct2013 15:14
Hi sowmya, Thanku for sharing the information. Good work.
Like (1)
Shokat Ali 25Oct2013 09:50
Very useful.Thanks for sharing.
Like (1)
Mariks . 25Oct2013 14:59
Thanks for sharing valuable information..
Like (1)
SAQ MD 28Oct2013 06:01
Dear Sowmya, Thanks a million..... Regards,
Like (1)
Emilio Roldan Cosano 29Oct2013 16:23
Hello, Very useful. Thanks for sharing
Like (1)
Raman KV 30Oct2013 06:53
Good job. Useful doc. Thanks for sharing
Like (1)
Lakshmi Sama 30Oct2013 09:44
Hi Sowmya, Nice Doc Regards,Lakshmi S
Like (1)
Gaurav Tibrewal 31Oct2013 14:54
Hi Sowmya, Thanks for sharing such a nice document with detailed explanation. Very useful. Regards,Gaurav
Like (1)
Sridevi B 04Nov2013 15:14
Thanks for sharing very good document ... Regards ,Sridevi
Like (1)
Balaji M 05Nov2013 11:03
Good Job Sowmya...
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 13/17
Like (1)
Rama Chandra 06Nov2013 13:23
Thanks for sharing for good document..............
Like (1)
Venkateswarlu Ravula 07Nov2013 10:37
Great job!. Thank you for sharing such a nice doc.
Like (1)
Swapnoneel Mukherjee 12Nov2013 05:27
Great job .. very precise and to the point document. Thanks
Like (1)
Karanam Madhava Raj 15Nov2013 07:14
Good job. Very Useful Doc. Thanks for sharing. Madhava Raj
Like (1)
Murali Babu Nallamothu 17Nov2013 03:37
Hi Deepthi, I’m jealous about your SD knowledge are you a SD consultant or FI Thanks for sharing your integartion knowledge. RgdsMurali. N
Like (1)
Daniel Carvalho 18Nov2013 12:04
Very good tips! I would also add that the Account Determination (VKOA transaction) can also be found on the FI Path,under IMG > Financial Accounting > General Ledger Accounting > Business Transactions >Integration > Sales and Distribution > Prepare Revenue Account Determination. Regards,Daniel
Like (1)
pulak samantaray 18Nov2013 16:13
Nice document sowmaya,Thanks for sharing. RegardsPulak
Like (1)
Muthukumareshan vijayan 19Nov2013 07:23
Hi, Very nice document and nice presentation too.Keep it up. Regards,Muthu
Like (1)
pranav kumar 21Nov2013 06:42
Nice one FISD integration . thanks a lott. Kind regardsPranav Kr.GuptaSAP FICO Consultant
Shankar Kaza 25Nov2013 12:26
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 14/17
Like (1)
Nice Document Soumya...Good effort..Keep it up RegardsShankar
Like (1)
David Elvira 29Nov2013 15:58
Good documentIn my company I've tried to avoid complication, so we have only 3 tables of conditions with differentdegrees of columns on it. I try to add as much as possible on the global tables and only use theprecise ones for precise cases.However, I've seen a lot of companies where all the customizing is on the precise tables. That meansthat when creating a global condition, you need you modify a lot of rows wich is time consuming andsource of errors.So, keep it simple.
Like (1)
RAJAGOPAL REDDY VEERIAGARI 19Dec2013 10:46
Thanks for sharing valuable knowledge, It is very clear & simple. please sahre the partII aswell. RegardsRaj.
Like (0)
Joshua Muthyala 05Mar2014 15:26
Hello, Thank you for the brilliant explanation. I followed everything until the last part, Where KOFI, KOFK comes into picture. I do understand thepurpose of these condition types, but I am very confused with the way these are mapped to SDcondition Types. I thought, the SD Pricing Prcodure + condition types is mapped to Account Key, which in turn ismapped to the G/L account. So how does KOFI/ KoFK come into picture. Does it mean that, this is a secondary segregation once the flow reaches FI? SD Pricing Procedure + condition Type mapped to Account Key. Account Key + sales org + KOFI orKOFK determines the final G/L account Is this line of thought correct? Any help is appreciated. Thank youRegards,Joshua
Like (1)
David Elvira 05Mar2014 16:09 (in response to Joshua Muthyala)
HelloKOFI / KOFK allows the determination of the P/L account and Provision account associatedto a conbination of several parameters. These parameters can be the account key, the salesorg, char of accounts, etc. KOFI means FI Account determination and KOFK CO accountdetermination.These "condition types" are only used to determine the parameters used on VKOAtransaction. These parameters help determing the GL account with more or less complexity. KOFI/KOFK have nothing to do with the condition types like PR00 used on the documentitself to determine prices.David
Like (0)
Joshua Muthyala 05Mar2014 16:28 (in response to David Elvira)
Dear David, Thank you for your reply. Basically, I am trying to determine the concept associates with SD Flow in to FI. Orrather, what is the basis on which an SD Transaction flows, eventually to a G/Laccount. What I understand is that, the pricing procedure and SD condition Type, determinethe Account Key. This account key in turn is ONE of the many parameters, thatalong with KOFI/ KOFK, lead to the eventual G/L Account. Is this right? Regards,Joshua
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 15/17
Like (0)
David Elvira 05Mar2014 16:37 (in response to Joshua Muthyala)
That's right!
Like (0)
Joshua Muthyala 05Mar2014 16:46 (in response to David Elvira)
Thank you David. Regards,Joshua
Like (1)
AMOL MARATHE 26Mar2014 08:11
Hello,exceptional document. thank you for sharing it. regards,amol
Like (0)
Sowmya Tiwary 26Mar2014 12:10 (in response to AMOL MARATHE)
Thank you Amol
Like (1)
Balaji M 02Apr2014 10:45
Hi Sowmya Deepthi, Its good documentation, i hope u can post lot of new topics in FICO areas like New GL, Report painteretc... Thanks once again for your valuable post to SCN. Regards,M.Balaji
Like (0)
Sowmya Tiwary 02Apr2014 14:14 (in response to Balaji M)
Thanks Balaji. I will try.
Like (1)
pranav kumar 02Apr2014 17:54 (in response to Sowmya Tiwary)
Hi Sowmya, Ryt , I hope next time you will provide NEW GL concept along with DocumentSplitting Step by step. and Report Painter for for Profit Center as well Cost Centeras well Product Costing. Advance thanks. Pranav Kr. GuptaSAP FICO Consultant
Like (1)
Hansraj Bansal 22Apr2014 17:22
exceptional and excellent sharing.....
Like (0)
Sowmya Tiwary 23Apr2014 07:33 (in response to Hansraj Bansal)
Thank you Hansraj
Like (0)
Линь Чан 23Jul2014 16:17
Thank you very much for the document. This is a really well structured and nice document.
Jandoval Nascimento Silva Junior 24Jul2014 13:29
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 16/17
Like (0)
Sowmya Thank you to share this document with us. This is very useful.
Like (0)
Basappa Allannavar 22Aug2014 11:14
Hello, Its very useful document, thank u for sharing. Regards,Basappa
Like (0)
Bose . 24Aug2014 17:41
Hi Sowmya, Your blog gives a very good idea on FISD integration. However I feel some continuity is missing onPricing procedure to billing !! Accounting Key specified in condition type linked to Pricing procedure (here I am not understandingclearly, what happens after Pricing procedure? by searching in the web i read in some posts, asPricing procedure will be assigned to Billing doc type, customer, Sales Org)... Can you please give some detail on this in your way of explanation (hope that goes a easyunderstanding), how pricing procedure is determined by system when billing document is processed PS: I thought to post this in the discussions, but i felt its close to your blog post so posting here Thanks,Bose
Like (0)
Ram Mandalaneni 24Aug2014 18:07
Really God job sowmya i am study ur blog Its very useful document, thank u for sharing Regards,Ram
Like (0)
Declan Bolger 27Aug2014 16:06
Very Useful. Thanks and great work.
Like (0)
Michael Turner 29Aug2014 07:34
Good document info. Thanks.
Like (0)
bhawna sajwani 13Sep2014 20:26
Hi Sowmya , Quite a structured blog A very good and must read for FI consultants. Thanks for sharing the knowledge. Regards,Bhawna
Like (0)
Pankaj Bhole 23Jul2015 11:47
thanks Sowmya for Sharing ! Nicely Explained RegardsPankaj b
09/12/2015 FISD Integration I | SCN
http://scn.sap.com/docs/DOC46903 17/17
Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of Use Legal Disclosure Copyright