Average variance in ranking list of vendor evaluation

Dear Gurus,
When we run the ranking list for vendor evaluation for a purchase org, in the last column there is a score for average variance for each of the vendor. COuld anyone tell me the significance of the same.
Also is there any better way to get the list in tabular form/ ALV grid format.
Thanks a ton
Kamal

I am interested in this also. Need to trigger Evaluation survey being sent out when GR is posted.

Similar Messages

  • Ranking lists of Vendors(ME65)

    Hi all,
    iam useing Tc:ME65
    i given   po,vendor and weighting keys , the ranking list was displayed. in that how we can get the Av.variance ?
    can any body help me.
    Edited by: Dhanush on Nov 5, 2008 5:41 AM

    hi
    Evaluation Lists - ME65
    Description:
    Based upon an overall vendor evaluation score, the Create Ranking List transaction generates a list of vendors in descending order. Additionally, the list displays individual main criteria and average values for the individual scores.
    Preliminary Steps:
    Valid vendors must exist in SAP with procurement activities against each one to be evaluated. SAP cannot evaluate, compare and rank vendors without prior procurement activity.
    Detailed Steps:
    1.    In the iPanel, My SAP Roles, select XX: Functional All Transaction Role>ME65 - Evaluation Lists. If you are in another transaction screen, enter/nME65 in the command line and click Enter. 
    2.    In the Ranking List of Vendors screen, enter DLA1 in Purchasing organization.
    3.    Enter the Vendor or range of Vendors, or click the match code button to create a list to select from.
    4.    If applicable, enter Vendor class.
    5.    If applicable, enter Scope of list.
    Note: Scope of List determines the list content and structure. This value defaults to STANDARD and no change is required.
    6.    Enter Number of vendors to define the maximum number of vendors to be displayed.
    Note: The default display value for the ranking list is 50.
    6.    Enter ABC indicator to display vendors classified according to DLA significance.
    7.    Enter the Industry sector.
    8.    Enter Country of supply to identify vendors from a particular country or countries.
    9.    Enter Weighting key to determine the weight of main ranking criteria.
    10.    Click Execute.
    11.    Review the list retrieved.  To see more details, select a line item and click one of the buttons.  You can select:
    Evaluation
    Vendor
    Original list
    hope it clears
    regards
    kunal

  • Vendor evaluation in purchase order (vendor unknown)

    Hi!
    I created 2 new evaluation criteria for vendor evaluation.
    When i go to tcode ME25 "create PO vendor unknown", I assign the source of suplly and click on "vendor evaluation" my 2 new criterias do not appear in the "Ranking list of vendors".
    Any ideas?
    Regards.

    I think the new vendor is having a different pricing schema than the old vendor. Check the pricing schema for the old vendor (in purchasing view in field 'Schema Group. vendor) and compare it to the new vendor. I think they're different.
    If it is then what i think happening is the user already input the price for the condition type in pricing schema A, then the vendor is changed and the new pricing schema is kiciking in thus making the old condition type missing.
    Try to either:
    A. Change to the old vendor back,
    B. Change the pricing schema of the new vendor to be the same with old vendor

  • Vendor Evaluation process (with QM module not implemented)

    Hi
    Can I have more input on Vendor Evaluation process (with QM module not implemented)  please ?

    Hi,
    Vendor evaluation can be automatic, manually or semi automatic. It is done on 4 criteria;
    1.     Price
    2.     Quantity
    3.     Delivery
    4.     Service 
    VE is done at p.org level, the Maximum no. of criteria that can be used are up to 99.
    IT is done in 4 steps:-
    1.     Define Weighing keys( equal weighing for all criteria or unequal weighing )
    2.     Define criteria
    3.     Define Scope of list
    4.     Define Pur. Org data for vendor.
    5.     
    SPRO—MM—PURCHASING --- VENDOR EVALUATION 
    ME61 Maintain vendor evaluation (Put p.org and vendor)
    Then ME65 Ranking list of vendor….
    Regards,
    Vivek

  • Vendor Evaluation - Fully Automatic

    Hi all,
    Could you please answer two queries in Vendor Evaluation.
    1. What is use and where we assign scope of list in vendor evaluation
    2. I want to take evaluation from Invoice also. Configurations I have done but system is not calculating the score on base of invoice verification.
    Regards

    Hi
    for your first question:
    The Vendor Evaluation component helps you select sources of supply and facilitates the continual monitoring of existing supply relationships. It provides you with accurate information on prices, and terms of payment and delivery. By evaluating vendors, you can improve your enterprise's competitiveness.
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/8d/b97c2d414511d188fc0000e8322f96/content.htm
    for your second question
    please re check your setting..
    very imp vendor evalution
    these links will help you.
    thanks..

  • Vendor Evaluation Standardizing Delivery Date Variance

    Hi,
    We are determining what the settings should be for On-Time Delivery and Quantity Reliability under Vendor Evaluation.  I understand how the formual works when it determines the scores for these.  Can someone tell me from a business process perspective what Standardizing Delivery Date Variance relates to? 
    Ours has been set to 100 which is 100 days with the scores set as:
    Percentage
    Score
    0
    100
    10
    90
    20
    95
    100
    80
    200
    60
    300
    40.......
    When we pick 100 days, is that supposed to be an average of how many days late goods receipts are?  Or is there another way to look at it? 
    Thanks
    Beverly

    Have you really read the documentation and the F1 field help, or any of our blogs, documents and wikis here in SCN?
    The table that you presented above is far a way from reality. a percentage can go from blank  to 99.9  and your from -99.9 to blank
    this is to cover both situations early deliveries and late deliveries
    the Standard Delivery Date Variance means the it is the maximum number of days a vendor can be late or early to the wanted delivery date, if this value is reached, then he just missed the point in the sense of the word. he does not get any single point for his performance.
    You have to ask your business how much days variance they accept before they cancel the order, or at least looking for a new vendor with the next order.
    From our point of view everything beyond a week is not at all acceptable and results in a total miss
    and in this case you do not need many percentages either in a 5 working day week  each day corresponds to 20%

  • Vendor Evaluation Smoothing Factor an average

    Hi,
    We are setting up Vendor Evaluation and would like the Delivery scores to be closer to a true average of all of the scores.  We are having difficulty getting to that number.  Is there a way to do it in SAP?
    Thanks.
    Beverly

    Hi Beverly
    Have a look at the following notes
    459516    FAQ: Vendor evaluation
    806834    Calculation of score for Quantity Reliability
    and also the following documentation
    Determining Scores - MM Vendor Evaluation - SAP Library

  • Vendor evaluation - Avrge Variance

    hi,
    when I excuting me6b ranking by material , i m getting individual  scores and average variance column also.
    please clarify me how  this average variance calculation happens ? how it be linked with overall score.
    Thanz in Advance.
    aparji

    hi
    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
    kunal

  • Standard report for Vendor Evaluation

    Hi everyone,
    Is there any standard reports (ALV) to display Vendor evaluation ranking list except ME65, ME6B, ME6H.
    any other Program names will also do...
    Thanks
    Sukriti...

    hi
    S_ALR_87012990 - Evaluation Comparison
    ME6H - Standard Analysis: Vendor Evaluation
    ME6E - Evaluation Records Without Weighting
    ME6C - Vendors Without Evaluation
    ME6B - Display Vendor Evaluation for Material
    ME65 - Evaluation Lists
    regards
    kunal

  • 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 scores sub criteria price level and price history

    Dear all,
    I have configured vendor evaluation with subcriteria price history and price level as automatis.
    For test, I created a vendor and a material. Assigned market price for year 2009 and 2010.
    Also info record price maintained for the vendor material combination.
    Vendor XYZ
    Material ABC
    For 2009 Market price 8 and effective price 8.5
    For 2010 Maket price 8.2  Effective price 8.5
    Variance calculated 8.43% and score is 15. This was calculated correctly.
    Now I created another material and maintained master data for that mater
    Vendor XYZ
    Material DEF
    For 2009 Market price 18 and effective price 20
    For 2010 Maket price 20  Effective price 22
    Variance calculated 1% for which the score is 50.
    When I go for vendor evaluation through ME61 , system is not considering the average of 2 scores. But giving a score of 50. Score bands are as follows.
    5     Price behavior     5.0     10
    5     Price behavior     10.0     15
    5     Price behavior     20.0     20
    5     Price behavior     50.0     20
    5     Price behavior     99.0     10
    5     Price behavior     5.0-     50
    5     Price behavior     10.0-     100
    5     Price behavior     50.0-     20
    5     Price behavior     99.0-     10
    Pls help me resolve the issue
    Regards.
    Milind Dugade

    Hi Siva,
    [Vendor Evaluation|http://help.sap.com/erp2005_ehp_03/helpdata/EN/8d/b97db3414511d188fc0000e8322f96/frameset.htm]
    [Price Level|http://help.sap.com/erp2005_ehp_03/helpdata/EN/8d/b97db3414511d188fc0000e8322f96/frameset.htm]
    [Price History or Behaviour|http://help.sap.com/erp2005_ehp_03/helpdata/EN/8d/b97db3414511d188fc0000e8322f96/frameset.htm]
    Reward if helpful.
    Thanks and Regards,
    Naveen Dasari
    Edited by: Naveen Dasari on May 16, 2008 1:10 PM

  • Vendor Evaluation - Price history

    Hi
    In vendor evaluation the score for the subcriteria Price History is not getting calculated.
    The scoring method that I have used is : Automatic Determ. from Purch. Statistics: Price Behavior
    What can be the reason? How it is calculated?
    Regards

    to determine how a vendor's price for a material has changed over the last few years, the material's price history is compared with the market price history.
    The system first checks whether the buyer has maintained the current market price and last year's market price for the material.
    If not, the system uses the price for the material group to which the material belongs.
    If this price is not maintained either, the system uses the effective prices from the previous year and the current year. Prices from standard purchase orders for materials and prices from subcontract orders are dealt with separately.
    The system then calculates the percentage variance between the old and new market prices.
    The vendor's effective price is re-calculated with this percentage variance. The result represents the effective price the vendor should be asking if his price had changed over time in the same way as the market price.
    This calculated effective price is then compared with the actual effective price, and a percentage variance is determined.
    The system then awards the vendor the score you have maintained in Customizing for this percentage variance.
    The system repeats this process for all the materials you procure from the vendor. Each time you start an evaluation, the system calculates the average score for all the materials. The result is the vendor's score for the subcriterion "Price History".

  • 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

  • Price level in vendor evaluation

    Hi,
    I have created 1st PO with price 50 and checked the ME63, system showed score for price level as 40. Then I made another PO with price 55 and checked ME63, system displayed the same score 40,
    While there is change in price of 10 %, so I was expecting score of 10 .
    Can anyone explain about this.

    Hi,
    Following is the calculation procedure for
    1) Price Level -
    If you have maintained market price for the material, the system checks vendor's price level with the market price, otherwise it compares the vendor's price with average price of material by all vendors. Then the price variance is calculated in percentage. The score is awarded for this price variance as per settings in your system configuration. This process is repeated for all the materials supplied by the vendor. The overall score is the average of all these scores.
    2) Price Behaviour -
    System checks market price / average price of the material for last year as well as for current year. System calculates the percentage change for the market price. System repeats this procedure for price of material by vendor. Then system compares these two values & calculates percentage variance. The score is awarded for this variance as per system configuration. The overall score is the average of all these scores of the materials.
    3)Online Delivry statistics -
    System calculates the difference between scheduled delivery date in PO & actual delivery date & calculates the percentage variance. The score is awarded as per settings in system configuration. This process is repeated for each P.O. & overall score is average of all these values.
    Hope the answer is helpfull. For more details, you can avail online help at site http//:help.sap.com on subject Vendor Evaluation.
    Regards,
    Prashant Kolhatkar

  • Mass Maintain weighting key for vendor evaluation.?

    Hi experts
    Can anybody give some inputs for below issue
    1.How to maintain weighting key for vendors .
    2.How to maintain weighting key for all vendors in mass .(Mass maintainence)
    3.How to get the report of vendor ranking list duration wise (Month, year..etc).
    Regards
    MM group

    weighting keys is customizing, and this is certainly not by vendor.
    you define one weighting key  and then you run vendor evaluation using this weighting key.

Maybe you are looking for