Minimum Delivery Percentage

Hi,
In vendor evaluation , how can i set Minimum Delivery Percentage and Standard Delivery Date Variance for subcriterion  "Adherence to confirmation date" and "On-Time Delivery Performance"?
regards
Nbanu

Hi,
Go to SPRO > MM > Purchasing > Material Master > Define Purchasing Value Keys > Here under "Vendor Evaluation" Subscreen, maintain following;
Min.Del.Qty %
StdDelDtVar
Then assign the Purchasing Value Key in the "Purchasing: view of material master.
Minimum delivery quantity (percentage): - Indicates the percentage of the order quantity that counts as the minimum quantity to be delivered.
Use: - Here you enter the minimum percentage of the PO quantity that must be delivered in order for the goods receipt to be included in the vendor evaluation.
In this way, you can prevent a vendor from receiving a good score for a punctual delivery, where the quantity delivered was insufficient.
Dependencies: - This value is applied if you have not set the indicator Minimum delivery quantity/stand. delivery time variance from material  - i.e. if no value from the material master record (purchasing value key) is to be used or if the relevant field in the material master record has not been maintained.
Standardizing value for delivery time variance: - Value in days that specifies how many days variance from the planned delivery date are to count as a 100% variance.
Use: - If you enter a value, the system evaluates the absolute variance in days between the planned delivery date and the actual goods receipt for all materials in the same way.
In the process, the actual (absolute) variance in days is converted into a relative variance and the number of days by which a delivery varies is set in relation to the standardizing/relativizing value.
Dependencies: - This value is applied if you have not set the indicator "Minimum delivery quantity/stand. delivery time variance from material" - that is to say, if no value from the material master record (purchasing value key) is to be used or if the relevant field has not been maintained in the material master record.
If you make no entry, the system calculates the value via the firm/trade-off zones in the case of scheduling agreements and via the order date and statistics-relevant delivery date in the case of purchase orders.
If you do not maintain the minimum delivery quantity, each goods receipt is included in the computation of scores irrespective of the quantity delivered.

