SD and MM FLOW with example

Question

Hi friends,
Can any one tell me the SD and MM Flow with respect to company and customer like what the company and customer will do in various stages?

Answer 1

hai  Reddy,
SAP Sales and Distribution Processing Document Flow
Document Flow in Sales
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customer’s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge – creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
The following graphic shows how the various types of sales documents are inter-related and how data subsequently flows into shipping and billing documents.
D 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.
MM  FLOW.
Tables
PO
EKKO---Header level
EKPO-Item level
PR
EBAN
GR/Material document
MKPF--Header
MSEG-Item
Invoice
RBKP-header
RSEG-Item
Accounting doc
BKPF--header
BSEG--Item
ServicesSSR--Header
ESLL-Item
It really depends on the company and their business process. Generally though:
Purchase Requisition (user reqests stuff, either for manuf/stock, or supplies). -> then the PReq would go through an approval process (Release Strategy). Once approved, one can either create a Request for Quote (RFQ) to multiple vendors to obtain the best prices - and/or create the Purchase Order (either directly from the PReq or from the RFQ).
Once the PO is created -> then a Goods Receipt is necessary (to indicate you received the goods ordered). Then Invoice Verification (again - if this is set up) - which basically prevents overpayment to a vendor (won't allow you to pay for goods not received through Goods Receipt). Then ultimately the payment to the Vendor.
So - Transaction flow for create (common):
PReq -> RFQ -> PO -> G/R -> Invoice -> payment (?)
ME51N -> ME41 -> ME21N -> MIGO -> MIRO -> payment (?)
Tables for Purchase Requisition:
EBAN -
EBKN - Account Assignment
Tables for Purchase Orders:
EKKO - Header
EKPO - Item
EINA - Purchasing Info Record (oops forgot to mention that above - PInfoRec has the vendor/material/price for future sourcing)
Tables for Request for Quote:
same as PO above
Tables for Goods Receipt:
MKPF - Material Document Header
MSEG - Material Document Item
EKBE - History of PO
Tables for Invoice Verification:
BSIS (good substitute for BSEG, which is a monster)
If Found Helpfull Do Reward.
Regards.
EShwar.