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%

Similar Messages

  • 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

  • Vendor Evaluation - Statistical Delivery Date

    Hi,
    The statistical delivery date is an important field during the calculation of the on-time delivery score. (see note 310666)
    After implementing a new support package this field wasn't filled up automatically anymore. Fortunately note 1039344 and 1164767 helped overcome this.
    But ... in the meantime purchase orders were created and received without a statistical delivery date.
    Which date / or what does sap do when calculating on-time delivery score if there is no statistical delivery date ? Does it take the "delivery date" into account ?
    with regards

    Use this link http://help.sap.com/search/highlightContent.jsp
    http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/MMISVE/MMISVE.pdf
    Or find on the SAP help Vendor evaluation white Paper its there.
    Edited by: Prashant Prasad on Jul 31, 2009 12:01 PM

  • Delivery date variance for multiple schedule lines in EKET

    Hi experts,
    can anyone tell me what dates  are used (from EKET, EKBE or any other table)  to calculate delivery date variances when there are multiple schedule lines in EKET table. I am able to match single schedule line POs but not POs having multiple schedule lines.
    thanks in advance,
    purvang

    can anyone provide input on this?

  • Delivery date variance

    Hi,
    We want to maintain the Delivery Date variance in the following customisation;
    SPROMaterials ManagementPurchasingStatistics-Define Grid for Delivery Date Variance
    Here We want to maintian the following intervals, how to maintian below ranges as when we trying to maintin the same we are getting error as "Enter Numeric Value"
    Also please explain where it will have the impact if we maintian these date here.
    Var1- 0 to 07 days
    Var2- 08 to 15 days
    Var3- 16 to 30 days
    Var4- 31 to 60
    Var5- > 61
    Please suggest.
    Thanks in advance
    Regards
    Shp

    HI,
    Can anybody suggest.
    Thanks
    Shp

  • 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 on Delivery

    Hi All,
    We have configured the vendor evaluation in our ECC 5.0 Dev system.
    We have Defined the main criteria, respective sub criteria s, weighting keys and also the purchase org level data.
    The weighting level is equal.
    The scoring methods have also been set such as:
    For Main Criteria Delivery,  Subcriterias such as On Time delivery, Quantity reliability, Adherence to confirmation date ...etc has been given the scoring methods.
    3 for On Time delivery
    2 for Quantity reliability
    B for Adherence to confirmation date.
    The point scores for these methods have also been set with scales such as
    for 5.0 %  score is 20
    for 20.0 %  score is 10
    for 50.0 %  score is 5
    for 99.9 %  score is 1
    In ME61 the vendor evaluation is created.
    We tried 2 scenarios.
    Scenario 1: Where the purchase order is created and the receipt is done at a later date than mentioned in the PO as the delivery confirmation date.
    Scenario 2: Where the purchase order is created and the receipt is taken for a quantity which is less than the quantity ordered.
    When the vendor evaluation is carried out in ME61 Automatic New Evaluation or ME63 we get the result for only price and that too
    The score is 1.
    The weighting is 100%
    The overall score is 1
    My Doubt is why isn't there a calculation on the scores done for criteria 03 - Delivery ???
    It shows a score of 0. But the scenarios mentioned should have populated the score for Delivery, I presume.
    Please advice where I have gone wrong or what is that I have missed to configure.
    Regards
    Govind
    Edited by: Govind Ramesh on Aug 23, 2011 11:54 AM

    I can see that you are using a ZSAP update group , and think this is the root cause for all your problems.
    See OSS Note 397864 - Self-defined info structures purchasing similar to S013
    it explains:
    Therefore, you are not permitted
    a) to use info structure S013 as a template for self-defined info structures (This is prevented as of Release 4.5 due to a termination message).
    b) to create any update rules for S013 with a self-defined update group.
    c) to include the enhanced update rules that are used for S013 during the definition of key figure updating into the definition of the update of a self-defined info structure (compute...).
    Sorry for this late update, just saw that you found it yourself, I had the reply open but then went for a breakfast without sending.
    Edited by: Jürgen L. on Aug 24, 2011 9:55 AM

  • Vendor Evaluation in different date Range

    Hi Experts,
    Vendor Evaluation is configured in our client. Our requirement is like this. We want to get vendor evalulation month wise.
    like
    01.04.2009 - 30.04.2009
    01.05.2009 - 31.05.2009
    01.06.2009 - 30.06.2009
    01.07.2009 - 31.07.2009
    How can I get vendor evaluation of a vendor for above period.
    Please guide me, full points for helping answers.
    Regards
    GR

    Hi,
    Check Vendor Evaluation Report tr. ME6H(after selection drilldown on the basis of month), Hope this will work for you
    thanks...

  • 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

  • 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

  • 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

  • MM Vendor Evaluation

    Dear friends !
    I have a doubt about Vendor Evaluation criteria calculation.
    For example , Price
    Into Price(main criteria) we have Price Level and Price history.
    SAP calculate scores to price using which tables ? this criteria is accumulated by month ? or by Purchase order ?
    Does anyone could help to understand the places where SAP catch data to calculate vendor scores ?I really do not understood the help.sap.com regarding this subject.
    Best regards,
    Ale

    Hi Alessandro Brazil 
    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. 
    Thanks

  • Vendor Evaluation using Factory Calendar?

    Hello,
    Can I set up Vendor Evaluation to consider the Factory Calendar when scoring with the Standard Delivery Date Variance?
    I have set it up to allow the delivery to score 100% of the points if the delivery is in by 6AM the following day.  But this does not work over the weekends.
    Thanks,
    Matt

    Please help.
    There must be some way to do this. 
    If the factory is closed on the weekends and you miss a Friday delivery, even though you could have made the Saturday delivery you have to wait until Monday and SAP scores you as though you were 3 days late instead of the actual 1 day late.
    How can I make Vendor Evaluation use the factory calendar?
    Thanks,
    Matt

Maybe you are looking for