sd integration with fico and mm

[Former Member]

Hi

please kinldy help me by sending complete integration notes between sd fico and mm

my email id is lbsrinivas@gmail.com

regards

srinivas

[Former Member]

Sent mail Reward if helps

[Former Member]

Hi...sriniwas..sending answer for query.rewrds me

Integration of SAPFI with MM is done at OBYC.

Let me elaborate... In MM you purchase goods and to which you pay, the purchasing process has the following steps:

Step1: First you send a Purchase Order to the Vendor.

Here there won't be any accounting entry as this is simply like telling the Vendor what goods you want, its quantity and the date of delivery etc.,

Step 2: You will receive the Goods to the Purchase Order.

When you receive Goods you CAN NOT make the following entry

Inventry A/c Dr

To Vendor A/c

because, some of the goods you have received may be damaged or may not be upto the mark or for any other reason goods may reject, so befor posting it to Vendor A/c we keep it in separate place till we verify the goods. And the actual entry will be

Inventry A/c Dr (Transaction Key

BSX @ OBYC)

To GR/IR A/c (Transaction

Key WRX @ OBYC)

Here the goods received is Debited to inventry and Credited to a temperary A/c i.e., GR/IR a/c

Step 3: You will post an Invoice to the Goods received.

Here you will post the invoice after you are satisfied with the goods received, the entry will be

GR/IR A/c Dr

To Vendor A/c

Now the goods are moved from GR/IR A/c and Vendor is Credited. Now you got the final entry of Goods to Vendor Account i.e,

Inventry A/c Dr

To Vendor A/c

i.e, Inventry A/c was Debited and Vendor A/c was Credit and GR/IR A/c is Dr and also Credited henced its balance became 'Zero', and it has to be Zero always.

[Former Member]

Hi...sriniwas..sending answer for query.rewrds me

Integration of SAPFI with MM is done at OBYC.

Let me elaborate... In MM you purchase goods and to which you pay, the purchasing process has the following steps:

Step1: First you send a Purchase Order to the Vendor.

Here there won't be any accounting entry as this is simply like telling the Vendor what goods you want, its quantity and the date of delivery etc.,

Step 2: You will receive the Goods to the Purchase Order.

When you receive Goods you CAN NOT make the following entry

Inventry A/c Dr

To Vendor A/c

because, some of the goods you have received may be damaged or may not be upto the mark or for any other reason goods may reject, so befor posting it to Vendor A/c we keep it in separate place till we verify the goods. And the actual entry will be

Inventry A/c Dr (Transaction Key

BSX @ OBYC)

To GR/IR A/c (Transaction

Key WRX @ OBYC)

Here the goods received is Debited to inventry and Credited to a temperary A/c i.e., GR/IR a/c

Step 3: You will post an Invoice to the Goods received.

Here you will post the invoice after you are satisfied with the goods received, the entry will be

GR/IR A/c Dr

To Vendor A/c

Now the goods are moved from GR/IR A/c and Vendor is Credited. Now you got the final entry of Goods to Vendor Account i.e,

Inventry A/c Dr

To Vendor A/c

i.e, Inventry A/c was Debited and Vendor A/c was Credit and GR/IR A/c is Dr and also Credited henced its balance became 'Zero', and it has to be Zero always.

[Former Member]

email sent.

Regards,

Rajesh Banka

Reward suitable points.

[Former Member]

sent mail reward if helps

[Former Member]

ome basic information :

FI-MM: The integration between FI-MM happens in T-code: OBYC

1. When PO is created :

-

---

No Entry -

---

2. When GR is posted

Inventory Account dr (Transaction Key BSX in OBYC)

To GRIR account (T.Key WRX in T-code OBYC)

3. When Invoice is posted

GRIR account Dr.

Vendor account Cr.

4. Payment made to Vendor

Vendor A/c Dr

To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions.

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,

1. Movement Types:

Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)

2. Valuation Class:

Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.

3. Transaction/Event key:

Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.

4. Material Type:

Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.

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

[Former Member]

Dear Srinivas,

<b>FI - SD:</b>• The basis of the sales process is the sales order . After receiving an inquiry from a customer a sales order has to be created to start the process.

• The sales order is generated on the level of the distribution chain. The ordered items may belong to different divisions. The sales order is an SD document and does not lead to posting in Financial Accounting.

• After the sales order is entered, the system performs an availability check for the desired delivery date.

• At the day of the shipping , a delivery document is created. The delivery is not ready for billing before the goods are picked from the warehouse inventory and posted as goods issue.

For the picking process, the warehouse management functionality is used. A warehouse transfer order has to be created which generates the picking request. The requested goods are picked from the warehouse and prepared for the delivery.

The goods to deliver are posted as goods issued . A goods issue document is created in MM and an accounting document is created in FI to post the goods issued on the right G/L accounts.

• The concluding activity in Sales and Distribution is billing . A billing document is created in SD and a printed invoice is sent to the customer. Simultaneously, an FI document is generated to post the receivables and revenues on the right accounts.

1)Insert regions OVK2

2)Define sales organization OVX5

3) Define distribution channel OVX1

4) Define shipping point OVXD

5) Assign sales organization to co.code OVX3

6) Assign distribution channel to sales organization OVXK

7) Assign division to sales org OVXA

😎 Assign sales org/distribution channel to plant OVX6

9) Assign shipping point to plant OVXC

10) Setup sales area OVXG

11) Define rules by sales area OVF2

12) Define pricing procedure determination

13) Define tax determination rules

14) Creation of G/L accts FS00

15) Assign G/L accts VKOA

16) Setup partner determination

17) Assign shipping points OVKC

18) Creation of SD customer master XD01

19) Creation of finished goods material master MM01

20) Maintain condition types VK11

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.

http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm

<b>Link Between SAP SD, MM & FI</b>

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.

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.

Integration of FICO with Other Modules

What are the steps for integration of FICO with other modules SD, MM etc. ?

Some basic information :

FI-MM: The integration between FI-MM happens in T-code OBYC.

1. When PO is created :

-

---

No Entry -

---

2. When GR is posted

Inventory Account dr (Transaction Key BSX in OBYC)

To GRIR account (T.Key WRX in T-code OBYC)

3. When Invoice is posted

GRIR account Dr.

Vendor account Cr.

4. Payment made to Vendor

Vendor A/c Dr

To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions.

---

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,

1. Movement Types:

Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)

2. Valuation Class:

Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.

3. Transaction/Event key:

Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.

4. Material Type:

Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.

Regards,

Naveen.