Skip to Content
Author's profile photo Former Member

FI-SD Integration – I

This series of documents for FI-SD 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 FI-SD Integration – I, it is the second part because part I was the pre-requisites required for the integration.

Part-I : Pre-requisites for FI-SD Integration

Part-III : FI-SD Integration – II

Part-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

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 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 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 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 customer 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.

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 see the table details and press enter.

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.

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.

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.

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.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member


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

      Author's profile photo Basappa Allannavar
      Basappa Allannavar


      Its very useful document, thank u for sharing.



      Author's profile photo Bose G
      Bose G

      Hi Sowmya,

      Your blog gives a very good idea on FI-SD integration. However I feel some continuity is missing on Pricing procedure to billing !!

      Accounting Key specified in condition type linked to Pricing procedure (here I am not understanding clearly, what happens after Pricing procedure? by searching in the web i read in some posts, as Pricing 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 easy understanding), 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



      Author's profile photo Former Member
      Former Member

      Really God job sowmya i am study ur blog

      Its very useful document, thank u for sharing



      Author's profile photo Declan Bolger
      Declan Bolger

      Very Useful. Thanks and great work.

      Author's profile photo Michael Turner
      Michael Turner

      Good document info.   Thanks.

      Author's profile photo Bhawna Sajwani Bhagat
      Bhawna Sajwani Bhagat

      Hi Sowmya ,

      Quite a structured blog 🙂

      A very good and must read for FI consultants.

      Thanks for sharing the knowledge.



      Author's profile photo Former Member
      Former Member

      thanks Sowmya for Sharing ! Nicely Explained 🙂


      Pankaj b

      Author's profile photo Former Member
      Former Member

      Rally nice step by step sequence for integration

      Author's profile photo Abhiram Aditya
      Abhiram Aditya

      Very helpful document. Gave much clear picture on FI SD integration. Thank you 🙂

      Author's profile photo Former Member
      Former Member

      This is brilliant, perfectly explained, thanks Sowmya, finally I understand how FI-SD integrate.

      Author's profile photo Sandeep TIMMAPUR
      Sandeep TIMMAPUR

      Thanks Soumya..Very helpful.. Do you have any document for FI-MM integration like this ?

      Author's profile photo Shagun Jain
      Shagun Jain

      This is awesome. Thanks Soumya..

      Author's profile photo SHAHEER ANSARI