Skip to Content
author's profile photo Former Member
Former Member

regarding SD, MM, and fi/co

hi to every one

i want the information about the

1.SD flow

2.MM flow

3.fi/co flow

4.how to integratie with SD to MM

5.how to integrare with SD to fi/co

6.how to integrate with MM to fi/co.

pls give help

thanks

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

6 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2007 at 11:17 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 31, 2007 at 11:19 AM

    Hi,

    SD & MM FLOW

    1. PURCHASE REQUISITION: is document created within the organization and submitted to Purchase Organization for requesting the procurement of required materials from the outside.

    t.code ME51

    2. Where as PURCHASE ORDER is issued by the Purchase Organization to vendor for the procurement of the materials.

    t.code ME21n

    <b>The Dataflow Of MM:</b>

    1) Purchasing Requisition -> sent by inventory dept to purchasing dept, STaff in an organization PLACES Pur requisition for want of some goods/products ME51

    2) Request for Quotation(RFQ)-> Purchasing Dept shall ask the vendors to give the quotation for the requested materials by inventory.ME41

    3) Quotation -> Quotation is sent by vendors to the company

    4) Purchase order-> Based on all paramers of a quotation sent by vendors. Vendors are selected from whom the material has to be obtained. The company gives purchase order to the vendor. ME21N

    5) Good's receipt -> vendors sends the goods to the company with goods receipt.

    6) Invoice verification -> this done based on good's receipt (MIGO). This means that the ordered goods have reached or not.

    7) Payment -> payment is done based on invoice verification. This is (FI/CO)

    <b>Transaction Codes:</b>

    RFQ to Vendor - ME41

    Raising Quotation - ME47

    Comparison of Price - ME49

    Creation of PO - ME21N

    Goods Receipt - MIGO

    Invoice (Bill PAssing) - MIRO

    Goods Issue - MB1A

    Physical Inventory - MI01( Create doc)

    MI04 (Enter Count)

    MI07 (Post)

    ****************

    <b>MM Process flow:</b>

    The typical procurement cycle for a service or material consists of the following phases:

    1. Determination of Requirements

    Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

    2. Source Determination

    The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

    3. Vendor Selection and Comparison of Quotations

    The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

    4. Purchase Order Processing

    The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

    5. Purchase Order Follow-Up

    The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

    6. Goods Receiving and Inventory Management

    Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.

    7. Invoice Verification

    The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

    <b>SD Process Flow:</b>

    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.

    <b>

    SD FLOW</b>

    <b>SD Flow Cycle and T Codes:</b>

    INQUIRY ( VA11)

    |

    QUOTATION (VA21)

    |

    PURCHASE ORDER (ME21)

    |

    ORDER CONFIRMATION (VA01)

    |

    PICKING LIST – (VL36)

    |

    PACKING LIST - (VL02, VL01)

    |

    SHIPPING – (VT01)

    |

    INVOICE – (VF21, VF01)

    |

    AR

    Explantion with relavent tables:

    Enquiry - Customer enquires about the Products services that were sold by a company - VA11

    Quotation - Company Gives a Quotation for the products and Services to a Customer

    Sales Order - Customer gives a Purchase order to the company against which a Sales order will be raised to Customer in SAP.

    VBAK: Sales Document(Header Data) (VBELN)

    VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)

    Enquiry, Quotation, Sales Order are differentiated based on Doc.

    Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,

    for Quotation 'B' & for Order it is 'C'.)

    Delivery(Picking, Packing, Post Goods Issue and Shipment)->

    Company sends the material after picking it from Godown and Packing it in a Handling Unit(box) and Issues the goods

    LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)

    LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)

    (LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)

    Billing - Also company bills to the customer for those deliveries

    And in FI against this billing Accounting doc is created.

    VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)

    VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)

    (VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)

    Apart from these tables there are lot of other tables which starts with

    ‘V’, but we use the following tables frequently.

    VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)

    VBTYP= ‘C’(Sales Order) VBTYP=’J’(Delivery) VBTYP=’M’(Invoice)

    VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)

    VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)

    VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)

    VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)

    VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)

    VEDA: Contract Data(VBELN,VPOSN)

    VEDAPO: Contract Data(VBELN,VPOSN)

    KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)

    A purchase order is a legal document acting as a purchasing document between the buyer and the seller. The buyer is the one who creates the purchase order. The purchase order contains some mandatory entries like name and address of the vendor, address of the buyer, quantity of the PO ,rate ,deadline for supply ...etc.

    In business point of view, there are two types of POs,

    one is vendor PO and the other is customer PO.

    Vendor PO is the one, we generate (Create) in the system and send to the supplier.

    vice versa, Customer PO come from the customer to the supplier and those listed items has to be supplied by the supplier.

    Customer PO can’t be generated in the SAP system, it can be registered in the SO (sale order) creation.

    1. What is meant by open purchase orders---> list of open which are open, means yet to receive goods from the vendor.

    2. What is meant by open Sales orders---> List of SO which has to be delivered to customers.

    What is meant by BOM (Bill of Material)---> BOM will consist of RAW materials required to produce one Finished GOOD.

    rewards if useful,

    regards,

    nazeer

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2007 at 11:24 AM

    Hello Srinivas,

    I can provide what are all the tables used in different modules in SAP.

    And the relation ship between tables and accross the modules also. In the bellow link u can download one .exe file. It consists of all the information.

    http://www.sap-img.com/sap-download/sap-tables.zip

    reward If Useful.

    Regards

    --

    Sasidhar Reddy Matli.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2007 at 11:24 AM

    <b>SD Flow</b>

    You create a sales document to enter information about different sales transactions. R/3 provides a number

    of predefined sales document types. However , these can be customized to suit your company's needs when

    R/3 is installed.

    Some examples of sales documents include:

    • sales queries

    • sales orders

    • outline agreements

    • complaints

    You use sales queries to enter information about potential sales into R/3.Types of sales query documents

    include:

    • inquiries

    • quotations

    • free-of-charge deliveries

    An inquiry is used to record any general queries a customer may have about goods or services they

    are thinking of buying from your company. An inquiry is one of the first possible documents you can

    create in the customer order management cycle. An example of the type of information contained in an

    inquiry is whether your company stocks a certain product line. Along with entering general customer

    queries, you can use inquiries to record the goods or services that a customer is interested in. And you

    can enter descriptions of goods or services that your company should research in order to answer customer

    queries. You can carry out automatic pricing for any goods or services you enter in an inquiry. This will

    enter the price of goods or services into the inquiry for you. You can also check whether any goods you

    entered in the inquiry are available in your company's warehouse. The order probability function enables

    you to determine the likelihood that a customer will buy from you. To increase the probability of a sale,

    you can offer the customer alternative goods and services.

    Quotations are sales query documents that you create when a customer requests specific information

    about a product. For example, you can use a quotation if a customer makes a query regarding how much

    goods or services cost or you can use a query if a customer asks when goods will be available for shipping.

    You can create quotations from scratch or you can create them by copying inquiries. If a customer is

    interested in the products or services after they have made an inquiry, you can provide a quotation based

    on the original inquiry. R/3 allows you to copy the information directly from an inquiry to a quotation.

    Let's say an inquiry was created when a customer inquired whether your company, could manufacture

    twenty motorcycles. Assume a quotation was created by copying this inquiry when the customer called

    back to inquire how much twenty motorcycles would cost. You can use quotations to enter information and

    descriptions for goods and services that are to be researched. You can also use them to carry out automatic

    pricing and to check goods availability. You can use quotations to calculate the probability that a customer

    will buy the goods or services entered on a quotation. This function is called order probability.You can

    also use quotations to enter details about alternative goods or services. These are goods or services that a

    customer did not inquire about but that you think they will consider purchasing. Once you have created a

    quotation for a query in R/3, you send the quotation to the customer who made the query. The quotation

    represents a binding offer made to the customer that includes quantity and cost details.

    You create a free of charge delivery when you send free samples of any goods that your company

    produces to customers. These contain information about the goods that are delivered but they don't

    include the corresponding pricing information for them.

    Let's look at the sales orders that exist in R/3.You create a sales order when a customer has ordered

    goods or services from your company. They are a part of the customer order management cycle.

    You can carry out automatic pricing in sales orders to enter the price of goods or services.

    R/3 will also run a credit check on the customer to see if they will be exceeding their credit limit.

    You can also check whether ordered goods will be available in your company's warehouse for delivery.

    Examples of types of sales order include

    • standard orders

    • consignment orders

    • cash orders

    • rush orders

    You create standard orders for goods and services that will be delivered or rendered according to

    the standard R/3 sales cycle. This means that goods are ordered, picked from the warehouse, and

    then shipped before customers are billed for them. Likewise, services are rendered before customers

    are billed for them.

    Your company may store its goods in its customers' warehouses. You create a

    consignment order when a customer is ready to retrieve stock from the warehouse.

    SAP can propose the most suitable stock to retrieve, including third-party stock.

    A consigment order is like a standard sales order for goods but it doesn't have any delivery

    information.

    You create cash orders and rush orders for the sale of goods only.

    You create a cash order when a customer picks up and pays for a delivery as soon

    as it is ordered. And you create a rush order when the customer picks up the goods on the

    same day as the order is placed. In this case, the invoice is created later.

    You can arrange to deliver goods or render services in installments. To do this, you create an

    outline agreement. Examples of some types of outline agreement include :

    • quantity and value contracts

    • master contracts

    • scheduling agreements

    • service contracts

    You create a quantity contract if a customer has agreed to order a certain quantity

    of goods from your company during a specified period.

    And you create a value contract if a customer has agreed to order goods of a certain

    cumulative value from your company during a specified period.

    Quantity and value contracts do not include delivery dates, so releases are made

    using a sales order.

    You can unite multiple contracts in a single master contract.

    Let's say you create a quantity contract because a customer has agreed to order

    500 engines in the first six months of the current year. If the customer orders 100 of these

    engines in January, you create a sales order called a release order.You refer to a quantity

    contract in a release order. So you refer to the quantity contract created for the 500 engines in

    each release order created for these engines. R/3 will then update the quantity contract

    automatically so it contains the correct number of remaining engines to be ordered.

    Scheduling agreements specify the installments in which goods will be delivered

    to a customer. They include the quantity of a product that will be delivered in each

    installment. And they include the delivery date of each installment. You process a delivery

    for each installment contained in the scheduling agreement in the same way that you process

    a delivery for a regular sales order.No sales documents, such as release orders, are created before

    the products included on a scheduling agreement are processed for delivery.

    You create a service contract if a customer requests a service over a particular

    period of time.For example, you could create a service contract if a customer ordered five

    one-hour maintenance checks from your company's motorcycle repair department.

    You create complaint sales documents if there has been a fault with any goods that

    have been delivered, or with any services rendered, by your company.

    For example, you create complaint sales documents if customers have been billed

    incorrectly for an item or service, or if goods are faulty.

    Different types of complaint sales document include

    • returns

    • credit memo requests

    • debit memo requests

    You create a returns document if a customer returns goods they have purchased from

    you because they are not satisfied with them. You can create returns from scratch or you can

    create them by copying the sales order that was originally created for the returned delivery.

    A returns document records that you expect stock to be returned to your warehouse.

    You can create one or more credit memo requests if a customer has been overcharged

    for a quantity of goods or services. You can also create a credit memo request if goods were

    damaged during transit and you want to credit the customer for the goods damaged.

    When you create a credit memo request, your Accounting department reviews it to

    confirm that it can be justified. If the credit memo request is approved, the Accounting department

    creates a credit memo based on the request. You can create credit memo requests by copying other

    sales documents such as the sales order where the overcharge occurred.

    You create debit memo requests when customers have been undercharged for products

    or services.Your company’s Accounting department can then create an invoice to bill the

    undercharged customer.

    This document is adopted from Smart Force Campus Course Material

    ___________________________________

    <b>MM Flow</b>

    PR >Release the PR>RFQ>Quotation>Quotation Comparison>PO>Release the PO>GR>Invoice Verification

    MM Process flow:

    Process Flow

    The typical procurement cycle for a service or material consists of the following phases:

    1. Determination of Requirements

    Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

    2. Source Determination

    The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

    3. Vendor Selection and Comparison of Quotations

    The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

    4. Purchase Order Processing

    The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

    5. Purchase Order Follow-Up

    The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

    6. Goods Receiving and Inventory Management

    Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.

    7. Invoice Verification

    The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

    Pur info record is nothing but a master data like thing which will be maintained for different materials to determine the prices etc.It Specifies the number that uniquely identifies a record.

    For Example: an info record is based on Plant Vendor and Material

    Based on these three the Material Prices will be calculated

    for different combinations different values are taken into consideration.

    During pricing it brings these values automatically based on this info record.

    Use ME11 Tcode to create this record.

    Common Tables used by SAP MM

    Below are few important Common Tables used in Materials Management Modules:

    EINA Purchasing Info Record- General Data

    EINE Purchasing Info Record- Purchasing Organization Data

    MAKT Material Descriptions

    MARA General Material Data

    MARC Plant Data for Material

    MARD Storage Location Data for Material

    MAST Material to BOM Link

    MBEW Material Valuation

    MKPF Header- Material Document

    MSEG Document Segment- Material

    MVER Material Consumption

    MVKE Sales Data for materials

    RKPF Document Header- Reservation

    T023 Mat. groups

    T024 Purchasing Groups

    T156 Movement Type

    T157H Help Texts for Movement Types

    MOFF Lists what views have not been created

    A501 Plant/Material

    EBAN Purchase Requisition

    EBKN Purchase Requisition Account Assignment

    EKAB Release Documentation

    EKBE History per Purchasing Document

    EKET Scheduling Agreement Schedule Lines

    EKKN Account Assignment in Purchasing Document

    EKKO Purchasing Document Header

    EKPO Purchasing Document Item

    IKPF Header- Physical Inventory Document

    ISEG Physical Inventory Document Items

    LFA1 Vendor Master (General section)

    LFB1 Vendor Master (Company Code)

    NRIV Number range intervals

    RESB Reservation/dependent requirements

    T161T Texts for Purchasing Document Types

    Tcodes:

    RFQ to Vendor - ME41

    Raising Quotation - ME47

    Comparison of Price - ME49

    Creation of PO - ME21N

    Goods Receipt - MIGO

    Invoice (Bill PAssing) - MIRO

    Goods Issue - MB1A

    Physical Inventory - MI01( Create doc)

    MI04 (Enter Count)

    MI07 (Post)

    ______________________

    <b>FICO</b>

    The FI module has 8 sub modules:

    FI-GL

    General Ledger Accounting

    FI-LC

    Consolidation

    FI-AP

    Accounts Payable

    FI-AR

    Accounts Receivable

    FI-BL

    Bank Accounting

    FI-AA

    Asset Accounting

    FI-SL

    Special Purpose Ledger

    FI-FM

    Funds Management

    CO Controlling

    represents the company's flow of cost and revenue. It is a management instrument for organizational decisions. It too is automatically updated as events occur.

    The CO module has following sub modules:

    CO-OM

    Overhead Costing (Cost Centers, Activity Based Costing, Internal Order Costing)

    CO-PA

    Profitability Analysis

    CO-PC

    Product Cost Controlling

    ____________________________

    regards,

    srinivas

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 31, 2007 at 11:34 AM

    <b><u>SD Flow</u></b>

    Inquiry <i>VA11/VA12/VA13</i> >> Quotation <i>VA21/VA22/VA23</i> >> Sales Order <i>VA01/VA02/VA03</i> >> Delivery & PGI (post goods issue) <i>VL01/VL01N/VL02NVL03N</i> >> Shipment VT01N/VT02N/VT03N >> Billing/Invoice <i>VF01/VF02/VF03</i>

    <b><u>MM Flow</u></b>

    Request for Quotation (RFQ) <i>ME41/ME42/ME43</i> >>

    Quotation <i>ME47/ME48</i> >>

    Purchase Requisition <i>ME51/ME51N/ME52N/ME53N</i> >>

    Purchase Order <i>ME21/ME21N/ME22N/ME23N</i> >>

    Goods Reciept <i>MB1C/MIGO</i> >>

    Invoice Reciept <i>MIRO</i> >>

    <i><b>FI Flow</b></i>

    Post Incoming payments F-28 >>

    Post outgoing payments F-31 >>

    Posting of other documents by F-02 >>

    there are many different transaction in FI

    <b><i>Integration of SD/MM/FI</i></b>

    - SD is integrated with MM at the time of Post Goods Issue of Delivery.

    - SD is integrated with FI when Accounting document of Invoice is generated.

    - MM is integrated to FI when Invoice document entry is made.

    above are main points of integration, still there are lots of other points of integration.

    - Alpesh

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 31, 2007 at 11:51 AM

    thanks for every one

    its more usefull

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.