ME43 — Display Request for Quotation
ME43 is used to display an RFQ sent to a supplier, including items, quantities, dates and communication-relevant data. It is most useful when procurement needs to review the sourcing request before comparing supplier quotations or diagnosing RFQ output. 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 ME43 — Display Request for Quotation. 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· 591 words
Esta página aún no está disponible en español.
Purpose
display an RFQ sent to a supplier, including items, quantities, dates and communication-relevant data. Treat ME43 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
ME43 is typically used when procurement needs to review the sourcing request before comparing supplier quotations or diagnosing RFQ output. 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
- Open the RFQ number from sourcing records.
- Review vendor and purchasing organization.
- Check item scope, quantities and dates.
- Compare the RFQ with received quotation data.
- Review message/output history if the supplier claims not to have received it.
Key data objects
These are the fields and business objects that most often explain the result in ME43. Record them in support evidence so the next person can reproduce the same outcome.
- RFQ number — verify the exact value, validity/date context and relationship to the source document.
- vendor — verify the exact value, validity/date context and relationship to the source document.
- item/material — verify the exact value, validity/date context and relationship to the source document.
- quantity/delivery date — verify the exact value, validity/date context and relationship to the source document.
- submission deadline — 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 ME43 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 ME43 as Display RFQ in S/4HANA purchasing display functions. 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
- Confusing the RFQ with the supplier's quotation response. Reconcile the exact business document and date before applying a workaround.
- Comparing a quotation against a later-changed RFQ without history context. Reconcile the exact business document and date before applying a workaround.
- Assuming document creation proves successful output. 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/me43ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.