fi sd stepbystep config

8/10/2019 FI SD Stepbystep Config

http://slidepdf.com/reader/full/fi-sd-stepbystep-config 1/15

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

2 Tweet 2

created by Sowmyadeepthi KVN on Sep 26, 2013 10:29 AM, last modified by Sowmyadeepthi KVN on Mar 21, 2014 11:50 AM

This series of documents for FI-SD i ntegration 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 FI-SD Integration - I, it is t he second part because part I was the pre-requisitesrequired for the integration.

Part-I : Pre-requisites for FI-SD IntegrationPart-III : FI-SD Integration - IIPart-IV : FI-SD Integration III

Automatic Account Determination

The accounting entries with respect to the billing will generally result in

◦ Debit Customer account

◦ Debit Freight-out 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 customer

account gets picked up from the customer master data and the revenue account is configured based on certain

inputs so that correct account is hit during FI posting. This automatic account determination is configured not only

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 and

Distribution -> Basic Functions -> Account Assignment/Costing -> Revenue Account Determination

FI-SD Integration - I

ShareShare 11LikeLike

Version 6

Page1 of 15FI-SD Integration - I | SCN

17-Nov-2014http://scn.sap.com/docs/DOC-46903



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 account

assignment 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 screen

above which ensures that, for example, all the trading goods (Group 01) can be posted to different accounts than

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 of the material master. The system automatically proposes the account assignment group for the material in the

Sales documents from the material master.

The second activity in this step is customer account assignment groups maintenance. From the screen, double

click on Customers: Account Assignment Groups. The screen for maintaining customer groups will appear.

Use the New Entries button to create new groups. There are different customer groups created as in the screen

above which ensures that, for example, all the domestic revenues (Group 01) can be posted to different accounts

