Erro ML014 - ME61 - Chave de ponderação para organização de compras 1000 inexistente

[osmarpetersen]

Estou tentando registrar a primeira avaliação de Fornecedor e uma mensagem de erro está impedindo que eu conclua:

Na configuração existem duas Chaves de Ponderações, a 01 - Materiais e 90 - Serviços e cada um com seus Critérios. Ao informar que a avaliação será criada para a Chave de Ponderação 01, a mensagem de erro continua a aparecer. O SAP não deveria entender que a avaliação será para a Chave de Ponderação 01 e ignorar o 90 ?

Existe uma checagem que verifica se o Critério existe configurado para a Chave de Ponderação, mas a partir do momento que escolho para qual Chave desejo gerar a avaliação, neste caso a 01, o SAP deveria entender que o critério de serviços pertencente à Chave de Ponderação 90 seria ignorado, certo?

Terei que realizar um desenvolvimento para ajustar esta questão ? Não encontrei Nota SAP sobre este erro para o meu cenário.

Obrigado.

Sds,

Osmar Petersen

[JL23 · Accepted solution]

Actually the coding that you showed is for error message ML061, your subject and error screenshots for ML014.

Have you maintained your point scores? Your screenshot does not look as if the customizing is complete, compare it with this pdf

You should also read this OSS note 102911 - ML061: System settings ... are incomplete

see also 38879 - Error ML061 occurs on Transaction ME61 or ME63

[osmarpetersen]

Jürgen, thank you for your attention and help. That's right. I am performing tests and any other need I will review the process.

Best Regards,

Osmar Petersen.

[JL23]

As you should see from the coding, SAP is looking for text.

As you can see from your first screenshot, you have no description for your main criteria 91.

HKRIT = Hauptkrierium = Main criteria

TKRIT = Teilkriterium = Sub criteria

There are many programs where SAP is using the text table instead of the main table to check whether the customizing or master data is available. You should always try to do a complete setup including transaction. Saving time by ignoring descriptions and translations easily turns out in burning time.

[osmarpetersen]

Good Morning.

I completed the texts but the error continues. I do not see a configuration error.

I do not agree with the logic employed in transaction ME61 (or ME63 or background).

If I choose Weighting key 01, the system should understand that what I'm evaluating is Eval. criterion 03. This is how the setup is. As in the example of the following figure:

But the configuration still understands in transaction ME61 that the Eval. criterion 91 belongs to Weighting key 01 or should belong.

I can not set up 91 for 01 because it would be disrupting a development of another company team.

I need to see another way, either by exit or enhancement so the transaction does not validate the 91 for Weighting key 01 because it is not part of my valuation project.

[osmarpetersen]

Good Afternoon, thank you for the answer.

But my setup looks like this:

Transaction ME61, ME63 or via background presents the same error message. By debugging, the program is checking whether Criterion 91 also belongs to Weighting key 01.

All this before entering the next screen. I passed the validation during the debug. In the next screen when I inform 01 the transaction should understand that I want to evaluate the criteria within Weighting key 01, correct?

The system has all the criteria (03 and 91) and at the moment I indicate that the Weighting key will be 01, the transaction does not understand that I need to evaluate only the criteria of Weighting key 01. I still understand that criterion 91 is part of Weighting key 01. Without any logic this form of transaction process.

Should I develop in some enhancement or exit to improve this validation?

Best Regards,

Osmar Petersen

[JL23]

The message says you have not made your customization