Maintaining key in vendor evaluation for porg

how do i maintain weighting key for p org in vendor evaluation?? when i am trying to run vendor evaln for a vendor and porg...i get this msg saying no weighting ke assigned to this porg...plzz telll me abt the settings

thnx i already found it, but thanx for the prompt reply...could u plzz help me further by confirming if by default the weighting keys assigned is 02.??
regards

Similar Messages

Weight Key in Vendor Evaluation

Hi all,
How the Weighting key in Vendor Evaluation is updating for Each Vendor?
If it is automatically Updating why ME6E is required?
regardds
Gibi Philip

hi,
Weighting Keys
A weighting key is an identifier under which the weighting factors for a number of main criteria can be grouped together and saved.
If you know that you will want to carry out an evaluation repeatedly with certain main criteria and certain weighting factors, you can save this combination under a weighting key.
When you carry out the next vendor evaluation, just enter the relevant weighting key instead of entering a weighting factor for each individual criterion. The system then automatically sets all the weighting factors.
There are two possible types of weighting key in the standard system:
Key 01
Key 02
Key 01 permits the equal weighting of all criteria.
Key 02 enables you to evaluate vendors supplying small parts, for example.
The weighting factors under this key are distributed as follows:
Price 5
Quality 3
Delivery 2
Gen. service/support 1
External service provision 2
Hope it explains you the importance ...
Regards
Priyanka.P
AWARD IF HELPFULL

Perform VENDOR EVALUATION for MORE THAN ONE VENDORS at a time

Hello all,
Please guide for any process where i can perform Vendor Evaluation for MORE THAN ONE vendors AT A TIME.
At my location there are around thousand vendors, which are to be evaluated, and difficult to perform the evaluation process one-by-one.
(ME61/ME62/ME63)
Detailed replies with various possibilities would be highly appreciated.
Thanks & Regards,
Joy Ghosh

The vendor evaluation for some thousand vendors at the same time has already been in SAP long before they developed LSMW. The purpose of LSMW is to load data from a legacy system, of course you can (mis-)use it for a lot other things.
But you should not always use LSMW if you are to lazy to go thru the SAP standard menu to find a transaction like ME6G
There you define a job that runs RM06LBAT report.
You first have to define a selection variant for this report. this can be done in SE38 by entering the report name, select variant, clicking display, then entering a name for the variant and clicking Create.

Weighting Key in Vendor Evaluation

Hi all,
Is there any configuration by which the weighting key is defaulted?
My client uses only one weighting key and whenever a vendor evaluation is run, they want the weighting key to be autopopulated.
FYI
No customization. Is this possible only through normal SAP configuration?
Thanks

Generally last time used weighting key will defult to ME61 but if not then you can create screen variant using SHD0 transaction.
Go to SHD0 adn type tcode ME61 and in tran variant type e.g. ZME61
and then hit create button
go through the transaction, every step popup will come
here just enter
and when you see the weighting key popup screen here check the w. content and output only check box (the value of weighting key should be populated)
then hit exit and save
it will ask object
enter the object and save
then from main screen
hit GOTO from header and click on create variant transaction and enter the variant transction code
e.g. ZME61 and save
give this to user
systen will defualt the weighting key
reward the points

Smoothing factors for Vendor Evaluation for Services

Hi Team,
How to apply smoothing factors for Quality and Timeliness of services in External Services. Any help is appreciated.
Thanks
ANita.

Hi ,
I will try to explain with one example
Actually in vendor evaluation , we are going to get only one percentage say for a material A for example Qty reliability - smoothing factor is 0.20
Material A is ordered by so many purchase orders and many goods receipts are done in many times. Goods receipt is done 6 times till now and the score is 80% . Now GR is done for 7th time . If the qty reliability is 100 % for this GR
the score is calculated in the following way
80%0.8+100%0.2 --- this the score after the 7th goods receipt....
Hope now u understand .... If u still have queries please post your feedback...
If u are satisfied , please reward points
Regrads
Mani

Vendor Evaluation for Service

Hi,
Can you anybody explain me how Vendor Evaluation will happen in case of Service and how to activate Vendor Evaluation tab in service entry sheet(ML81N).
Regards
Suresh Kumar Maroli
Consultant-MM