Similar Messages

  • Minimum delivery quantity

    dear gurus
    I have requirement from my client of delivery in multiples.
    For example: 1 cartoon = 50 ea for material
    So the user books the order of 210 ea of material.
    Now when he creates a delivery, and if they pick 210 ea then the system should through error.
    I have maintained minimum delivery quantity & even tried delivery unit as 50. but still no sucess.
    Kindly help.
    Regards

    Dear EKS EKS
    In the material master if the delivery unit is maintained as 30 in sales org data 1 tab
    during order placing if in the multiples of 30 or 60 or 90 only should be used
    If you place order for 100 then system will give a warning message and you can ignore that and enter
    If you want a avoid this go to OVAH and message no V4 and 081 change from warning to error and save
    Now the sales order should be in multiples of 30 only like 60,90,120,150 etc
    If any other is given you will get error message
    Please try this and it will work for you
    In your case you have to enter 50 ea as delivery unit in material master in sales org data 1 tab
    Regards
    Raja

  • Delivery quantity is less than minimum delivery quantity

    Hello Experts,
    I received an error log "Delivery quantity is less than minimum delivery quantity 20 EA" when I first tried to create delivery using sales order. Well the reason for the error log was because of the CMIR record maintained in the system with min quantity set as 20 (Ordered Quantity = 10 in the sales order).
    After realization, I did delete the CMIR record and then tried to create delivery for the same sales order but I'm still receiving the same error log "Delivery quantity is less than minimum delivery quantity 20 EA".
    How can I overcome this issue.
    Any help will be highly appreciated.
    Thanks in advance

    Hi Hegal,
    Thanks for your quick response.
    But I've one more question regarding the same error log.
    Initially the Ordered Qty was 10 and CMIR record was with 20 and it gave me a error log (which works as expected).
    I deleted CMIR record and it still gives the same error log "Delivery quantity is less than minimum delivery quantity 20 EA".
    Later when I increased the sales order quantity to 20 or more, I'm not getting any error log even though CMIR record is not maintained in VD52. This is something which is unusual and I feel there is some place in the file where this information is stored and later compared against the sales order quantity.
    This is something which I would like to know for my own understanding.
    I did ask user to delete the sales order line item and reenter the same product and now everything is working as expected.
    Thanks

  • Total delivery percentage available

    Hi,
    my requirement is to display all the deliveries for stock shipment report based on a plant and planned shippong date. For each of the deliveries displayed system has to calculate all the quantity of Total delivery percentage available. How I can write the functional spec for this requirement.
    thanks and regards
    venkat reddy

    Create a PO without tick GR-Bsd IV, suppose I have created PO with qty 20 and rate 1 INR and give freight 50 INR (Fixed Amount)..
    Then I have done partial GR for qty 5. My freight amount booked as 12.5 INR (for partial GR)
    Then I have gone for MIRO..
    Here select Goos/Service item + Planned delivery cost.
    Enter the PO, you can see two line items appear..
    One for goods and one for freight...
    Goods will come as qty 5 and amount 5 INR and Freight will come as qty 5 and amount 12.5 INR.
    Just change the freight qty and amount as 20 and 50 INR.
    Then post the MIRO, you can see your total freight will be booked to vendor..
    Now again do GR for qty 2, at that time your freight amount will booked as 5 INR.
    Then when you will go for MIRO, you can see only the GR item, Freight qty and amount will not come at the time MIRO..
    (Note : I have told the scenario as per my previous screen shot)

  • Minimum Delivery Value

    Hi All,
    Just some advice really. I am busy with trying to improve the MDV process, by adding a MDV surcharge condition, that will be applied if the delivery value is below the MDV threshold .
    Example :
    MDV Threshold condition = 300€ , MDV surcharge = 30€
    Order A 100€
    Order B 150€
    Both grouped in a delivery ( Value 250€ ), as it is less than 300€ , then create the delivery and add the surcharge 30€, the customer will then be charged for 280€=(250€+30€)
    So besides just creating an MDV surcharge condition( ZMIZ ) and applying it to the delivery pricing procedure (ZVP000) which already has the MDV condition (ZMDV), this will have effects in billing. Making sure the surecharge is carried over to billing.
    Is it a case of account determinations and assigning the condition to an account key?
    Basically what are the settings I should think about with billing?
    Regards
    TV

    Hi,
    This can be done mainly by the calculation type and basic config of the condition type.
    First you need to enter  that surcharge condition that has to be invoked with the inbuild condition that( if the total delivery doc value equals or exceeds 2500 then this condition will not be reflected) .
    I guess this should be at the header level.
    Second the basis prerequistes condition has to be set in (requirement )delivery to ensure the visbility of this condition type may be in the form of routine with the logic:
    That if the total delivery value net value (NETWR)in KOMP table gets updated with the value less than a certain amount then this condition type will get invoked and also display a second condition type with surcharge rate.
    regards,
    Siddharth.

  • PO-   Contract release Qty  not matching with  minimum delivery qty

    Hi  expert,
    I have a requirement   , there  is a  business process  where my   client need  to  replenish the fuel tank every two days . The tank capacity is 100,000 gallon   and supplier supply the fuel  of tank  11500 gallon every time.
    To map this process, we have set annual contact for   1000,000 gallon, We have  set our reorder pint as  50,000 gallon and lot size as HB  .  We have also maintained  alternate unit of measure as 1TRUCK= 11500 gallon.
    When the stocks  falls below 50,000 system create PR and auto PO generate  for  short  qty.
    But we need the short qty should multiple of deliver qty  I,e  11500 x3   = 34,500  not 40,000 gallon which calculate by system
    Am I missing something?
    Thanks
    Dilip

    No I have not maintained  rounding profile. The  qty i,e 40000 requirement calculation based  on  ( Max stock i,e Tank capacity  90000  --  50000 as Consumption qty)= Balance 40,000 qty PR generate  through MRP
    My requirement , System should generate PR for 11500 X3= 34500  Qty instead of  40,000 Gal
    Could it be possible
    Thanks
    Dilip

  • Delivery rating in vendor evaluation

    Can I know on what logic system calculates the delivery rating, for schedule agreement which has more than one schedule lines.
    Regards,
    M.M

    Dear Magesh,
    This is for On time delivery:
    ===========================================================
    At the time of a goods receipt against a purchase order, the system checks whether the delivery was on time or late:
    GR date - delivery date = date variance
    If the delivery was on time, the system checks whether a minimum delivery quantity is to be taken into account.
    It checks the Minimum delivery quantity/standardizing value for delivery time variance from material indicator.
    – If the indicator has been selected, it checks whether a value has been maintained in the material master record.
    If a value exists, it is used. If no value exists, the value from the Minimum delivery percentage field is used. If there no such value in this case either, goods receipts of fractions of the order quantity are included in the calculation of the score.
    – If the indicator has not been selected, the value from the Minimum delivery percentage field is used. If no value exists, goods receipts of fractions of the order quantity are included in the calculation of the score.
    If the minimum delivery quantity is not reached, the system does not determine a score for the goods receipt.
    If the minimum delivery quantity is reached and the delivery date adhered to, the variance is zero and the system awards the highest points score for the relevant goods receipt.
    If the delivery is not on time, the system calculates the date variance in days and converts it into a percentage variance.
    In the process, the system searches for the standardizing value as follows:
    It checks the Minimum delivery quantity/standardizing value for delivery time variance from material indicator.
    – If the indicator has been selected, it checks whether a value has been maintained in the material master record.
    If a value exists, it is used. If not, the value from the Standardizing value for delivery time variance field is used. If there is no such value in this case either, one of the following values is used:
    – in the case of goods receipts against scheduling agreement releases: the firm zone
    – in the case of goods receipts against purchase orders: the difference between the statistical delivery date and the order date
    – If the indicator has not been selected, the value from the Standardizing value for delivery time variance field is used. If there is no such value, one of the following values is used
    – in the case of goods receipts against scheduling agreement releases: the firm zone
    – in the case of goods receipts against purchase orders: the difference between the statistical delivery date and the order date
    The system then awards the score you defined in Customizing for this percentage variance.
    The new score is then included in the vendor's previous score for the subcriterion. To calculate the new score for the subcriterion from the already existing composite score and this new individual score, the system applies the smoothing factor Date variance defined in Customizing.
    When you run a new evaluation, the system calculates the average of the individual scores for all materials. The result is the vendor's score for "On-Time Delivery Performance".
    If a goods receipt covers several schedule lines, MM Vendor Evaluation performs this calculation for each schedule line.
    This results in more than one score for the single goods receipt. Each of these scores is multiplied by the quantity delivered against the relevant schedule line and is thus weighted by quantity.
    The sum of the weighted points scores is divided by the total goods receipt quantity. The result is the score for this one goods receipt.
    The score for the goods receipt is smoothed and included in the existing score for on-time delivery performance for the vendor
    Adherence to Conf. Date :
    ===========================================================
    1. When a goods receipt is posted for an order item, the system checks whether open inbound deliveries exist for the order item, i.e. inbound deliveries for which no goods receipts have yet been recorded.
    If open inbound deliveries exist, the system checks whether the date previously notified by the vendor has been adhered to or whether the goods receipt date differs from the date thus confirmed:
    GR date - date confirmed by vendor in shipping notification = date variance
    2. If the delivery was on time, the system checks whether a minimum delivery quantity has been defined in Customizing.
    a. If you have not set a minimum delivery quantity, goods receipts representing partial deliveries will also be included in the calculation of the score.
    b. If the minimum delivery quantity is not reached, the system does not determine a score for the goods receipt.
    c. If the minimum delivery quantity is reached and the delivery is on time, the variance is zero. This means that the system awards the maximum score for the goods receipt.
    3. If the delivery date is not in accordance with the notified one, the system calculates the date variance in days and converts it into a percentage variance.
    4. The system then awards the score you defined in Customizing for this percentage variance.
    5. The new score is then merged with the vendor's previous score for the subcriterion. To calculate the new score for the subcriterion from the already existing composite score and this new individual score, the system applies the smoothing factor On-time delivery performance/Timeliness of service provision (defined in Customizing for Vendor Evaluation under Purchasing organization data for Vendor Evaluation).
    6. When you run a new evaluation, the system calculates the average of the individual scores for all materials. The result is the vendor’s score for adherence to the confirmation date.
    If a goods receipt covers several schedule lines, MM Vendor Evaluation performs this calculation for each schedule line.
    This results in more than one score for the single goods receipt. Each of these scores is multiplied by the quantity delivered against the relevant schedule line and is thus weighted by quantity.
    The sum of the weighted points scores is divided by the total goods receipt quantity. The result is the score for this one goods receipt.
    The score for the goods receipt is smoothed and merged with the existing score for adherence to the confirmation date for the vendor.
    Regards,
    w1n

  • Reg: Vendor Evaluation - Criteria "Delivery"

    Hi Gurus,
    I am in process of vendor evaluation in system. Confguration is maintained and I am opting for Automatic vendor evaluation and our interest is in Price and delivery. When I am doing Vendor evaluation in ME61,
    I am getting the automatic values for Criteria "Delivery" and subcriteria  "Price Level" "Price Behavior".
    But incase of delivery I am not getting any values. I checked for settings in confirguration but not able to trace why the delivery vendor evaluation is not happening.
    Pls advice on this.
    Regards,
    Venu

    Hi
    There are some settings like minimum delivery percentage which needs to be fulfilled for calculating score with respect to delivery performance.
    Check the PDF from the link, it gives you more details on how score is been calculated for each criteria and customizing settings
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf
    Regards
    Raja

  • Vendor evaluation delivery rating

    hi,
    Presently working on vendor evaluation.
    i did config. but not getting proper result
    pl note the scenario; ifany body can help.
    a)On time delivery rating (ODR):- ODR is calculated to determine how precisely a vendor has adhered to the specified delivery dates.
      Scoring Procedure:-
    ODR =1 if Goods receipt dateu2264 Specified delivery date
    ODR =0 if Goods receipt date>Specified delivery date
    b)     Quantity Rating (QNR):- QNR is calculated to determine whether a vendor has delivered the quantity specified in the purchase order.
    Scoring Procedure:-
    Quantity Rating Score (QNRS) = _Qty Received/Total qty to be delivered    *100
    QNRS                      QNR
    QNRSu2265100     1
    75u2264 QNRS <100     0.75
    50u2264 QNRS <75     0.50
    20u2264 QNRS <50     0.20
    0u2264 QNRS <20     0
    mainly problem is in spro-purchasingvendor evaluationdefine purchasing org data for vendor evaluation--pointscore
    if anybody can help
    regards

    Hi,
    Computing scores for DELIVERY, minimum delivery percentage and the standardizing value for delivery time variance are taken from the material master record(In purchasing value key) or from the fields : Minimum delivery qty. in percentage and Standard del. time variance fields in Txn: OMGL.
    1. You maintain minimum delivery percentage, if you do not want a vendor to receive a very good scoreif delivered goods on time, but not the exact qty.
    2. You maintain Standard del. time variance, to reate delivery dates variances in days.
    *% variance= (Difference between Statistical delivery date & GR Date)/Standard del. time variance 100.
    Hope this helps!
    Regards,
    Shilpa

  • Standard Delivery Date Variance

    Hi,
    I am doing vendor evaluation. I want to set Minimum Delivery Percentage and Standard Delivery Date Variance for all materials. I know about purchasing value key setting. then i have to maintain for each material.
    My requirement is that I have to set Minimum Delivery Percentage as 20% for all materials and Standard Delivery Date Variance for vendors as 30 days. Where can i set this?
    rewards assured.
    regards
    NBanu

    Hi,
    If you know about the Purchasing Value Key then what is the issue?
    Simply create one Purchasing Value Key and maintain the Minimum Delivery % as 20% and Standard Delivery Time Variance as 30 days and then maintain this Purchase Value Key in "Purchasing" view of all the Materials.
    If you want to do mass maintenance then use transaction MM17
    And to create Purchasing Value Key, go to SPRO > MM > Purchasing > Material Master > Define Purchasing Value Key

  • REGARDING VENDOR QUALITY RATING

    Hi All
    My client wants vendor quality rating
    for this i maintend quality score in clint data maintened score procedure and assing it to inspection type
    define the formula for quality rating in functional modul for Q score procedure
    is this suficient or i m missing some thing pls tell me
    regards
    Sachin

    HI
    endor Evaluation for Purchasing
    Define the weighting keys in SM30 - V_T147J.
    Weighting keys 01 and 02 are defined in the standard system. You combine the following
    weighting shares for the standard main criteria:
    Main criterion     Key 01 Key 02
    Price                   1      5
    Quality                 1      5
    Delivery                1      2
    Gen. service/support    1      1
    Ext. service provision  1      2
    Define the criteria in SM30 - V_T147G - Double click on the line items
    In this step, you define the criteria by which the system computes scores for vendors and
    specify whether the scores for the subcriteria are computed manually, semi-automatically, or
    automatically.
    You can also store your own methods of computation for the scores for subcriteria in the
    form of user exits. The enhancement MM06L001 is available for this purpose.
    Define the scope of list in SM30 - V_T147M - Double click on the line items
    Define Purchasing Organization data for vendor evaluations in transaction OMGL.
    An example :-
    How the system calculates the score for the automatic subcriteria
    "On-Time Delivery Performance"?
    The system uses the statistics-relevant delivery date in the purchase order
    (Items -> Delivery Schedule) and the goods receipt date to calculate date variances.
    You use the statistics-relevant delivery date, for example, if you know that the vendor
    will not deliver the material as scheduled on September 15 but on September 30. Enter the
    delivery date as September 30, but enter the statistics-relevant delivery date as
    September 15.
    In calculating the score for on-time delivery performance, the system will then not use
    the actual delivery date, but the statistics-relevant delivery date. This has a negative
    effect on the score for this goods receipt.
    However, materials planning and control uses the realistic delivery date (September 30)
    which the vendor will actually adhere to.
    The system considers only goods receipts against purchase orders and scheduling agreements
    into stores and the release of GR blocked stock into stores. In the standard system, these
    are the movement types 101 and 105.
    Minimum Delivery Percentage - OMGL in the On-time delivery section
    If you do not want a vendor to receive a very good score if he delivered the goods on time,
    but did not deliver the required quantity, you can maintain a minimum delivery percentage
    in Customizing.
    Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on
    time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is
    not included in the calculation of the vendoru2019s score for on-time delivery performance. So
    that the non-scoring of the on-time delivery performance criterion in this case does not
    bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score
    for quantity reliability. On-time delivery performance is thus always to be seen in
    conjunction with quantity reliability.
    Standardizing Delivery Date Variance  - OMGL in the On-time delivery section
    To rate delivery date variances in days, maintain the Std.del.time var. parameter.
    If you assign a lower standard value, this means that relatively low date variances produce
    high percentage variances. If you set a higher standard value, this results in a relatively
    low percentage variance:
    The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27;
    the statistical delivery date was Nov. 15. There is thus a difference of 12 days.
    The system calculates the percentage variance as follows:
    12 / 20 x 100 = 60
    If the Std.del.time var. parameter had the value 60, the variance would be 20%
    (12 / 60 x 100 = 20).
    If you do not maintain this parameter, the system calculates the delivery time variance via
    the firm zone in the case of scheduling agreements, and via the order date and the
    statistics-relevant delivery date in the case of purchase orders. 
    With regrds
    Yashodhan

  • Kindly suggest me regarding vendor evaluation (me63) score

    Dear Friends,
    I have excuted the report of vendor evaluation but here for Price criteria ( subcriteria) 40,40 are coming and some times it is 46,48 are coming. and for other criteria delivery it is 68,70 like that it is coming. kindly let me know how much is the maximum score for delivery,quality and price. and how it is distributed in standard when i have selected equal weightage
    Regards,
    Saurav

    Dear Friend,
    Kindly go through the below documents,
    Define the weighting keys in SM30 - V_T147J. Weighting keys 01 and 02 are defined in the standard system. You combine the following weighting shares for the standard main criteria: Main criterion Key 01 Key 02 Price 1 5 Quality 1 5 Delivery 1 2 Gen. service/support 1 1 Ext. service provision 1 2 Define the criteria in SM30 - V_T147G - Double click on the line items In this step, you define the criteria by which the system computes scores for vendors and specify whether the scores for the subcriteria are computed manually, semi-automatically, or automatically. You can also store your own methods of computation for the scores for subcriteria in the form of user exits. The enhancement MM06L001 is available for this purpose. Define the scope of list in SM30 - V_T147M - Double click on the line items Define Purchasing Organization data for vendor evaluations in transaction OMGL. An example :- How the system calculates the score for the automatic subcriteria "On-Time Delivery Performance"? The system uses the statistics-relevant delivery date in the purchase order (Items -> Delivery Schedule) and the goods receipt date to calculate date variances. You use the statistics-relevant delivery date, for example, if you know that the vendor will not deliver the material as scheduled on September 15 but on September 30. Enter the delivery date as September 30, but enter the statistics-relevant delivery date as September 15. In calculating the score for on-time delivery performance, the system will then not use the actual delivery date, but the statistics-relevant delivery date. This has a negative effect on the score for this goods receipt. However, materials planning and control uses the realistic delivery date (September 30) which the vendor will actually adhere to. The system considers only goods receipts against purchase orders and scheduling agreements into stores and the release of GR blocked stock into stores. In the standard system, these are the movement types 101 and 105. Minimum Delivery Percentage - OMGL in the On-time delivery section If you do not want a vendor to receive a very good score if he delivered the goods on time, but did not deliver the required quantity, you can maintain a minimum delivery percentage in Customizing. Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is not included in the calculation of the vendoru2019s score for on-time delivery performance. So that the non-scoring of the on-time delivery performance criterion in this case does not bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score for quantity reliability. On-time delivery performance is thus always to be seen in conjunction with quantity reliability. Standardizing Delivery Date Variance - OMGL in the On-time delivery section To rate delivery date variances in days, maintain the Std.del.time var. parameter. If you assign a lower standard value, this means that relatively low date variances produce high percentage variances. If you set a higher standard value, this results in a relatively low percentage variance: The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27; the statistical delivery date was Nov. 15. There is thus a difference of 12 days. The system calculates the percentage variance as follows: 12 / 20 x 100 = 60 If the Std.del.time var. parameter had the value 60, the variance would be 20% (12 / 60 x 100 = 20). If you do not maintain this parameter, the system calculates the delivery time variance via the firm zone in the case of scheduling agreements, and via the order date and the statistics-relevant delivery date in the case of purchase orders.
    http://www.sap-img.com/mm009.htm

  • Vendor Evaluation in MM

    Hi All
    Can u tell me the Detail  process of Vendor Evaluation in MM
    Regards
    Manju

    HI,
    Vendor Evaluation for Purchasing
    Define the weighting keys in SM30 - V_T147J.
    Weighting keys 01 and 02 are defined in the standard system. You combine the following
    weighting shares for the standard main criteria:
    Main criterion Key 01 Key 02
    Price 1 5
    Quality 1 5
    Delivery 1 2
    Gen. service/support 1 1
    Ext. service provision 1 2
    Define the criteria in SM30 - V_T147G - Double click on the line items
    In this step, you define the criteria by which the system computes scores for vendors and
    specify whether the scores for the subcriteria are computed manually, semi-automatically, or
    automatically.
    You can also store your own methods of computation for the scores for subcriteria in the
    form of user exits. The enhancement MM06L001 is available for this purpose.
    Define the scope of list in SM30 - V_T147M - Double click on the line items
    Define Purchasing Organization data for vendor evaluations in transaction OMGL.
    An example :-
    How the system calculates the score for the automatic subcriteria
    "On-Time Delivery Performance"?
    The system uses the statistics-relevant delivery date in the purchase order
    (Items -> Delivery Schedule) and the goods receipt date to calculate date variances.
    You use the statistics-relevant delivery date, for example, if you know that the vendor
    will not deliver the material as scheduled on September 15 but on September 30. Enter the
    delivery date as September 30, but enter the statistics-relevant delivery date as
    September 15.
    In calculating the score for on-time delivery performance, the system will then not use
    the actual delivery date, but the statistics-relevant delivery date. This has a negative
    effect on the score for this goods receipt.
    However, materials planning and control uses the realistic delivery date (September 30)
    which the vendor will actually adhere to.
    The system considers only goods receipts against purchase orders and scheduling agreements
    into stores and the release of GR blocked stock into stores. In the standard system, these
    are the movement types 101 and 105.
    Minimum Delivery Percentage - OMGL in the On-time delivery section
    If you do not want a vendor to receive a very good score if he delivered the goods on time,
    but did not deliver the required quantity, you can maintain a minimum delivery percentage
    in Customizing.
    Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on
    time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is
    not included in the calculation of the vendoru2019s score for on-time delivery performance. So
    that the non-scoring of the on-time delivery performance criterion in this case does not
    bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score
    for quantity reliability. On-time delivery performance is thus always to be seen in
    conjunction with quantity reliability.
    Standardizing Delivery Date Variance - OMGL in the On-time delivery section
    To rate delivery date variances in days, maintain the Std.del.time var. parameter.
    If you assign a lower standard value, this means that relatively low date variances produce
    high percentage variances. If you set a higher standard value, this results in a relatively
    low percentage variance:
    The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27;
    the statistical delivery date was Nov. 15. There is thus a difference of 12 days.
    The system calculates the percentage variance as follows:
    12 / 20 x 100 = 60
    If the Std.del.time var. parameter had the value 60, the variance would be 20%
    (12 / 60 x 100 = 20).
    If you do not maintain this parameter, the system calculates the delivery time variance via
    the firm zone in the case of scheduling agreements, and via the order date and the
    statistics-relevant delivery date in the case of purchase orders.
    You can also refer http://help.sap.com/saphelp_47x200/helpdata/en/8d/b97e4f414511d188fc0000e8322f96/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf
    Thanks & Regards,
    Kiran

  • Vendor Evaluation Automatically

    Dear all
            Kindly sent the related Document both configuration & end user details for Vendor evaluation.
    Urgent Please.

    Hi,
    Vendor Evaluation for Purchasing:
    Define the weighting keys in SM30 - V_T147J.
    Weighting keys 01 and 02 are defined in the standard system. You combine the following
    weighting shares for the standard main criteria:
    Main criterion     Key 01 Key 02
    Price                   1      5
    Quality                 1      5
    Delivery                1      2
    Gen. service/support    1      1
    Ext. service provision  1      2
    Define the criteria in SM30 - V_T147G - Double click on the line items
    In this step, you define the criteria by which the system computes scores for vendors and
    specify whether the scores for the subcriteria are computed manually, semi-automatically, or
    automatically.
    You can also store your own methods of computation for the scores for subcriteria in the
    form of user exits. The enhancement MM06L001 is available for this purpose.
    Define the scope of list in SM30 - V_T147M - Double click on the line items
    Define Purchasing Organization data for vendor evaluations in transaction OMGL.
    An example :-
    How the system calculates the score for the automatic subcriteria
    "On-Time Delivery Performance"?
    The system uses the statistics-relevant delivery date in the purchase order
    (Items -> Delivery Schedule) and the goods receipt date to calculate date variances.
    You use the statistics-relevant delivery date, for example, if you know that the vendor
    will not deliver the material as scheduled on September 15 but on September 30. Enter the
    delivery date as September 30, but enter the statistics-relevant delivery date as
    September 15.
    In calculating the score for on-time delivery performance, the system will then not use
    the actual delivery date, but the statistics-relevant delivery date. This has a negative
    effect on the score for this goods receipt.
    However, materials planning and control uses the realistic delivery date (September 30)
    which the vendor will actually adhere to.
    The system considers only goods receipts against purchase orders and scheduling agreements
    into stores and the release of GR blocked stock into stores. In the standard system, these
    are the movement types 101 and 105.
    Minimum Delivery Percentage - OMGL in the On-time delivery section
    If you do not want a vendor to receive a very good score if he delivered the goods on time,
    but did not deliver the required quantity, you can maintain a minimum delivery percentage
    in Customizing.
    Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on
    time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is
    not included in the calculation of the vendor’s score for on-time delivery performance. So
    that the non-scoring of the on-time delivery performance criterion in this case does not
    bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score
    for quantity reliability. On-time delivery performance is thus always to be seen in
    conjunction with quantity reliability.
    Standardizing Delivery Date Variance  - OMGL in the On-time delivery section
    To rate delivery date variances in days, maintain the Std.del.time var. parameter.
    If you assign a lower standard value, this means that relatively low date variances produce
    high percentage variances. If you set a higher standard value, this results in a relatively
    low percentage variance:
    The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27;
    the statistical delivery date was Nov. 15. There is thus a difference of 12 days.
    The system calculates the percentage variance as follows:
    12 / 20 x 100 = 60
    If the Std.del.time var. parameter had the value 60, the variance would be 20%
    (12 / 60 x 100 = 20).
    If you do not maintain this parameter, the system calculates the delivery time variance via
    the firm zone in the case of scheduling agreements, and via the order date and the
    statistics-relevant delivery date in the case of purchase orders.
    regards,
    sasi

  • Source inspection configuration

    dear all,
    what is source inspection and vendor evaluation, please give me details of configuration steps for it.
    thanks in advance

    *What is Source Inspection* 
    What is source inspection and what are the setup required to do in system to implement successfully?
    A source inspection is a quality inspection in which Buyer required the quality check before the material received. So that he performed the quality inspection at the vendoru2019s Location.
    To setup source inspection, you should define inspection type (01 and 0101) in material master QM View. (MM01)
    When requesting source inspection, include the following information:
    a)  Purchase order number
    b)  Item number
    c)  Part number
    d)  Quantity of parts to be inspected
    e)  Date source inspection is required
    f)   Types of inspection  required
         - In Process
         - Final
         - Interim
         - First Article Inspection (FAI)
    g)  Contact name and phone number
    Go to transaction QI07 and give the material code, vendor, plant and opening period. When you execute the transaction you would find open purchase orders for the given input data. Select the Purchase Order you wish to perform Source Inspection and choose Create Inspection Lot. These inspection lot triggers for inspection type 0101. Against this inspection Lot perform result recording QE01 & QA11.
    When finally you received Goods at your premises, then inspection lot will triggered automatically (01) and perform result recording QE01 & QA11 
            How to do Source Inspection in QM
    Can any one guide how to do Source Inspection in QM. What are the settings required to be done and can the lot for source inspection be trigerred manually or automatically. 
    The Q-Info Record is used to trigger a source inspection lot for a material/vendor and plant. Under the tab key Inspection Control in Q-Info Record, you would find vendor source Inspection and under that select the inspection type desired for source inspection (say 01,0101) and give the lead time required to perform the  inspection in days (say 10 days).  If you do not want to trigger an inspection lot @ GR for a source Inspection lot then check the box (Source Insp. No Gr).
    Ensure that the inspection type selected @ source inspection is activated in the Material Master Record for the chosen material in the Quality Management View.
    To trigger the lot manually you need to have some open purchase orders for the material/plant/vendor. Go to transaction QI07 and give the material code,vendor,plant and opening period. When you execute the transaction you would find open purchase orders for the given input data. Select the Purchase Order you wish to perform S.I and choose Create Inspection Lot. 
    This would trigger the lot and then it is QE01 & QA11.
    Vendor Evaluation for Purchasing
    Define the weighting keys in SM30 - V_T147J.
    Weighting keys 01 and 02 are defined in the standard system. You combine the following
    weighting shares for the standard main criteria:
    Main criterion     Key 01 Key 02
    Price                   1      5
    Quality                 1      5
    Delivery                1      2
    Gen. service/support    1      1
    Ext. service provision  1      2
    Define the criteria in SM30 - V_T147G - Double click on the line items
    In this step, you define the criteria by which the system computes scores for vendors and
    specify whether the scores for the subcriteria are computed manually, semi-automatically, or
    automatically.
    You can also store your own methods of computation for the scores for subcriteria in the
    form of user exits. The enhancement MM06L001 is available for this purpose.
    Define the scope of list in SM30 - V_T147M - Double click on the line items
    Define Purchasing Organization data for vendor evaluations in transaction OMGL.
    An example :-
    How the system calculates the score for the automatic subcriteria
    "On-Time Delivery Performance"?
    The system uses the statistics-relevant delivery date in the purchase order
    (Items -> Delivery Schedule) and the goods receipt date to calculate date variances.
    You use the statistics-relevant delivery date, for example, if you know that the vendor
    will not deliver the material as scheduled on September 15 but on September 30. Enter the
    delivery date as September 30, but enter the statistics-relevant delivery date as
    September 15.
    In calculating the score for on-time delivery performance, the system will then not use
    the actual delivery date, but the statistics-relevant delivery date. This has a negative
    effect on the score for this goods receipt.
    However, materials planning and control uses the realistic delivery date (September 30)
    which the vendor will actually adhere to.
    The system considers only goods receipts against purchase orders and scheduling agreements
    into stores and the release of GR blocked stock into stores. In the standard system, these
    are the movement types 101 and 105.
    Minimum Delivery Percentage - OMGL in the On-time delivery section
    If you do not want a vendor to receive a very good score if he delivered the goods on time,
    but did not deliver the required quantity, you can maintain a minimum delivery percentage
    in Customizing.
    Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on
    time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is
    not included in the calculation of the vendoru2019s score for on-time delivery performance. So
    that the non-scoring of the on-time delivery performance criterion in this case does not
    bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score
    for quantity reliability. On-time delivery performance is thus always to be seen in
    conjunction with quantity reliability.
    Standardizing Delivery Date Variance  - OMGL in the On-time delivery section
    To rate delivery date variances in days, maintain the Std.del.time var. parameter.
    If you assign a lower standard value, this means that relatively low date variances produce
    high percentage variances. If you set a higher standard value, this results in a relatively
    low percentage variance:
    The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27;
    the statistical delivery date was Nov. 15. There is thus a difference of 12 days.
    The system calculates the percentage variance as follows:
    12 / 20 x 100 = 60
    If the Std.del.time var. parameter had the value 60, the variance would be 20%
    (12 / 60 x 100 = 20).
    If you do not maintain this parameter, the system calculates the delivery time variance via
    the firm zone in the case of scheduling agreements, and via the order date and the
    statistics-relevant delivery date in the case of purchase orders.

Maybe you are looking for

  • I don't know how to get it online?

    I try to export to HTML and from there I don't know how to get HTML (which is a little off anyways, doesn't look the same as it does on Muse) onto the actual site? It just pops up in a window, not online but as a file on my browser window. It's in a

  • How can I capture Microsoft EventSource Events on a Windows Phone?

    I use Microsoft EventSource Library to create events to instrument our applications. For Windows Applications running on Windows 7/8/8.1 I can use xperf to capture the events (xperf.exe" -start UserLogger -on GUID -f User.etl). But how can I do this

  • Internet in my Area

    Some of your partner sites tell me that I should be capable of recieving some of your internet plans, though when I went to a Verizon store they told me that Verizon stops at the end of my street. The verizon store told my family that they were build

  • DVD Dual Layer, +/- which is better?

    I've been trying to burn a dual layer DVD-R DL from iDVD6 but it won't let me, it will however let me burn a DVD+R DL even though my burner can burn both. What are the benefits however of burning one from the other as iDVD seems to mainly support DVD

  • Creating an SRM Purchase Order with a Return Line

    Is it possible within standard SRM to create a purchase order with a 'Returns Item' line? I know it's possible in R/3 but really need to create it via SRM. Regards Keith