Confirmation date in vendor evaluation

Hi Gurus,
               Can you please let me know the settings to be maintained to get a score for the sub criteria Adherence to confirmation date during vendor evaluations.
I've already maintained the purchasing org config settings like weighting and point scores for the automatic criteria.
But when I run a vendor evaluation there is no score coming out for the sub-criteria Adherence to confirmation date.
I'm using the confirmation control key One day acknowledge and confirmation category AB (Order acknowledge). Please let me know if anything is missing out
Regards,
Ashwin.

Ashwin
Our company has the same issue, did you find a solution to this problem?
Thanks
Brad

Similar Messages

  • Delivary date parameter in vendor evaluation

    hi
    where we maintain the delivary date parameter in vendor evaluation.
    nitin

    Hi,
    Delivery date in vendor evaluation is a subcriteria for On time delivery and its automatic (3)
    Delivery date is calculated from GR from stastical delivery date in delivery schedule TAB and actual receipt date
    Hope this is clear to you
    BR
    Diwakar
    reward if useful

  • FM creation for vendor evaluation data

    Hai,
        In my function module I need to get vendor evaluation data. To do this from where I can get the details, r there any tables for this, could u suggest something for this, actually I'm new for this MM. Eventhough if there r any tables, before writing FM r there any settings to be done for this.
                I know in ME61 we can get these details, but to write RFC how to proceed.
                                       Thank you
                                     Regards
                                      Srinivas

    hi
    check
    ELBK, ELBN, ELBP u2013 Vendor Evaluation Related Data
    ELBM ( Vendor Evaluation: Material-Related Item)
    S013
    regards
    kunal

  • 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

  • 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 - Automatic new evaluation

    Hi,
    Vendor evaluation is maintained. But it does not get updated automatically after GR. We have to update them one by one (ME61/ME63). Is there a way to automatically revaluate multiple vendors at the same time.
    Regards,
    Pratap

    Hello,
    If you want to evaluate vendors on a large scale, the system offers standard analysis to meet with your needs. They are transactions ME6B, ME6C, and ME6D. YOU can access these transactions via the front-end SAP menu Logistics>MM>Purchasing>Master Data>Vendor Evaluation>List Displays. For details about these standard analysis
    report, you can read the online documentation at SAP Liabrary>Logistics>MM>Information System>MM Vendor Evaluation>Reports and Analyses in Vendor Evaluation.
    What data will be taken into account in vendor evaluation is defined by the applicability period (period in calendar days) in IMG Customizing >MM>Purchasing>Vendor Evaluation>Define Purchasing Organization Data for Vendor Evaluation. Note: The applicability period is not taken into account with respect to all vendor evaluation criteria. It is therefore not designed to restrict the period to a certain year.
    Example:
    If you enter the value 150 here, the system will take into account data from the past 150 days for vendor evaluation purposes. Data that is more than 150 days old will not be included in the evaluation process.
    Next, after a configuration change, you will have to rebuild table S013 to get data before the configuration into vendor evaluation with transaction OLI3. I have attached note 64636 which describes the process of rebuilding your statistics.
    Regards,

  • 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 - General Service and support

    Hi
    What are the subcriteria that can be under General Service and support?
    How the scores are calculated for this?\
    If manual where can we enter the scores for these?
    Regards
    Soumen

    Hi,
    Following are the answers for your questions.
    What are the subcriteria that can be under General Service and support?
    Ans: - Subcriteria can be defined by us as per our requirement but SAP has provided following 2 Subcriteria;
    - Quality of service
    - Service timeliness
    How the scores are calculated for this?
    Ans: - For above 2 subcriteria, you can assign a scoring method as following;
    C Determination from quality rating of service
    D Determination from timeliness rating of service
    Config Path: - SPRO > MM > Puchasing > Vendor Evaluation > Define Criteria > Here maintain subcriteria for Service criteria and assign the scoring method
    At the time of processing Service Entry Sheet, under "Vendor evaln" Tab, you will have option to enter scores for the following subcriteria
    - Quality of service
    - Service timeliness
    Once you enter scores here, it will get calculated in ME61, if automatic evaluation is configured for above 2 subcriteras
    Config Path: - SPRO > MM > Puchasing > Vendor Evaluation > Define Purchasing Organization Data for Vendor Evaluation > Here for Service criteria and it's subcriteria do not activate manual maintenance indicator
    If manual where can we enter the scores for these?
    Ans: - And if you want to maintain values manually for Service criteria and subcriteria then activate the manual maintenance indicator in above config path and then maintain it duirng ME61 (Vendor Evaluation)

  • Vendor Evaluation Price Level  For services

    Hi expert, I've seen that the Main Criterion "Price" is just for materials, and I wanted to know whether there is a way of Calculating Scores for Automatic Subcriteria for services.
    I also wanted to know if there is any other standar criterion for evaluating services.
    Thanks !!

    Hi,
    Subcriteria can be defined by us as per our requirement but SAP has provided following 2 Subcriteria;
    - Quality of service
    - Service timeliness
    For above 2 subcriteria, you can assign a scoring method as following;
    C Determination from quality rating of service
    D Determination from timeliness rating of service
    Config Path: - SPRO > MM > Puchasing > Vendor Evaluation > Define Criteria > Here maintain subcriteria for Service criteria and assign the scoring method
    At the time of processing Service Entry Sheet, under "Vendor evaln" Tab, you will have option to enter scores for the following subcriteria
    - Quality of service
    - Service timeliness
    Once you enter scores here, it will get calculated in ME61, if automatic evaluation is configured for above 2 subcriteras
    Config Path: - SPRO > MM > Puchasing > Vendor Evaluation > Define Purchasing Organization Data for Vendor Evaluation > Here for Service criteria and it's subcriteria do not activate manual maintenance indicator
    And if you want to maintain values manually for Service criteria and subcriteria then activate the manual maintenance indicator in above config path and then maintain it during ME61 (Vendor Evaluation)

  • Configuration vendor evaluation

    Dear MM consultants
    I am facing problem in configuration of vendor evaluation.
    In Vendor evaluation
    1) define weighing key i.e-1- equal weighting, 2 - unequal weighting
    2)define criteria . here I created 1-price, 2-quality, 3- delivery, 4-service
    In criteria "price" I created subcriteria price level & the subcriteria no 1 & scoring method is 4.In criteria quality I created three subcriteria 1)GR INSPECTION
    2) COMplaint/rejection, 3)audit & the scoring method is 7,8,9. In delivery criteria the subcriteria is 1-on time delivery.& the scoring method is "B".& FOR SERVICE CRITERIA 1) SAFTY & SCORING METHOD i HAVE NOT selected because I have taken "no automatic determination".
    in pur organisation data for vendor evaluation when i click on subcriteria icon I put "1" in weighing field.when I click on weighting I entered weighting key 1& 2 for price, quality, delivery, service.& when i click in point score of automatic criteriaI I copied  from standard system which has been maintained in sap system.AFTER DOING ALL THE THINGS WHEN i USED t-CODE ME61 THE MESSAGE COMESweighting key for purchase organisation does not exist.PLEASE SOLVE MY PROBLEM TODAY EVENING.
    THANKING YOU
    CHITTARANJAN

    goto define pur org data for vendor evaluation and select oyur pur org and hit the weighting button at the left and maintin the weighting key for all your criteria here

  • 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

  • Vendor evaluation Transactional ODS

    Hi all,
    I need follwoing information with respect to supplier evaluation, pulling the data from SRM:
    1) what is the differnce between the ODS 0SRVE_O4 and 0SRVE_O2?
    2) what is the differnce betwwen the ODS 0SRVE_O3 and 0SRVE_O1?
    3) How and when can we use the transactional ODS 0SRVE_O1 and 0SRVE_O2?
    If anybody has worked on these ODS in any of the project, please share the experience of it and how to go about these transactional ODS, in the terms what is the utility of these transactional ODS.
    Thanks and Regards,
    Neha

    Hi Neha,
    Please check the following link, it will provide detailed information on all these ODS.
    http://help.sap.com/saphelp_nw70/helpdata/en/f0/3abab39e044d41b8a553136d5ff2f4/frameset.htm
    Usually for vendor evaluation ODS 0SR_VE and infocube 0SR_VE_C1 is enough to take care of the requirements. However, it depends on the business requirement whether you have to go for transactional ODS. The transactional ODS enrich the data of vendor evaluations by capturing the data from GRs etc.
    Hope this information helps.
    Please let me know in detail about your requirement so that I can help you.
    Regards,
    Sreenivas.

  • Vendor evaluations

    pl. guiide me ,
    i have maintain all settings for vendor evalations for perticulat pur.org. but while evaluation there is a error - system settings for pur. org. is incomplete in me 61 tcode. or tell me with tcode the vendor evaluation steps

    SPRO->MM->purchasing->vendor evalution
    1. Define weighing keys
    2. Define criteria
    3. Define scope of list
    4. Define purchase organisation data for vendor evalution
    5. Goto Main criteria
    6. Select criterial clicl on sub criteria
    7. Points score for automatic criteria
    ME61 Maintain
    ME64 Compare evalution
    Ravi

  • System setting for vendor evaluation incomplete

    HI....
    I want to caryout automatic vendor evaluation when i run t code ME63, its show an error system setting for purchase org incomplete where as i have maintained all the parameters from standarfd 0001, can anyone tell me how to carry out ven evaluation.
    Regards
    SARFRAZ

    Hi,
    Select SPRO --> Materials Management --> Purchasing --> Vendor Evaluation. Select following criteria -
    1) Define Weighing keys - Here define weighing keys in addition to 01- Equal Weighing & 02- Unequal Weighing (if required)
    2) Define Criteria - Here 5 standard criteria are maintained. Maintain additional criteria if required. Also maintain sub-criteria. Each main criteria contains some standard subcriteria. If required you may maintain additional subcriteria upto 20 per main criteria.
    3) Define Scope List - Here you may maintain how the evaluated vendors should be ranked.
    4) Define Purchase Organization Data for Vendor Evaluation - Here you may maintain main criteria & sub-criteria for your purchasing organisation. Also maintain score for equal & unequal weighing. Maintain point score for automatic  criteria for each percentage vainance
    Hope this fulfils your query
    Regards

  • Vendor evaluation points automatic criteria

    Hi
    How the percencetage & points are determined for automatic criteria.
    Regards
    Umapathy

    hi,
    Vendor Evaluation for Purchasing
    Go to SPRO --> Materials management --> Purchasing -
    > vendor evaluation
    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
    Regards,
    Manish

