Link Between SAP SD, MM & FI

1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-

1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped 
directly to your customer). 

1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc.                *-- Shahee

The link between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availibility check related data is also taken from MM although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.

4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.

There are many such links between SD and MM.

Now the link between SD and FI :-

1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.

Sales Order – 
Integration Points                      Module
•Availability Check             -       MM
•Credit Check                   -       FI
•Costing                        -       CO/ MM
•Tax Determination              -       FI
•Transfer of Requirements       -       PP/ MM

Delivery & Goods Issue – 
Integration Points                      Module
•Availability Check             -       MM
•Credit Check                   -       FI
•Reduces stock                  -       MM
•Reduces Inventory $            -       FI/ CO
•Requirement Eliminated         -       PP/ MM

Billing -
Integration Points                      Module
•Debit A/R                      -       FI/ CO
•Credit Revenue                 -       FI/ CO
•Updates G/ L                   -       FI/ CO
  (Tax, discounts, surcharges, etc.)
•Milestone Billing              -       PS

Return Delivery & Credit Memo -
Integration Points                      Module
•Increases Inventory            -       MM
•Updates G/ L                   -       FI
•Credit Memo                    -       FI
•Adjustment to A/R              -       FI
•Reduces Revenue                -       FI
Tips by: Subha

SD Transaction Code Flow: 

Inquiry / Document type IN
Tcode for creation VA11,VA12,VA13. tables VBAK, VBAP

Quotation / QT
Tcode for creation VA21,VA22,VA23. tables VBAK, VBAP

Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO, EKPO.

Sales Order OR
Tcode for creation VA01,VA02,VA03. tables VBAK, VBAP

Delivery LF
Tcode for creation VL01,VL02,VL03. tables LIKP, LIPS

Billing MN
Tcode for creation VF01,VF02,VF03. tables VBRK, VBRP

To create a sales order we need purchase order number and custmer number.  Before that, to create a purchase order we need to have material no, vendor no.

To create vendor tcode is 
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.

To create custmer tcode is xd01, xd02, xd03.
Table is kna1.

After creating sales order using this no we can create delivery note tcode is vl01.    *-- Ujwala Shirsulla

See also:
The Flow Of Return Sales Order

Get help for your SAP SD problems
Do you have a SAP SD Question?

SAP Sales and Distribution Books
SAP SD Books  - Certification, Interview Questions and Configuration

SAP SD Discussion Forum and Sales/Distribution Tips

Main Index
SAP Basis, ABAP Programming and Other IMG Stuff

All the site contents are Copyright © and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of or the content authors.