Solved: SD Flow Overview

Former Member · ‎06-21-2007

Hi

i'm ABAP consultant.i want to know the flow of SD and integration of SD with other modules.help me to know about SD.

Former Member · ‎06-21-2007

Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with which sales, production, and other supply chain targets can be set on the basis of historical, existing, and estimated future data. Rough-cut planning can also be carried out to determine the amounts of the capacities and other resources required to meet these targets.

Use SOP to streamline and consolidate your company’s sales and production operations.

SOP is particularly suitable for long- and medium-term planning.

Integration

SOP constitutes the planning functionality of the LIS information systems.

You pass on SOP plans to Demand Management (PP-MP-DEM) in the form of independent requirements. In turn, this data is fed to Master Production Scheduling (PP-MP-MPS) and Material Requirements Planning (PP-MRP).

An interface with Profitability Analysis (CO-PA) allows you to use CO-PA data as the basis for sales planning in SOP.

You can also pass on the results of SOP to Profitability Analysis (CO-PA), Cost Center Accounting (CO-OM-CCA), and Activity-Based Costing (CO-OM-CCA).

For more information please visit the following link:

http://help.sap.com/saphelp_erp2005/helpdata/en/a5/632f3b43a211d189410000e829fbbd/frameset.htm

Procurement Process consist of:

Purchase Requisition - A purchase requisition is a request or instruction to Purchasing to procure a certain quantity of a material or a service so that it is available at a certain point in time.

Request For Quatation - A request for quotation (RFQ) is an invitation extended to a vendor by a purchasing organization to submit a quotation (bid) for the supply of materials or performance of services.

Purchase Order - Formal request or instruction from a purchasing organization to a vendor or a plant to supply or provide a certain quantity of goods or services at or by a certain point in time.

Outline Agreement with vendors

a. Outline Purchase Agreement - An outline purchase agreement is a longer-term agreement between a purchasing organization and a vendor regarding the supply of materials or the performance of services within a certain period according to predefined terms and conditions. (Outside SAP, such agreements may be referred to by a number of terms, including "blanket", "master", "framework" or "umbrella" agreements)

b. Contract - In the MM Purchasing component, a contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame. (In the literature and in practice, similar concepts may also be referred to by a number of other terms, such as "systems contract", "blanket order agreement", "blanket contract", and "period contract".)

c. Schedulilng Agreement - A form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period.

Goods Receipt - If your company uses the MM Purchasing component, deliveries from vendors are most likely the result of purchase orders initiated by the purchasing department.

The purchase order is not only the document with which the purchasing department orders goods from the vendor; it is also an important planning and tracking tool for the following departments: Purchasing, Material Requirements Planning (MRP), Inventory Management, and Invoice Verification.

Quality Inspection - If an inspection at the time of goods receipt has been defined for the material, the system automatically creates an inspection lot when the goods receipt is posted. Quality Management uses this inspection lot to carry out the inspection.

Confirmation - Working with confirmations has the advantage that Materials Planning does not have to depend solely on the delivery dates and quantities set out in purchase orders or the delivery schedules of scheduling agreements.

Confirmations enable you to plan more exactly, since during the time-span between the order date and the desired delivery date you receive increasingly more reliable information from the vendor regarding the anticipated delivery.

Receipt of Vendor Invoice - Document from an invoicing party containing the payments to be made based on business transactions performed in Purchasing and Inventory Management. An incoming invoice can be an invoice or a credit memo.

Invoice Verification - Logistics Invoice Verification is a part of Materials Management (MM). It is situated at the end of the logistics supply chain that includes Purchasing, Inventory Management, and Invoice Verification. It is in Logistics Invoice Verification that incoming invoices are verified in terms of their content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The system updates the data saved in the invoice documents in Materials Management and Financial Accounting.

Sales

Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.

Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.

Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.

The sales area that accepts the inquiry is responsible for completing the agreement.

Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.

b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).

c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.

Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.

Reward points if this is helpful.

Regards,

Rajesh Banka

Former Member · ‎06-22-2007

http://www.sap-img.com/

Topic:

Free ABAP eBook Download

SAP MM, SD, FI, PS, PP, PM, HR, System Tables

Regards,

Rajesh Banka

Reward points if helpful.

Former Member · ‎06-22-2007

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

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

Regards,

Rajesh Banka

Reward points if helpful

Former Member · ‎06-21-2007

Hi Michael,

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

Thanks,

Vinay

Former Member · ‎06-21-2007

Hi Michael,

SD Life cylce is

Inquiry -> Quotation -> Sales Order -> Delivery -> Picking -> Packing -> Transporting -> Check status -> PGI -> Invoice -> Released to accounting (FI Module)

Transactions for create/change/view

Inquiry - VA11/VA12/VA13

Quotation - VA21/VA22/VA23

Sales Order - VA01/VA02/VA03

Shchedule Agreement - VA31/VA32/VA33

Contract - VA41/VA42/VA43

Delivery - VL01/VL02/VL03

Invoice - VF01/VF02/VF03

Item Proposals - VA51/VA52/VA53

Thanks,

Vinay

Former Member · ‎06-21-2007

Hi Michael,

INTERGRATION BETWEEN SD AND MM AND SD & FICO

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

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

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

Former Member · ‎06-21-2007

Hi,