Maybe you are looking for

  • WebLogic Server: 10.3.5.0 - Managed stuck in STARTING

    Hi all. I have a managed stuck in STARTING for like 2 hours, the logs are these: ####<Sep 25, 2013 1:40:42 PM CEST> <Info> <JMS> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kern

  • IPhoto library won't sync with iTunes

    I recently bought an Apple TV and when I went to sync my iPhoto pictures (via the Photos tab in iTunes) no albums appeared in the box beneath. When I tried to sync anyway, the following message apeared: "iTunes cannot sync photos to Apple TV because

  • Queries related

    Hello, I have few more doubts regarding queries.Kindly tell me. 1)List segments with more than 500M of free DB Blocks SELECT SEGMENT_NAME, SEGMENT_TYPE, TABLESPACE_NAME, EXTENT_ID, BYTES/1024, BLOCKS FROM DBA_EXTENTS WHERE BYTES/1024 > 500; 2)List al

  • SAP ERP 6  system and compatibility with BW systems.

    Hi All, An upgrade to a ECC 6.0 system form 4.6C or 4.7 system is fine. But however, in an integrated environment - the 4.6C system is usually integrated with other SAP Products as well. The question I have is is a ECC 6.0 system compatible with BW 3

  • Compiling Servlet problem that uses a JavaBean

    I have a servlet that will get data from a JavaBean which is created before in a jsp file. While I trying to compile the servlet I am getting this message: --------------------Configuration: JDK version 1.3 <Default>-------------------- Command : "C: