SAP OSS Notes on vendor evaluation 1

19.03.2009 Page 1 of 5

SAP Note 459516 - FAQ: Vendor evaluation

Note Language: English Version: 14 Validity: Valid Since 01.06.2007

Summary

SymptomThis note contains questions and answers that are often come up whendealing with MM-PUR Vendor Evaluation.

Catalog of questions:

1. Why is my purchase order not considered when calculating a score forquantity reliability?

2. Why is a score of zero calculated for on-time delivery?

3. Why is no score calculated for a goods receipt reversal?

4. Why are no scores calculated for some criteria such as delivery,quantity, shipping, etc.?

5. Why are wrong scores calculated for sub-criteria on-time delivery?

6. Why are wrong scores calculated for sub-criteria quantity reliability?

7. Why is the statistical delivery date (eket-slfdt) used for on-timedelivery calculation, instead of the item delivery date (eket-eindt)?

8. Why are scores returned when running new vendor evaluation, althoughnothing exists in S013 within the applicability period that's definedin customizing(T147-STAGE)?

9. Why does the system generate error message ML061 'System settings forpurchasing organization xxxx incomplete' when I maintain a vendorevaluation ?

More TermsFAQ, vendor evaluation, quantity reliability, on-time delivery, pricelevel, price history, price behavior, score, points.

Cause and PrerequisitesFAQ Vendor Evaluation

Solution

1. Question:Why is my purchase order not considered when calculating a score forquantity reliability?

Answer:Only closed purchase orders will be considered, as long as they fall withinyour given time range.A purchase order is closed if:

19.03.2009 Page 2 of 5


o the goods receipt quantity is greater than or equal the poquantity.

o the delivery complete flag is set in the purchase order.

The time range is set in:

o TA OLME -> Purchasing->Vendor evaluation->Define Purchasing...-> doubleclick your purchasing organization -> Applicability period -> timerange in days

-----------------------------------------------------------------------

2. Question:Why is a score of zero calculated for ontime-delivery?

Answer:Please implement note 507627.

-----------------------------------------------------------------------

3. Question:Why is no score calculated for a goods receipt reversal?

Answer:

o Behavior of reversals: See note 451733.Problem with scores: See note 512037.

-----------------------------------------------------------------------

4. Question:Why are no scores calculated for some criteria such as delivery, quantity,shipping, etc.?

Answer:

o Most of the scores for vendor evaluation are computed during the

o processing of a goods receipt and stored in the purchasingstatistical

o table S013.

o If you don't have scores for these criteria check whether:

o

o - There are goods receipts for the evaluation period.

o

o - Update of S013 has been set. (transaction OMO2).-----------------------------------------------------------------------

19.03.2009 Page 3 of 5


5. Question:Why are wrong scores calculated for sub-criteria on-time delivery?

Answer:Please check notes 568357 and 806832.

-----------------------------------------------------------------------

6. Question:Why are wrong scores calculated for sub-criteria quantity reliability?

Answer:Please check note 806834.

-----------------------------------------------------------------------

7. Question:Why is the statistical delivery date (eket-slfdt) used for on-timedelivery calculation, instead of the item delivery date (eket-eindt) ?

Answer:The statistical delivery date allows you more flexibility in the scoring ofyour vendor.This information is copied directly from the help portal for MM VendorEvaluation. Please refer to http://help.sap.com :

"The system uses the statistics-relevant delivery date in the purchaseorder and the goods receipt date to calculate date variances.

You use the statistics-relevant delivery date, for example, if you knowthat the vendor will not deliver the material as scheduled on September 15but on September 30. Enter the delivery date as September 30, but enter thestatistics-relevant delivery date as September 15.

In calculating the score for on-time delivery performance, the system willthen not use the actual delivery date, but the statistics-relevant deliverydate. 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 andscheduling agreements into stores and the release of GR blocked stock intostores. In the standard system, these are the movement types 101 and 105."-----------------------------------------------------------------------

8. Question:Why are scores returned when running new vendor evaluation, althoughnothing exists in S013 within the applicability period that's definedincustomizing(T147-STAGE)?

Answer:The applicability period is used to smooth an old score with a new score.In S013 you have 2 fields for each score. One is the current score, and theother is the cumulative score, which takes the scores from all periods into

19.03.2009 Page 4 of 5


consideration. (example in s013: PWMT1 and PWMT2).

In order to calculate the score for the cumulative field(PWMT2), the systemlooks in s013 for the most recent period that is covered by theapplicability period. The score will be smoothed and saved in the newperiod. For the current field(PWMT1), the system will store the score forthe current period only.

EX. In S013, you have an entry is for June,July and Agust. Now in October,you post a goods receipt and a score for quantity reliability is calculatedand should be saved for a new period in October. A new period will becreated on S013, and the system will search for the most recent periodwhich is available in the applicability period(6 months). In this case, itwill take the scores from Agust and will smooth with the actual score, inorder to calculate the cumulative score(PWMT2). The current score(PWMT1)will be the new score for the period(PWMT1).

If you don't have an entry in the applicability period, then the cumulativescore and the score for the period will always be the same as what was lastrecorded. It is not correct to set the score to zero, since we always havea smoothed score from all periods. The vendor evaluation is not based onperiods, but on the history with this vendor. Why should a vendor get ascore of zero, just because he hasn't delivered anything(it could be thatwe haven't ordered anything for him to deliver). The history has to beconsidered.

-----------------------------------------------------------------------

Question:Why does the system generate error message ML061 'System settings forpurchasing organization xxxx incomplete' when I maintain a vendorevaluation ?

Answer:SAP Note No. 102911

Header Data

Release Status: Released for CustomerReleased on: 01.06.2007 03:39:29Original Lang.: EnglishPriority: Recommendations/additional infoCategory: FAQ

Main Component: MM-PUR-GF-VE Vendor Evaluation

The Note is release-independent

19.03.2009 Page 5 of 5


Related Notes

Number Short Text

834773 S013: Scores aren't cumulated and smoothed from all periods

806834 Calculation of score for Quantity Reliability

806832 Calculation of score for On-time Delivery

568357 Vendor evaluation: wrong on-time delivery scors

512037 Vendor Eval: Cancellation Goods receipt not taken scores

507627 EKS - S012/S013 incorrect

451733 Vendor Evaluation: Reversal of Goods Receipt

Attributes

Attribut Value

Transaction codes OLME

Transaction codes TIME

Documents

SAP OSS Notes on vendor evaluation 1