ME62 — Display Vendor Evaluation
ME62 is used to display vendor evaluation scores and criteria used by classic MM Purchasing vendor evaluation. It is most useful when buyers or auditors need to review supplier performance ratings without changing them. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for ME62 — Display Vendor Evaluation. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 602 words
Esta página ainda não está disponível em português.
Purpose
display vendor evaluation scores and criteria used by classic MM Purchasing vendor evaluation. Treat ME62 as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
ME62 is typically used when buyers or auditors need to review supplier performance ratings without changing them. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Enter vendor and purchasing organization.
- Review overall score and each criterion.
- Check whether scores are automatic, manual or based on current weighting.
- Compare with underlying delivery/quality evidence.
- Use evaluation as one sourcing input rather than the sole supplier decision.
Key data objects
These are the fields and business objects that most often explain the result in ME62. Record them in support evidence so the next person can reproduce the same outcome.
- vendor — verify the exact value, validity/date context and relationship to the source document.
- purchasing organization — verify the exact value, validity/date context and relationship to the source document.
- overall score — verify the exact value, validity/date context and relationship to the source document.
- main/subcriteria — verify the exact value, validity/date context and relationship to the source document.
- evaluation period/history — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the ME62 document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
SAP Help lists ME62 as Display Vendor Evaluation; S/4HANA customers may also use newer supplier evaluation apps and Ariba-based processes. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Comparing scores across purchasing organizations with different criteria. Reconcile the exact business document and date before applying a workaround.
- Treating manually entered scores as objective system facts. Reconcile the exact business document and date before applying a workaround.
- Using classic vendor evaluation where the enterprise has moved to another supplier-performance platform without checking the active process. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the MM/P2P team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me62ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.