than that of all the foreign r evenues (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 the

Sales Area data in the customer master. The system automatically proposes the account assignment group for

the customer in the Sales or Billing documents from the c ustomer master.

Define Dependencies of Revenue Account Determination





The next step is defining the dependencies for revenue account determination – defining fields as well as

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

As already mentioned, the purpose of setting up account determination is to be able to differentiate accounts for

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 such

differentiation. The field catalog contains fields that can be selected when we create or maintain a condition

Table. These decided criteria are to be added by double clicking on the Field Catalog: Allowed fields for the tables

option.

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 listed

as shown below.

As shown above, if we want to add Payment cards: Card type as a criteria, double click on the entry and then

press 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 be

displayed using Account Determination: Display Tables option.

Enter the table number for which we need to s ee the table details and press enter.

As seen in the screen above, table 9 uses Sales Organization, Distribution Channel and Division as criteria for

account determination. The left pane shows the fields selected as criteria for this table and the right pane shows

the 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 standard

condition 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 is

being 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 can

enter the existing table number in the field below the new table number.

Select the field payment card type and choose the Select field button.

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 fields and press

save. The new condition table h as been created.

Note : The Field Catalog table is cross-client. Therefore, any changes done to this table will have effects in all

clients 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, the

sequence in which these tables will be accessed and the field contents of these condition tables. Double click on

the option.

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 click on theAccesses 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 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 tables is configured

such that, the more specific tables are accessed first for the information and then the less specific ones follow.

The Tab column contains the condition table number and the Description field contains the table description. To

see the fields contained in the condition table, click on the respective row and double click on the Fields folder as

highlighted on the left hand side. To add new tables to the access sequence use the new entries 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.





Average User Rating

(37 ratings)

2 Tweet 2

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 condition fulfilled.

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 for the various

application areas such as pricing, material determination, account determination etc. are maintained using

transaction code VOFM. Once the created, they can be assigned as required to access sequence's / pricing

procedures, etc.

Note : The Access Sequences table is cross-client. Therefore, any changes done to access sequences will have

effects in all clients on a server.

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 procedures as

discussed in the pre-requisites section. These condition types are used in account determination procedure. 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 start with

Z.

24333 Views Tasks: integration Tags: sap , billing, fico, reconciliation , financials , fi-sd

ShareShare 11LikeLike

66 Comments

Ranu Eugene Sep 26, 2013 11:22 AM

Hi Sowmyadeepthi KVN ,Nice Doc.Very useful.





Like (2)

Thanks for sharing.

Keep up the good work.

Best of Luck.

RegardsEugene

Like (1)

Sampat Kumkar Sep 26, 2013 11:30 AM

Hi

Its really good docs and useful for clearing the integration of FI-SD

thanks for nice document...

RegardsSampath

Like (1)

pankaj labhasetwar Sep 26, 2013 1:58 PM

Hi,

Very nice document and nice presentation too.

Keep it up.

Regards,

Pankaj

Like (2)

Ravi Sankar Venna Sep 26, 2013 2:00 PM

Good job Sowmya, keep it up.

Best Regards,Ravi

Like (1)

DHANAPRABU M Sep 26, 2013 3:31 PM

hi sowmya grt work keep going..all the best..

Regards,

Dhanaprabu

Like (1)

Suman Sardar Sep 26, 2013 4:04 PM

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$

Like (1)

Nishan Dev S Sep 26, 2013 5:21 PM

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, t hanks for sharing more to come from your library.

Thanks again for sharing,Nishan

AIM M Sep 27, 2013 6:48 AM

Hi

Sowmyadeepthi .....Good Document...........Great work..........Keep it up.





Like (1)

Thanks & Regards,

Aish.

Like (1)

Naresh Krishnamoorthy Sep 27, 2013 6:58 AM

Useful one...Thanks.

Best Regards,Naresh K.

Like (1)

krish S Sep 27, 2013 8:35 AM

Nice work.. keep to post some other documents also.. thank you so much.

Like (1)

Srinivas Salpala Sep 27, 2013 9:00 AM

Sowmya,

Good work!! Integration part is always a key area to learn. Keep up the best effort..

BR, Srinivas Salpala

Like (1)

Akberhusain Ajmeri Sep 27, 2013 11:48 AM

Good Job

Thanks for sharing

Like (1)

Sudhir Krishna Kumar Singh Sep 27, 2013 11:53 AM

nice document .....all the best,

ThanksSudhir Krishna Kumar Singh

Like (1)

Venkatesh Bandi Sep 30, 2013 3:30 PM

Nice document.

Like (1)

Erwin Leitner Sep 30, 2013 3:55 PM

Hello,

Many Thanks for sharing very good information.

all the best Erwin

Like (1)

Muthukumareshan vijayan Oct 4, 2013 4:56 PM

Hi,

Nice Doc.Very useful.

Thanks for sharing..

ThanksMuthu

Like (2)

Shrikant Sapaliga Oct 4, 2013 6:50 PM

Hi,

Thanks. Very useful doc.

regardsShrikant Sapaliga





Like (1)

Srinu S Oct 15, 2013 2:40 PM

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 Oct 15, 2013 2:49 PM

Hi Sowmyadeepthi KVN ,

Thanks for share your knowledge with us.

Regrads.

Jandoval Nascimento

Like (1)

Nishu Shah Oct 15, 2013 2:55 PM

Keep up the spirit

Thanks

Like (1)

Satya Yenumula Oct 18, 2013 7:45 AM

Hi Sowmya

Nice presentation.. Very useful...

ThanksSatya

Like (1)

prasanna dash Oct 18, 2013 8:20 AM (in response to Satya Yenumula)

Dear Sowmya,

Many many thanks for sharing valuable knowledge with us. Please share more document.

Regards-Prasanna

Like (1)

sanjeev Singh Oct 19, 2013 2:50 PM

Good JobThanks for sharing

Like (1)

rohit singh Oct 23, 2013 5:40 PM

Hi Sowmya,

it's a valuable information to understanding the concept of FI-SD Intergation.

I appreciate your job

Thanks

Like (1)

Gowthaami Moganti Oct 24, 2013 3:14 PM

Hi sowmya,

Thanku for sharing the information.

Good work.

Like (1)

Shokat Ali Oct 25, 2013 9:50 AM

Very useful.

Thanks for sharing.





Like (1)

Karanam Madhava Raj Nov 15, 2013 7:14 AM

Good job. Very Useful Doc. Thanks f or sharing.

Madhava Raj

Like (1)

Murali Babu Nallamothu Nov 17, 2013 3:37 AM

Hi Deepthi,

I’m jealous about your SD knowledgeare you a SD consultant or FIThanks for sharing your integartion knowledge.

RgdsMurali. N

Like (1)

Daniel Carvalho Nov 18, 2013 12:04 PM

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 Nov 18, 2013 4:13 PM

Nice document sowmaya,Thanks for sharing.

RegardsPulak

Like (1)

Muthukumareshan vijayan Nov 19, 2013 7:23 AM

Hi,

Very nice document and nice presentation too.

Keep it up.

Regards,Muthu

Like (1)

Pranav gupta Nov 21, 2013 6:42 AM

Nice one FI-SD integration .

thanks a lott.

Kind regardsPranav Kr.GuptaSAP FICO Consultant

Like (1)

Shankar Kaza Nov 25, 2013 12:26 PM

Nice Document Soumya...Good effort..Keep it up

Regards

Shankar

Like (1)

David Elvira Nov 29, 2013 3:58 PM

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 the preciseones 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 Dec 19, 2013 10:46 AM

Thanks for sharing valuable knowledge, It is very clear & simple. please sahre the part-II aswell.

RegardsRaj.

Like (0)

Joshua Muthyala Mar 5, 2014 3:26 PM

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 or KOFK determines the final G/L account ---Is this line of thought correct?

Any help is appreciated.

Thank youRegards,Joshua

Like (1)

David Elvira Mar 5, 2014 4:09 PM (in response to Joshua Muthyala)

HelloKOFI / KOFK allows the determination of the P/ L account and Provision account associatedo a conbination of several parameters. These parameters can be the account key, the sales

org, 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 VKOAransaction. 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 Mar 5, 2014 4:28 PM (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. Or rather, 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, determinehe Account Key. This account key in turn is ONE of the many parameters, that

along with KOFI/ KOFK, lead to the eventual G/L Account.

Is this right?

Regards,Joshua

Like (0)

David Elvira Mar 5, 2014 4:37 PM (in response to Joshua Muthyala)

That's right!

Like (0)

Joshua Muthyala Mar 5, 2014 4:46 PM (in response to David Elvira)

Thank you David.

Regards,Joshua

AMOL MARATHE Mar 26, 2014 8:11 AM

Hello,exceptional document. thank you for sharing it.





Like (1)

regards,amol

Like (0)

Sowmyadeepthi KVN Mar 26, 2014 12:10 PM (in response to AMOL MARATHE)

Thank you Amol

Like (1)

Balaji M Apr 2, 2014 10:45 AM

Hi Sowmya Deepthi,

Its good documentation, i hope u can post lot of new topics in FICO areas like New GL, Report painter etc...

Thanks once again for your valuable post to SCN.

Regards,M.Balaji

Like (0)

Sowmyadeepthi KVN Apr 2, 2014 2:14 PM (in response to Balaji M)

Thanks Balaji. I will try.

Like (1)

Pranav gupta Apr 2, 2014 5:54 PM (in response to Sowmyadeepthi KVN)

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 Center as well Product Costing.

Advance thanks.

Pranav Kr. GuptaSAP FICO Consultant

Like (1)

Hansraj Bansal Apr 22, 2014 5:22 PM

exceptional and excellent sharing.....

Like (0)

Sowmyadeepthi KVN Apr 23, 2014 7:33 AM (in response to Hansraj Bansal)

Thank you Hansraj

Like (0)

Van Linh Tran Jul 23, 2014 4:17 PM

Thank you very much for the document. This is a really well struct ured and nice document.

Like (0)

Jandoval Nascimento Silva Junior Jul 24, 2014 1:29 PM

Sowmya

Thank you to share this document with us. This is very useful.

Like (0)

Basappa Allannavar Aug 22, 2014 11:14 AM

Hello,

Its very useful document, thank u for sharing.

Regards,Basappa

Bose . Aug 24, 2014 5:41 PM

Hi Sowmya,





Follow SCNSite Inde x Contact Us SAP He lp P ortalPrivacy Terms of Use Legal Disclosure Copyright

Like (0)

Your blog gives a very good idea on FI-SD integration. However I feel some continuity is miss ing 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, as Pricingprocedure 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 Aug 24, 2014 6:07 PM

Really God job sowmya i am study ur blog

Its very useful document, thank u for sharing

Regards,Ram

Like (0)

Declan Bolger Aug 27, 2014 4:06 PM

Very Useful. Thanks and great work.

Like (0)

Michael Turner Aug 29, 2014 7:34 AM

Good document info. Thanks.

Like (0)

bhawna sajwani Sep 13, 2014 8:26 PM

Hi Sowmya ,

Quite a structured blog A very good and must read for FI consultants.

Thanks for sharing the knowledge.

Regards,Bhawna
