integration between sd&fico

[Former Member]

hi guru's

wat is the intigrations between sd&all modules in real time scenario especially i want fico.plz send it as soon as possible.

regards

praveen

[Former Member]

Hi Praveen,

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 INTEGRATON WITH MM

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 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, and ME23. Tables EKKO, EKPO.

Sales Order OR

Tcode for creation VA01, VA02, VA03. Tables VBAK, VBAP

Delivery LF

Tcode for creation VL01, VL02, and VL03. Tables LIKP, LIPS

Billing MN

Tcode for creation VF01, VF02, and VF03. Tables VBRK, VBRP

To create a sales order we need purchase order number and customer 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 customer tcode is xd01, xd02, xd03.

Table is kna1.

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

check following link also

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

A3.

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.

A4.

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.

1. looking at MM and SD integration 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 on material 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.

SD Integration With CO PA

Sales & Operations Planning is integrated with Profitability Analysis. Thus, you have direct access to the quantities planned in CO-PA from Sales & Operations Planning.

The system needs to know the CO-PA field name and the CO-PA version in order to copy data from CO-PA. You can maintain a CO-PA field name for a product group in the master data of the product group’s master record. This establishes the link between the SOP product group and the desired CO-PA hierarchical level. If you carry out this function for a single material, the CO-PA field name is predefined and you cannot change it.

You can copy quantity key figures only.

If the plant of the material or product group is specified in CO-PA, it is this plant’s data that is copied. Otherwise, the system breaks down the quantities of the material or product group into plants using the settings made in the Customizing activity Define proportional distribution across plants.

To copy data from CO/PA in standard SOP:

Choose Edit ® Create sales plan ® Transfer CO-PA plan.

The Transfer Area dialog box appears.

Specify the number of the planning version within CO-PA, and the start and finish dates of the planning horizon for which you want to copy the data.

The CO-PA field name of a product group is maintained in the product group master record. It establishes the link between the SOP product group and the desired CO-PA hierarchical level.

To continue, choose ENTER .

The key figure values from CO-PA now appear in the planning table.

For more information on this method of creating sales plans in standard SOP

Sales & Operations Planning is integrated with Profitability Analysis. Thus, you have direct access to the quantities planned in CO-PA from Sales & Operations Planning.

The system needs to know the CO-PA field name and the CO-PA version in order to copy data from CO-PA. You can maintain a CO-PA field name for a product group in the master data of the product group’s master record. This establishes the link between the SOP product group and the desired CO-PA hierarchical level. If you carry out this function for a single material, the CO-PA field name is predefined and you cannot change it.

You can copy quantity key figures only.

If the plant of the material or product group is specified in CO-PA, it is this plant’s data that is copied. Otherwise, the system breaks down the quantities of the material or product group into plants using the settings made in the Customizing activity Define proportional distribution across plants.

SD INTGRATON WITH PS (Project Systems)

PS SD integration happens during Milestone billing...

Below is whole process-

Billing Plan for Milestone Billing

Milestone billing means distributing the total amount to be billed over multiple billing

dates in the billing plan.

As each milestone is successfully reached, the customer is billed either a percentage of

the entire project cost or simply a pre-defined amount.

During sales order processing, the system determines from the item category whether a

billing plan is required and, if so, which type of plan

The type of billing plan that is determined at this point is set up in Customizing and

cannot be changed in the sales document.

Billing plans for periodic billing and milestone billing plans for project-related milestone

billing have different overview screens so that you can enter data relevant to your

processing.

For example, for milestone billing, you must be able to enter data to identify the

individual milestones.

IMG configuration requires:-

1. Maintain billing plan types for milestone billing in OVBO.

2. Define date description in SM30 - V_TVTB.

3. Maintain Date Category for Billing Plan Type IN OVBJ.

4. Allocate date category in SM30 - V_TFPLA_TY.

5. Maintain date proposal for Billing Plan Type in OVBM.

6. Assign Billing Plan Type to Sales Documents Type in OVBP.

7. Assign Billing Plan Type to Item Categories in OVBR.

8. Define rules for determining the date in OVBS.

Milestone billing is typically used for billing projects, such as plant engineering and

construction projects. Such projects often include a series of milestones that mark the

completion of different stages of the work. In the SAP R/3 System, milestones are defined

in a network along with planned and actual dates for the completion of work. The milestones

are also assigned to the billing dates in the billing plan.

Each milestone-related billing date is blocked for processing until the Project System

confirms that the milestone is completed.

Delivery-relevant order items for which a milestone billing plan applies are billed on the

basis of the requested delivery quantity and not on the total of the confirmed quantities.

The connection between the project and the sales document item is made in the individual

schedule lines of the item. Each schedule item can be assigned to a network in a project.

To display the project-related data for a schedule line, proceed as follows:

In one of the overview screens of the sales document, select

1. Item -> Schedule lines.

2. Mark the schedule line and select Procurement details.

The following figure shows an example of milestone billing where only the Contract have

been billed :

Order Item Turbine 100,000

Billing Plan

Billing date Description % Value Billing Block Milestone Billing Status

01-10-94 Contract 10 10,000 - x x

01-03-95 Assembly 30 30,000 x x

01-04-95 Maintenance 30 30,000 x x

01-05-95 Acceptance 30 30,000 x x

01-06-95 Final invoice .. .. x

Network/Activities

Milestone Estimate Actual

