Process flow of material creation

hi sap gurus,myself rekha
i want to know the process flow  of material creation-FERT

Check below link .You have to use transaction MM01 to create material.
https://www.google.com.au/search?q=process+flow+for+material+creation&oq=process+flow+for+material+creation&aqs=chrome..69i57.9710j0j8&sourceid=chrome&espv=210&es_sm=122&ie=UTF-8#q=process+flow+for+material+creation%2Bsap

Similar Messages

  • Exact process flow  for   Material management  (MM)  and  UI  Tcodes.

    Hi  Gurus,
    Could  any one tel me Exact process flow  for   Material management  (MM)  and  UI  Tcodes.
    ALL   BAPIs  for   MM  module.
    Thanks in Advance.

    hi,
    Check the threads:
    MM  flow
    MM-Process
    For tcodes:
    TCODES IN MM
    TCODES IN MM
    Hope it helps..
    Regards
    Priyanka.P

  • Work Flow for Material Creation in MDM

    Hi MM Experts,
    Can any one tell me whether there is an option of having Work Flows for Creating Material in SAP MDM (Master Data Management). I think this feature is not available in Standard SAP R/3.
    Cheers
    Deepal

    hi
    check this website.
    https://www.sdn.sap.com/irj/sdn/nw-mdm?rid=/webcontent/uuid/5024a59a-4276-2910-7580-f52eb789194b [original link is broken]

  • Process flow For Transportation

    Hi:
    I would really appreciate if You could send me process flow from delivery creation to freight cost settlement in SAp. I want to understand how it works in SAP. Is freight PO generated for each shipping document? Is it manual or automatic process. Also would like to have config behind transportation,
    Thanks

    Hi Dev,
    Process flow for Transportation planning
    Delivery(After picking and Before PGI)(VL01N) >Shippment document(VT01)>Shipment cost document(VI01)
    If do the transfer in the shipment cost document automatically service  PO will be created based on the PO Invoice will be created automatically.
    Manually also you can process PO and Invoice based on the configuration settings.
    Transportation Planning configuration Steps: -
    1.Maintain Transportation planning point: -
       Menu path:  SPRO --> IMG -->Enterprise structure --> Definition --> Logistics execution --> Maintain Transportation planning point.
    2.Shipments: -
       Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Shipments.
    2.1 Maintain Transportation relevance
    Menu path: SPRO --> IMG --> Logistics execution --> Transportation > Shipments> Maintain Transportation relevance.
    2.2 Define Shipping type: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Shipments --> Define Shipment type.
    3.Basic Transportation functions: -
       Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions
    3.1 Defining Output control for the shipments: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Output control --> Maintain Output determination for shipments.
    3.2 Partner control for the shipments: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Partner control --> Set up partner determination for Shipments.
    3.3 Text control for the shipments: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Text control --> Define & Assign Text determination procedure.
    3.4 Routes: -
        Menu path: SPRO --> IMG --> Logistics execution ---> Transportation --> Basic Transportation functions --> Routes --> Define Routes.
    3.4.1 Define Routes: -
    a.Define Transportation connection points.
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Routes --> Define Routes --> Define Transportation connection points.
    b.Define Routes and stages.
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Routes --> Define Routes --> Define Routes and stages.
    3.4.2 Route Determination: -
       Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Routes --> Routes determination
    a.Define Transportation zones
       Menu path: SPRO  IMG --> Logistics execution --> Transportation -->Basic Transportation functions --> Routes --> Routes determination --> Define Transportation zones.
    b. Maintain country and transportation Zone for shipping point
    Menu path: SPRO -->IMG --> Logistics execution -->Transportation -->Basic Transportation functions --> Routes --> Routes determination --> Maintain country and transportation Zone for shipping point.
    c. Maintain Route Determinations: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Basic Transportation functions --> Routes --> Route determination --> Maintain Route determination.
    4. Shipping Costs : -
        Menu path:  SPRO -->IMG --> Logistics execution -->Transportation --> Shipping cost
        4.1 Shipping cost Basic Functions: -
         Menu path:  SPRO --> IMG --> Logistics execution --> Transportation --> Shipping cost --> Basic functions --> Define Date Rules.
    4.2 Shipping Cost Document: -
       Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Shipping cost --> Shipment cost document.
    a. Shipping cost type and item categories.
        Menu path: SPRO --> IMG -->Logistics execution --> Transportation -->Shipping cost --> Shipment cost document --> Shipping cost type and item categories.
    b. Shipping Cost relevant and Default setting for shipment cost type: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Shipping costs Shipment cost document --> Shipping Cost relevant and Default setting for shipment cost type.
    4.3 Shipment cost Pricing: -
        Menu path: SPRO --> IMG --> Logistics execution -->Transportation --> Shipping costs --> pricing
      a. Define & Assign pricing procedures.
         Menu path: SPRO --> IMG --> Logistics execution -->Transportation -->Shipping costs --> pricing --> Define & Assign pricing procedures.
    4.4 Shipment cost settlement: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation -->Shipping costs --> settlement.
    a.Assign purchasing data
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation -->Shipping costs --> settlement --> Assign purchasing data.
    b. Automatic determination of CO assignments: -
        Menu path: SPRO --> IMG --> Logistics execution --> Transportation --> Shipping costs --> settlement --> Automatic determination of CO assignments.
    I hope it will help you,
    Regards,
    Murali.

  • Materialized View Refresh; Process Flow

    I was wondering if anyone has used process flow to refresh materialized view;
    I am trying to use a process flow for this i.e. run something similiar to below
    EXECUTE dbms_refresh.refresh('"ODW_SRC"."MV_SERVICE_DAILY_AUDIT"');
    I am trying to avoid using DB scheduler because I want to make sure process flow doesn't clash with update of materialized view causing possible conflict of longer than expected job run time goes into refresh window.
    I am assuming I could use a transformation and build it out; but I was wondering if there is an easier way in just executing this one line ... any idea's
    Thank you in advance for your help

    Sorry, I think the OWB term is post mapping process, its actually an operator in an OWB mapping where you can add a procedure call for example. The procedure can do pretty much what it wants.
    Cheers
    David

  • Material creation process in SRM-MDM

    Dear All,
    I am new to SRM. Please correct me about material creation procedure in SRM if I am wrong:
    Normally in classic/extended classic scenario, material first created in MM and then it replicated to SRM. Base on configuration setting for number range, system either create the product ID same as material number number in SRM when it replicated into SRM. In final steps, the product information will upload into MDM either XI integration or manually via excel upload.
    My question:
    + Is it possible to automatic create product without XI via T.Code - MDMGX in MDM.
    + If the replicated product ID of SRM is different then MM material number, which number we should consider for creating product
       MDM.
    Thanks in advance.
    BR
    Jennifer

    Hi Jennifer,
    Answer1) You can only replicate Product Groups, Currencies and Unit of Measures through t-code MDMGX. XI/PI is required for Contract and Product Catalogs.
    Answer 2) If the replicated product ID of SRM is different then MM material number, you should enter MM material number and in External Web Service Configuration for that internal catalog, uncheck  "Do not check Product" indicator so that SRM will not check the Product ID and when item goes to backend system, it will have correct MM material number.
    Thanks,
    Anshuk Saxena

  • URGENT: Oracle Workflow Error: API-10020 on Creation of OWB Process Flows

    I am trying to use Oracle Workflow to create Process Flows, in order to link together various mappings and components in Oracle Warehouse Builder. However, in the process flow editor window when I attempt to drag an object such as a mapping onto the editor panel, I get an error message stating the below:
    API-10020: Unable to determine if the map is a PLSQL or SQLLDR map, please correct the map or choose another map.
    All my maps are in PLSQL, and the language setting is set to this. I have tried modifying the langauge settings to see if it makes a difference but with no luck. My colleague believes this is a known bug in Oracle Workflow and there is a patch available to correct it.
    Can anyone help with this query please? Thank you for your time.

    In some versions of OWB (10.1, 10.2) The mapping property will display PL/SQL, but will actually be set to NULL in the repository (which will cause PL/SQL to be displayed as default).
    The fix is easy enough: in the developer navigator, right-click on the mapping and go to configure and set the generation language first to something other then PL/SQL (you should get an error) and then place it back to PL/SQL. This should force the GUI to reset the parameter.
    Alternatively, use OMB*Plus:
    OMBALTER MAPPING 'MAPPINGNAME' SET PROPERTIES \
    (GENERATION_LANGUAGE) VALUES ('PLSQL');
    Good Luck,
    Robbert

  • Ways of creating contract and process flow of contracts

    hi friends
    ways of creating contract and process flow of contracts
    thanks for ur help
    regards
    krishna

    hi,
    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.
    Contracts can take the following forms:
    Quantity contracts
    Use this type of contract if the total quantity to be ordered during the validity period of the contract is known in advance. The contract is regarded as fulfilled when release orders totaling a given quantity have been issued.
    Value contracts
    Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value. The contract is regarded as fulfilled when release orders totaling a given value have been issued.
    You can also set up corporate buying contracts with your vendors. These are valid for all plants and company codes within a client (see Centrally Agreed Contract).
    You can create a contract as follows:
    Manually
    You enter all data relating to the contract manually.
    Using the referencing technique
    As reference document (the document you copy from), you can use:
    Purchase requisitions
    RFQs/quotations
    Other contracts
    CREATION OF CONTRACT MANUALLY:
    Choose Outline agreement --> Contract --> Create(ME31K)
    The initial screen appears.
    Enter the necessary data. If you make any specifications under the group heading Default data, this data will appear as the default data in each item.
    In the Agreement type field, specify whether you are creating a quantity or value contract, for example.
    Press ENTER .
    The header data screen appears.
    Enter the contract validity period. Check the other fields on this screen and make any necessary changes (e.g. the terms of payment) and define the header conditions.
    Press ENTER .
    The item overview screen appears.
    On this screen, enter the information for each item (material number, target quantity, price, receiving plant, or account assignment, etc.) using the same procedure as with purchase orders.
    Material without a master record: leave the field for the material number empty and enter the following:
    u2013 Short description of the relevant material or service in the Short text field
    u2013 Material group to which the material belongs, in the Material group field
    u2013 Account assignment category
    You can enter u (unknown) or the category of an account assignment.
    u2013 The target quantity and the order unit
    If you specify an account assignment category other than U (field A), you must enter the relevant account assignment data for the item. To do so, choose Item ® Account assignments (see also Account Assignment).
    If necessary, review the details for each item. Select the item(s) to review. Then select Item -> Details.
    Enter the desired conditions.
    Enter further text for the item if any additional instructions to the vendor or Goods Receiving are necessary. Choose Item -> Texts -> Text overview.
    Save the contract.
    Hope it helps..
    Regards
    Priyanka.P
    AWARD IF HELPFULL
    Edited by: Priyanka Paltanwale on Aug 25, 2008 7:20 AM

  • PPT on SD process flow

    Hi guys am in need of help from u
    am not so clear about the SD process flow
    can anyone pls send me a PPT on SD process flow
    to my email id:- (<REMOVED BY MODERATOR>).
    thanking u in advance..
    Regards
    Jino.

    Sales Organization   :
    Responsible for:
    •     Distribution of goods and services
    •     Negotiating Sales Conditions
    •     Product Liability and rights of recourse
    •     A sales organization is uniquely assigned to a company code
    •     Master data’s are separately maintained for a sales organization
    •     All items in the Sales and Distribution document belong to a sales organization
    Distribution Channel:
    Means through which products and services reach the customer 
    A distribution channel:
    •     Defines responsibilities
    •     Helps in achieve flexible pricing
    •     Differentiate Sales statistics
    Division:
    •     A division is used to group products and services.
    •     A division represents a product line.
    Sales Area:
    A Sales area is a combination of
    •     Sales organization
    •     Distribution Channel
    •     Division
    Each Sales and distribution document is assigned exactly to one sales area.
    A sales area can belong to only  one company code.
         Sales Organization
         Distribution Channel
         Division
                     Sales Area
    Plant and Storage Location:
    •     A Plant is a location where stock is maintained
    •     Plant and storage location are used by all logistic area of R/3 System
    •     A Plant is uniquely assigned to a company code
    Shipping point:
    •     Shipping point is the highest level of organizational unit in shipping
    •     Each outbound delivery is processed by one shipping point
    •     Shipping points are assigned to a plant
    •     More than one shipping point can be assigned to a plant
    Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
    A Standard sales transaction has the following flow:
    Inquiry
    Quotation
    Order
    Delivery
    Billing
    The customer order management cycle begins with pre-sales activities.
    A standard order in SAP contains:
    •     Customer and material info
    •     Pricing conditions
    •     Delivery dates and quantities
    •     Shipping info
    •     Billing Info
    Inventory sourcing in SAP is taken care by
    •     Availability check
    Shipping in SAP supports
    •     Outbound delivery creation
    •     Picking
    •     Packing
    •     Post Goods Issue
    Billing in SAP supports
    •     Creating invoices for products and services
    •     Creating credit and debit memo
    •     Cancel previously posted billing documents
    •     Automatically transferring billing documents to accounting
    When a billing document is created for a sales order we
    •     Credit the sales revenue account
    •     Debit the customer receivables account
    Sales Document
    A sales document is grouped into three structures
    •     Header
    •     Item
    •     Schedule Line
    Outbound delivery
    A delivery document is grouped into two structures
    •     Header
    •     Item
    Several orders can be grouped into same outbound delivery if they have same
    •     Shipping point
    •     Delivery date
    •     Ship-to- address
    Picking
    •     A transfer order is created for an outbound delivery
    •     A transfer order is created for a warehouse number
    Post Goods Issue
    When PGI is done the system
    •     Updates the quantity in inventory management and delivery requirements in materials planning
    •     Generates additional documents for accounting
    •     Adds the delivery to the billing due list
    •     Updates status in sales documents
    Billing
    We can group deliveries into single billing document if the deliveries have same
    •     Billing date
    •     Payer
    •     Destination Country
    The effects of billing are
    •     Debit on the customer receivables account and credit on sales revenue account is created
    •     Sales information system
    •     Sales statistics is updated
    Master data in SAP
    SAP SD has got the following main masters:
    •     Customer master
    •     Material master
    •     Condition master
    •     Output master
    •     Customer material information master
    Customer master
    General Data                                         Sales Area Data          Company Code data
    Tab pages                                              Tab pages                                      Tab pages
    Address     Order             Accounting
    Control data                                              Shipping               Payment
    Payment terms                                          Billing               Correspondence
    Marketing                                                   Partner functions                Insurance
    Unloading points
    Export data
    Contact persons
    The chart above shows detail on three main areas of customer master and the tab pages found under each area.
    Material Master is maintained in different views and important views of sales and distribution are
    •     Basic data 1
    •     Sales Org 1
    •     Sales Org 2
    •     Sales : Gen/Plant
    •     Foreign Trade
    •     Sales text
    Sales document in Sales and distribution mainly controls:
    •     Number range
    •     Item No increment
    •     Reference mandatory
    •     Item division
    •     Read info record
    •     Document pricing procedure
    •     Incomplete messages
    •     Alternative sales documents
    •     Delivery block
    •     Billing block
    •     Immediate delivery
    •     Delivery type
    •     Billing type
    •     Proposed delivery date
    •     Lead time for delivery
    •     Proposed pricing date
    Plant determination in Sales and distribution:
    To determine the plant in an order the system checks the master in the following order:
    a)     Customer material info. record of the sold-to –party
    b)     Customer master record of the ship-to-party
    c)     Material master record of the material
    Shipping point determination
    The following rule is used in determining shipping point in a sales order   :
    Plant + Shipping condition (Sold-to-Party) + Loading group                  Shipping point
                                                          Maintained in Material master Gen: Plant data
    Route determination
    Route determined using the following rule in Sales and Distribution (SAP)
    Departure Zone of Shipping Point
    +
    Shipping condition (Sold-to-Party)
    +
    Transportation Group (Material master)
    +
    Transportation Zone (Ship-to-Party)
    Route
    Delivery scheduling:
    As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
    •     Material availability date
    •     Transportation planning date
    •     Loading date
    •     Goods Issue date
    •     Delivery date
    Availability Check in SAP:
    •     Availability check is carried out at item level for a plant
    •     Availability check is done on the material availability date
    •     If material availability date is in the past the forward scheduling is done, if not backward  scheduling is done.
    Item category determination in the order:
    Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
    Sales document type
    +
    Item category group (Material master)
    +
    Item usage
    +
    Item category of higher level item
    Item category of the item
    Item category in a sales document mainly controls the following
    •     Relevance for billing of an item
    •     Billing block
    •     Pricing relevance
    •     Business data relevance item
    •     Schedule line allowed
    •     Item relevant for delivery
    •     Returns
    •     Determine cost
    •     Credit active
    •     Incompletion procedure
    •     Partner determination procedure
    •     Structure scope (relevant for bill of material explosion)
    •     Value contract material
    •     Contract release control
    Schedule line category:
    Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
    Item category + MRP type(Material Master)         Schedule line category
    Schedule line category mainly controls:
    •     Delivery Block
    •     Movement type
    •     Item relevant for delivery
    •     Req/Assembly
    •     Availability
    •     Product Allocation
    Copy Control:
    Copy control is normally set for
    •     Header
    •     Item
    •     Schedule line  levels
    To control copying procedure we have
    •     Data transfer routines
    •     Copying requirements
    •     Switches
    Pricing Procedure determination:
    Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
    The major factors taken into consideration for pricing procedure determination is:
    Sales area
    +
    Customer Pricing procedure(Customer Master –Sales area data)
    +
    Document Pricing Procedure(Sales Document Type)
    Pricing Procedure
    What are the components of pricing procedure?
    How is  that a person should work on Pricing Procedure?
    To start with first
    Define a Condition table:
    What is a condition table?
    A table where the key fields are data combinations for which messages are triggered (and offered for processing).
    For each data combination, there is a condition record in the table. The data part contains the actual message.
    As mentioned above a condition table is a table which carries key fields for picking up the prices.
    Define Access Sequences
    The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
    For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
    Recommendation
    •     If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
    •     Do not change access sequences contained in the standard SAP R/3 System.
    Actions
    1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
    2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
    3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
    4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
    Example
    In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
    Define Condition Type
    A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
    Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
    You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
    You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
    Note
    •     The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
    Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
    •     You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
    Recommendation
    •     If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
    •     Do not change the condition types which are contained in the standard SAP R/3 System.
    Actions
    1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
    2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
    Specify an alphanumeric key which can have up to 4 digits, and a textual description.
    Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
    3. Maintain the detail screen of the condition type.
    You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
    In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
    Define Pricing Procedures
    The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
    A standard pricing procedure is defined in the standard SAP system.  It contains conditions most commonly used.  These include material prices, discounts, and surcharges, such as freight, or tax.
    SAP Recommendation
    •     Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
    •     Do not change the pricing procedures contained in the standard SAP R/3 System.
    Actions
    1. Create new pricing procedures by copying a similar pricing procedure.
    o     Specify a key with up to 6 characters and a description.
    o     For a procedure, specify the condition types in the sequence of their usage.
    Maintain the lines of the pricing procedure
    2. Afterwards define the customer determination procedures for determining the procedure.
    3. Define the document pricing procedures for determining the procedure.
    4. Assign the procedure to the sales document types and billing types.
    5. To determine the procedure, define the allowed combinations of:
    o     Sales area
    o     Customer pricing  procedure
    o     Document pricing procedure
    o     Pricing procedure
    Shipping:
    The basis for shipping is delivery.
    Delivery document controls the following in deliveries
    •     Number range
    •     Item no increment
    •     Storage location rule
    •     Route determination
    •     Text determination
    •     Delivery split
    •     Gen. packing material / item
    •     Order required
    Delivery item category controls:
    •     Check min delivery
    •     Availability check
    •     Relevant for picking
    •     Storage location required
    •     Determine storage location
    •     Automatic batch determination
    •     Text determination procedure
    Billing:
    Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
    Billing document has got the following structure:
    •     Header
    •     Item
    Billing documents mainly control:
    •     No. range
    •     Posting block (Controls posting to accounting)
    •     Relevant for rebate
    •     Account determination procedure
    •     Account determination recon account
    •     Account determination pay.cards
    •     Output determination procedure
    Account Determination in SAP
    Account determination in SAP-SD happens with the following rule
    Sales Organization
    Chart of Accounts
    Account assignment group –Customer
    Account assignment group-Material
    Account Key
    G/L account on which the postings  has to happen.
    CHeers!!!

  • Mm process flow

    hi
    will any body give a complete life cycle flow of material management module or product life cycle management of mm module
    regards
    brijesh

    <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 underdeliveries 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>Common Tables used by SAP MM:</b>
    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
    <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>Also please check this links.</b>
    http://www.sapgenie.com/sapfunc/mm.htm
    http://www.sap-basis-abap.com/sapmm.htm

  • QM process flow

    Hi,
    Can any one explain the general process flow of Qm module.I have no idea on the Qm management.
    Thanks.
    -Santhosh

    Dear Santhosh,
    In Quality Management following are the broad level activities need to be conducted :
    1) Incoming Inspection : This is for raw materials, or other input materials  on which the quality of final product is dependent. (For activating this, in QM material master you need to define '01' inspection type)
    2) In process Inspection :  This is the inspection in - process meaning in house inspection during the process inside. (For activating this, in QM material master you need to activate '03' inspection type)
    3) Final Inspection or out going inspection  : This is inspection of final products or finished product. This is to ensure that correct quality product is going to customer. (For activating this, in QM material master you need to activate '04' inspection type)
    Apart from this you can do inspections at vendor, predespatch insp, Recurring insp ,competitors sample evaluation etc.
    For doing all this in terms of SAP you need to do:
    1) Quality Planning : Defining of masters like Master Inspection characteristics, Inspection method, sampling scheme, sampling procedure, catalog selected sets and code groups, then assign all these Masters  in Inspection  Plan . also assigning QM view to materiel master so that inspections are activated.
    2) Quality Inspection : Inspection lot creation , result recording, defect recording  and completing the lot by giving user decesion.
    3) Quality control : This include raising notification, SPC, using dynamic modification, quality certificates etc.
    4) Test equipment management : This includes Calibration of instruments
    5) Control in logistics : This include Control in Procurement, Production and sales & distribution
    you can get all details of these processes at
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/a6/df293581dc1f79e10000009b38f88/frameset.htm
    Best Regards,
    Shekhar

  • PS Process flow

    Hi Folks,
    Actully im a technical consultant. Now I want to study Projrct systems.
    tell me the process flow of the Project systems. And also I need important transactions and Master tables.
    Please anybody guide me.
    Thanks for your valuable time,
    Points will be appreciated.

    Project Systems:
    1. Project Structure Creation
    Creation of Project Definition, WBS Element, Network, Activity(Internal, External, Cost, Service)  (Tcode: cj20n)
    2. Planning:(Tcode: cj20n)
    Date Plannnig
    Material Planning
    Service Planning
    3. Execution (Tcode: cj20n)
    Change Project Status / Project Release
    (status change CRTD-REL)
    Confirm Activities (status change REL-CNF)
    4. Reports:
    Progress: cne5
    Plan/Act/Variance s_alr_87013432, s_alr_87013542
    5. Project Closing
    Settlement (Tcode: cjb2, cj88)
    Close Project (status change CNF-TECO-CLSD) (Tcode: cj20n)
    75% of work is completed in cj20n - Project Builder
    Main Tables:
    PROJ, PRPS, AFCV, etc...
    Happy Learning
    SSanjay

  • Process Flow Diagram

    Can someone provide me with a process flow diagram and the step for creation of returnable packaging ?
    Thanks
    Logi

    Hi,
    For returnable pacaging,you have to create a material with "LEIH" material type.
    Pls go through the following link for process flow daigram:
    [Process flow for LEIH material type|http://help.sap.com/bp_bl603/BBLibrary/Documentation/155_Scen_Overview_73_EN_PE.ppt]
    Pls go through the following link for process flow of shipping:
    [Process flow of shipping|http://help.sap.com/bp_bl603/BBLibrary/Documentation/107_Scen_Overview_EN_US.ppt#488,1,Sales Processing Using Third Party (with Shipping Notification) SAP Best Practices Baseline Package  (U.S.)]
    Hope this is what you are looking for.And this will help you also.
    Regards,
    Krishna.

  • WM process flow diagram

    Can anybody help me to get process flow diagram of any standard WMS in SAP?
    I appriciate your help
    Thanks,

    HI ,
    Refer the general scenario followed most commonly in WM,
    A) IN MM At the time of good receipt MIGO
    1.creation of transfer requirement takes place. Material Goes to Interim Storage type (902)
    2. Transfer order from TR is created ( we get destination storage type) --  In LT04 or LT06
    3. Confirmation of TO.(Put away completed )     In LT12
    B) IN PP
    1. Requirement we get from MD11,MD04,CO01.(staging , BOM Explosion etc.)
    this time Generally TR, will be created Automatically( As per setting).
    With LB10 TR to TO
    TO will be confirmed in staging process.(Quantity of picked materials will be reduced )
    (Hear the raw material will be consumed. & TR for finished material will be created.)
    With LB10 we can perform creation of TO.
    TO for finished material will be confirmed when it will placed in the destination Bin.
    Hear we will get the Finished good in the Unrestricted stock.
    C)IN SD.
    Creation of sale order: VA01
    Creation of Outbound deliveryu2019s TO. VL01
    TO confirmation after reaching to destination.LT03 then LT12 to confirm.
    Dev.

  • Process flow for SD

    Hi All,
    Could you pls send me the process flow PPT for SD @ the following e-mail ID.  [email protected]
    Regards
    Nishant

    SD flow 1. Enquiry and quotation 2. Sales order (Which Customer, from which plant, delivery payment terms, quantity and rate) 3. Delivery (With out post goods issue – no owner. In with out PGI no account document only material document ex: - Factory plant to port or with post goods issue- with owner. In this PGI accounting transaction done, ex: - Factory plant – port – customer. Entry is Invoice /decrease in stock Dr to in finished goods.
    •     SD Integration steps: - 1. Define region 2. Define sales organization 3. Determine distribution channel 4. Define shipping point 5. Assign sales organization to company code 6. Assign distribution channel to sales organization 7. Assign division to sales organization 8. Setup sales area 9. Assign sales org- distribution channel – plant 10. Define rules by sales area 11. Assign shipping point to plant 12. Define pricing procedure determination 13. Define tax determination rules. Testing: - 1. Creation of GL master sales local (Go29 revenue) 2.  Assign GL accounts (NKOA) 3. Setup partner determination 4. Assign shipping points. User level 1. Creation of SD customer master (XD01)). And MM: - Movement types: -101 material receipt, 201 issue to cost center, 261 issue to order, 521 production receipts with out production order, 561 opening stocks, 601 delivery.

Maybe you are looking for