Solved: INTEGRATION BETWEEN SD & OTHER MODULES

Former Member · ‎07-25-2007

Hi Gurus,

I would like to know the exact points at which the whole process of Integration happens between SD and other modules thru the entire Sales Cycle.

Regards,

Vinod

Former Member · ‎07-25-2007

Hi Vinod,

Details are below:

Link Between SAP SD, MM & FI

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

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 F2

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

Hope this will help you out !

Regards,

Syed Nasir

Former Member · ‎07-25-2007

Hey There,

It was nice of Nasir and Sateesh to have answered my query. Thanks a lot.

But I would like to know of the link between SD & PPQM modules.

regards,

Former Member · ‎07-25-2007

hi,

1.Looking at MM and SD intergation first, take the scenario of a 3rd 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 quantity as that which the vendor sends to you (but obviously shipped directly to your customer)

2.billing in an SD FUNCTION . but sap needs to know when processing a customer payment , to which G/L accounts the payment has to be processed. for example payment of the UK based nmaterial would be placed in different G/L account to that of a non-uk based material

Further more, a uk based customer may have a different G/L account to that of an export customer this is configured in account determination.

pls reward points if the answer is helpful

Regards,

Murali

Former Member · ‎07-25-2007

FI-SD Integration: The integration is done in T-code VKOA

1. Sales Order Created

~~-No Entry~~-

2. PGI done (Goods issue)

Cost of Goods Sold Dr (Configured in OBYC GBB T-Key)

To Inventory Account

3. Billing document released to Accounting

Customer Account Dr.

To Sales Revenue Account (ERL T-key in Pricing procedure)

Note : The GL account is assigned to this ERL in VKOA

4. Payment Received

Bank Clearing A/c Dr

Customer A/c Cr.

Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc.

Regards,

Rajesh Banka

Reward points if helpful.

Former Member · ‎07-25-2007

Hi Vinod Kumar,

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

SD AND MM INTGRATON

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

In Pricing we would want to determine the cost of the product

thru VPRS Condition Type. This cost of the material is

picked from the Material Master. How this happens is, if

we would want to determine this cost VPRS in the Sales Order

for Profitability purpose then , all those Item categories

that can appear in a sales order must be activated for

Determine Cost Check box in customizing. That’s one of the SD

MM Integration.

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 background. E.g. 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 Module is integrated with various modules during transaction processing ...

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

If you work in SD area, then the most important process where you really need to know MM area is the third-party process. In this case from SD sales order automatically the purchase requisition will be created on MM side. From this purchase requisition on MM side you create the purchase order on MM side. This purchase order updates the sales order on SD side, if you create the confirmation of the purchase order. This process takes place for the pure third-party as well as for individual purchase order process. Later the invoice will be sent from MM to SD (transaction MIRO) and will update the status of the SD order. If you work with this process then you need really know MM transactions quite well, because it is the same SD and MM system.

Another area where you have SD of one system integrated with MM of another system is the EDI process. Here several remarks concerning EDI concept of SD:

EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronically documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.

If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every time send a change to the existing order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).

So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOICE.

Additional processes in SD, where EDI are used in communication with MM are:

1) sending (from MM side) and application (on SD side) of delivery schedules to the scheduling agreement: IDOC of type DELINS. In this case we have practically automatically communication between SD and MM scheduling agreements via IDOCs;

2) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV are sent from MM customer to SD customer. So, the output function module belongs to MM area and the inbound function module - to SD area.

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula