Vendor evaluation - deletion of key for evalaution criterion

[Former Member]

Dear All,

In SAP's Vendor Evaluation, I have two Keys for evaluation criteria: key 01 (Standard) and key 02.

I need to remove 01 key, or else to copy values from 02 key to 01 key, and finally remove 02 key. Is it possible? Could this deletion generate any problem?

Thanks a lot!

Regards.

[JL23 · Accepted solution]

you should only delete an entry from customizing if you are certain that it was not used.

Here you have to check table ELBK

Further you must delete it in the right sequence.

In Customizing you have the task for defining the weighting key and then the other task to define the purchasing organization data for vendor evaluation where this key is used.

Hence you need to delete first the purchasing org data before you delete the key.

[Former Member · Accepted solution]

Jürgen,

Thanks a lot for your answer! It's been really helpful.

I would also like to know what happens if the criterion key that I want to delete was already used for an evaluation. Am I able to delete it? Would it cause data issues? I have to point out that we don't need to use again that criterion key for vendor evaluation.

Finally, considering it is the standard, is there any problem in deleting the 01 key?

Thanks and regards.

[JL23 · Accepted solution]

you are certainly able to delete it, as customizing is not checked against transaction data, it can usually not check as customizing is done in a development client while the data is in the production client. The consultant has to know what he does and that he creates inconsistencies when deleting customizing which was in use.

There is no problem if you delete a SAP given key and just use your own (on the other hand I do not understand why one creates an own key instead of changing the existing)

I think you will not really see any issues in this particular case, but I often had errors because of such deletions in other cases, e.g. with purchasing groups and storage locations.

Purchasing groups for example are checked when you archive data like purchase orders. if the purchasing group was deleted, then the program may dump in worst case or just  not consider this record.

Thats why I usually recommend not to delete any used customizing, rename it to do not use and restricting the usage with authorization settings is more secure (I do not know if there is any authorization object for weighting keys)

[Former Member · Accepted solution]

Jürgen,

We have finally removed the 01 weighting key, even with data in ELBK.

The inconsistences generated have been solved running the RM06LBAT report. This report changes the old (and removed) weighting key and replaces that for a new weighting key.

Thanks a lot for your help!

Regards.