Scribd Logo
Upload

Welcome to Scribd!

  • 22 views

    Presentation 1

    Uploaded by

    warlareyes
    The document describes the key components of SAP MM and SAP SD modules. For SAP MM, it outlines the enterprise structure, configuration, master data types, different procurement requirements like purchase orders and contracts, as well as goods receipt and invoice processes. For SAP SD, it similarly outlines the enterprise structure, configuration, master data like customers and materials, sales order types, delivery, billing, and block and rejection functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Presentation 1

    Uploaded by

    warlareyes
    22 views26 pages
    The document describes the key components of SAP MM and SAP SD modules. For SAP MM, it outlines the enterprise structure, configuration, master data types, different procurement requirements like purchase orders and contracts, as well as goods receipt and invoice processes. For SAP SD, it similarly outlines the enterprise structure, configuration, master data like customers and materials, sales order types, delivery, billing, and block and rejection functions.

    Original Title

    Presentation1

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes the key components of SAP MM and SAP SD modules. For SAP MM, it outlines the enterprise structure, configuration, master data types, different procurement requirements like purchase orders and contracts, as well as goods receipt and invoice processes. For SAP SD, it similarly outlines the enterprise structure, configuration, master data like customers and materials, sales order types, delivery, billing, and block and rejection functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    22 views26 pages

    Presentation 1

    Uploaded by

    warlareyes
    The document describes the key components of SAP MM and SAP SD modules. For SAP MM, it outlines the enterprise structure, configuration, master data types, different procurement requirements like purchase orders and contracts, as well as goods receipt and invoice processes. For SAP SD, it similarly outlines the enterprise structure, configuration, master data like customers and materials, sales order types, delivery, billing, and block and rejection functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 26

    SAP MM

    - Enterprise Structure & Configuration


    - Master Data
    - Different Types of Requirements
    1. Purchase Requisition
    2. Purchase Order
    3. Purchase Contract
    4. Scheduling Agreement
    5. Consignment
    6. Subcontracting
    - Goods Receipt
    - Invoice Verification
    - Physical Inventory

    SAP SD
    - Enterprise Structure & Configuration
    - Master Data
    - Different Types of Requirements
    1. Sales Quotation
    2. Sales Order
    - Delivery
    - Billing
    - Block
    - Reject
    SAP MM
    Enterprise Structure

    Client Overall owner of the organization.


    Company Code Company/ies owned and handled by the client.
    Plant Actual infrastructure.
    Storage Location Tangible place for materials.
    Purchasing Organization Responsible for procurement process.
    Configuration

    - Where the customization of data happen (Define, Assign, etc.)


    - Tcode SPRO > SAP Reference IMG
    Master Data

    Material Master (MM01/MM02/MM03)

    - Stores the relevant data regarding the material.


    Vendor Master (XK01/XK02/XK03)

    - Stores the relevant data about the vendor.


    Info Record (ME11/ME12/ME13)

    - Stores the price of a material with regards to vendor.

    Source List (ME01/ME03)

    - Stores the supplier of a material in a plant.


    Bill of Materials (CS01/CS02/CS03)

    - Stores the components that builds a material.


    Condition Records

    Pricing Determination

    - Uses Tcodes MEK1/MEK2/MEK3 Condition Records to set the price of a material.


    - Condition Type uses Access Sequence for Determination; that can be setup in SPRO.

    Output Message Determination

    - Procedure on how to send the data to vendor.


    - Some Tcodes: MN01 (RFQ), MN04 (Purchase Order)
    Different Types of Requirements

    Purchase Requisition

    - Tcode ME51N/ME52N/ME53N; Release ME54N to convert into purchase order.


    - Approvable document for requesting goods. Not the formal document for procuring goods.

    Purchase Order

    - Tcode ME21N/ME22N/ME23N; Release ME29N for the order to be processed.


    - Formal document for procuring goods.
    Purchase Contract

    - Tcode ME31K/ME32K/ME33K
    - Used to fulfill the procurement via Quantity or Value within a validity period.
    Scheduling Agreement

    - Tcode ME31L/ME32L/ME33L; Create Delivery Schedule ME38

    Consignment

    - Special Procurement Type 10; Item Category K; Mvt Type 101K & 411K
    - Info Record Type Consignment

    MB51 (after Goods Receipt and Transfer Posting)


    Subcontracting

    - Special Procurement Type 30; Item Category L


    - Info Record Type Subcontracting
    - Has BOM for Provide material
    - Movement Type 101 (for Subcontracting material), 541 (for Provide material using Tcode ME2O)

    MB51 (Mvt 543 is backflush after MIGO Mvt 101)


    Goods Receipt (MIGO)

    - Done to receive the procured goods. Mvt 101. Increase in stocks, decrease in asset.
    Invoice Verification (MIRO)

    - Done to create billing/invoice for the received goods.


    Physical Inventory Management

    - Comparison and tallying between Physical Inventory and System Inventory


    - Freeze Book – to stop goods movement during Physical Inventory and prevent count differences
    - Tcodes:
    1. MI01 – Create Inventory Document
    MI24 – “Not Yet Counted” Status

    2. MI04 – Enter Inventory Count


    MI24 – “Counted” Status
    3. MI07 – Posting Inventory Count
    MI24 – “Counted, Adjusted” Status
    SAP SD
    Enterprise Structure

    Company Code Company/ies owned and handled by the client.


    Sales Area Consists of 3 Organizational Unit.
    Sales Organization Responsible for sale and distribution of goods and services.
    Distribution Channel How the goods reach to customers.
    Division Categorizing goods and services.
    Sales Office Physical location responsible for sales process.
    Sales Group Group of people who are responsible for processing sales and can be assigned to
    Sales Office
    Plant Actual infrastructure.
    Shipping Point Where goods and shipments are processed and monitored for delivery and usually
    assign to plant.
    Storage Location Tangible place for materials.
    Configuration

    - Where the customization of data happen (Define, Assign, etc.)


    - Tcode SPRO > SAP Reference IMG
    Master Data

    Customer Master (XD01/XD02/XD03)

    - Stores the relevant data regarding the customer.


    Material Master (MM01/MM02/MM03)

    - Stores the relevant data regarding the material.


    Output Master

    - How the sales requirement is sent to a customer.

    Condition Master (VK11/VK12/VK13)

    - How a material get its price with regards to a customer.


    Free Goods

    - Special type of condition records. Offered to customers and is included with the ordered
    quantity.
    - Item Category TANN (Free of Charge Item).
    Different Types of Requirements

    Sales Order (VA01/VA02/VA03)

    - Formal document for selling goods.


    - VKM1/VKM4 to release customers from their Credit Check

    Sales Quotation (VA21/VA22/VA23)

    - Informational document about the sales goods that is sent to customer.


    Outbound Delivery (VL01N/VL02N/VL03N)

    - Contains the happenings done to the materials (Picking, Post Goods Issue, etc)

    Billing Document (VF01/VF02/VF03)

    - Done to create billing document for the Outbound Delivery.


    - Accounting Document/Journal Entry is automatically created once processed.
    Block

    Billing Block

    - This field prevents a sales requirements to be billed. Needs to be released first.

    Delivery Block

    - This field prevents a sales requirements to be processed with Outbound Delivery. Needs to be
    released first.
    Reject

    Reason for Rejection

    - Done if an instance to not proceed with an order and/or to reject an order.

    You might also like