Assembly 01-03-95 01-03-95

Maintenance 01-04-95

Acceptance 01-05-95

For each billing date in a milestone billing plan, you can specify whether the billing

date is:

1. fixed

2. Always updated with the actual date of the milestone

3. Updated with the actual date of the milestone, if the date is earlier than the

planned billing date for the date

A2. Following is the SD & PS integration scenarios where milestone billing & Periodic billing plays the important role for these integration:

Milestone billing is typically used for billing projects, such as plant engineering and

construction projects. Such projects often include a series of milestones that mark the

completion of different stages of the work. In the SAP R/3 System, milestones are defined

in a network along with planned and actual dates for the completion of work. The milestones

are also assigned to the billing dates in the billing plan. The connection between the project and the sales document item is made in the individual

schedule lines of the item. Each schedule item can be assigned to a network in a project.

PS-SD Integration as below:

A) Billing plan, at each WBS element, network and Activity level.

B)DIP profile which is assigend to item category. DIP for resource related quotation works only with ECP ( easy cost planning).

C)sales pricing - generally, there r 2 types of sales pricing in PS . lumpsum contract and unit rate contract.

D)BOS - bill of Services. which has to be activated. It is industry specific solution. If BOS is activated you also have integration for vendor RFQ and Analysis.

Further pls provide ME ur mail id , will mail some zip files regarding integration of SD module with all other module including PS.

A3. Project System(PS) works for any project e.g construction, operation or any large projects where project management tools are required. it integrates all modules may be like MM for vendor process or for RFQ etc or say may be SD for Resource related quotation with the help of DIP profile or Milestone process etc. IT is largely used in construction projects. IT helps in controlling the whole of project from one single screen and it works with 3 elements WBS element ( work break down structure), Network and Activity.

Please go throgh this Please check this links perhaps they may help.

http://help.sap.com/bp_imcv1500/IMC_US/HTML/preconfigured_scenarios.htm

ETO:

http://help.sap.com/bp_imcv1500/IMC_DE/HTML/E83_EN_DE.htm

http://help.sap.com/bp_bblibrary/500/HTML/E46_EN_DE.htm

MTO:

http://help.sap.com/bp_bblibrary/500/HTML/V66_BB_EN_US.htm

http://help.sap.com/bp_imcv1500/IMC_DE/HTML/E70_MTOQuotProc_EN_DE.htm

PS - SD integration are on

1.Billing pan, at each WBS element, network and Activity level.

2. DIP profile which is assigend to item category. DIP for resource related quotation works only with ECP ( easy cost planning).

3.sales pricing - generally, there r 2 types of sales pricing in PS . lumpsum contract and unit rate contract.

4. BOS - bill of Services. which has to be activated. It is industry specific solution. If BOS is activated you also have integration for vendor RFQ and Analysis.

5. resource related Billing

SD integration with HR

There is no major integration between SD and Hr, except the sales employee which is created in HR and used in SD. Apart from that some specialized modules like campus management which is sub module of HR module uses SD pricing procedure.

Can u explain the scenario where you find the other integration.

HR SD Integration happens...

1) Factory calendars...

2) Enterprise structure when you are assigning sales persons..

3) During workflow ...when you define and assign responsible persons responsible for particular process position wise..

INTERCOMPANY BILLING PROCESS

Intercompany Billing:

Go through the explanation given below with test cases.

Business case: -

Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.

SPRO Customization required:-

1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)

2. Maintain intercom any billing type as IV for sales document type OR

3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)

4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)

5. Automatic posting to vendor account (Optional)

6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing

Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing

Master data to be maintained:-

1. Create end customer master in company code/sales org 4211/RT/11

2. Create customer master for 4211 company code/sales org in 4436/RT/11

3. Maintain PR00 as price for end customer-Active in RVAA01

4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01

5. Maintain IV01 as inter-company Price-Active in ICAA01

Process:-

1. Create OR with sold to party as end customer.

2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.

3. Pricing procedure is RVAA01

4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.

5. Ordering sales org will create billing document F2 with reference to delivery for end customer.

6. Delivering sales org will create intercompany billing IV with reference to delivery document.

Following link

http://help.sap.com/saphelp_46c/helpdata/en/e6/4a6dc89e0311d189b70000e829fbbd/frameset.htm then go to special business transaction n click on intercompany sales processing.

http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b911d43ad11d189410000e829fbbd/content.htm

http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b917843ad11d189410000e829fbbd/content.htm

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

Hi

Interface between SD-FI/CO

1. Account determination

2.credit management

3.tax determination.

4.Accounting document at goods issue

For detailed information please ref : http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm

SD-MM

1. Material master

2. material document creation when Good issue

3. Third party.

4. stock transport order.

5. Induvidual purchase order.

SD-PP

Availability & MRP

Reward if helpfull

Muthupandiyan

[Former Member]

Hi Praveen Reddy

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.

Reward if useful to u

[Former Member]

hi,

with FICO:

tax determination,account determination.

with MM,

MMR,Shipping point determination,route determination,sto,third party process,intercompany billing.

with PP:

MTO process,MRP run,requirement type,availability check.bye.

reward me if it is useful

MCM

[Former Member]

Hi Praveen,

Following are few integration points between Sd and FICO

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 FI

Reward if this adds info

[Former Member]

hi

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

www.surya-padhi.net

Click FICO

In it check the documents link in GL section.

U have the integration manual.