Check
Re: Vendor evaluation - General Service and support

Score problem in vendor evaluation for sub criteria Quantity Reliability...

Hi Experts,
For the subcriteria Quantity Reliability i have calculated the score like below,
pur.order quantity - 1000.
receipt qty - 900.
var = 900-1000/1000 *100 = 10%.
10% var = 90 pts.
old score - 41
new score -90
smoothing factor - .30
41 * (1-.30) + 90 * .30 = 56. Am getting,but
system calculates 59.how.Is there any configuration problem.
I hardly need to solve this.pls anyone help me.
Thanks in advance.
Edited by: Ranganayahi Chandirasekaran on Nov 4, 2009 12:17 PM

Hi,
to answer your question satisfactorily we need to knwo about more details.
what are the minimum delivery factors, overdelivery and underdelivery tolerances?
these all are considered in the score calculations.
to adjust the score the system gives high priority to average score that is 1-smoothing factor.
if you have just updated the score for same delivery then the score calculation is different.
in case of further queries please find the MMSIV document you could find it in some fo the posts.
you will get some more information in one of my earlier posts.
regards,
Adwait Bachuwar

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

Vendor Evaluation-Scoring logic for percentage

Dear Experts,
I have mention below % and score of vendors for sub criteria on-time delivery,it is mention in std SAP..I want to know % value is calculated here? how negative % values is given score?
-          100     On-time del.
1,0       90     On-time del.
2,0         95     On-time del.
10,0         80     On-time del.
20,0         60     On-time del.
30,0         40     On-time del.
40,0         20     On-time del.
50,         5     On-time del.
99,9           1     On-time del.
-5,0            95     On-time del.
-10,0     65     On-time del.
-20,0     75     On-time del.
-30,0     60     On-time del.
-40,0     40     On-time del.
-50,0     20     On-time del.
-60,0     5     On-time del.
-99,9     1     On-time del.
Thanks,

Hi Shyam,
I am also looking for the same.
can u send me the full details of the Vendor Evaluation score % calculation .
and MANUAL, Semi Auromatic, Fully Automatic Evaluation. what is the difference.
what is the function of end user for execute Vendor evaluation for all the VENDORS AT A TIME.?
Regards,
Anthyodaya.

Additional sub criteria for Vendor Evaluation tab in SES (ML81N).

Hi,
I like to add two additional sub criteria for Vendor Evaluation tab in SES (ML81N). Based on which vendor evaluation will be calculated.
1. Safety/Envt Upkeep
2. Morale
These two are added in SPRO->Purchasing->Vendor Evaluation ->Define Criteria. But not displayed in ML81N->Vendor Evaluation tab.
Existing criteria. 1) Quality of Service and 2) Service Timeliness are already available.
Thanks in advance.
Chetan Shah

Hello Chetan,
have you checked note 79166 "MM-SRV Hint: Vendor evaluation for service"?
Define an evaluation criterion for services in Customizing of the vendor evaluation to be able to use the vendor evaluation also for the services management.The main criterion must contain the determination methods 'C' (determination from the quality valuation of the service) and 'D' (determination from the timeliness rating of the service) in the sub-criteria.
Kind Regards
TomT

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 vendors 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 vendors 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 Period Selection

Dear Sir,
We use ME63 for Vendor Evaluation , here we do not find any option to give the period over which Vendor should be Evaluated . We have a requirement that Vendor Evaluation must be based upon the Purchases made during period 1-DEC-2007 to 31-DEC-2008 .
Kindly guide us , as how can be achive it please .
Rgds
B Mittal

Hi
Standard SAP does not provide you such a facility, wherein you can run the vendor evaluation for a specific date range.
There is a days selecion criteria in customizing settings for a purchasing organization wherein you specify the no. of days which needs to be considered for reporting from the current date, the documents that are posted within that date range from the current date are only taken into consideration for vendor evaluation.
You can manually maintain the number of days in the customizing, which needs to be considered for scores calculation.
Thanks
E.Avudaiappan.

Maintaining key in vendor evaluation for porg

Similar Messages

Maybe you are looking for