ME41 — Create Request for Quotation
ME41 is used to create RFQs for selected vendors and procurement requirements so quotations can be collected and compared. It is most useful when sourcing needs competitive vendor pricing before a purchase order or contract is awarded. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains ME41 — Create Request for Quotation — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 575 words
Esta página ainda não está disponível em português.
Purpose
create RFQs for selected vendors and procurement requirements so quotations can be collected and compared. The key is to treat ME41 as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
ME41 is typically used when sourcing needs competitive vendor pricing before a purchase order or contract is awarded. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Create the RFQ with clear material/service scope and delivery requirements.
- Assign the intended vendors.
- Review communication/output details.
- Track vendor quotations against the same commercial requirement.
- Use quotation comparison before awarding the source.
Key data objects
These fields and business objects usually explain the result in ME41. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- RFQ number — verify the exact value, status, organizational context and date relevance.
- vendor — verify the exact value, status, organizational context and date relevance.
- material/service — verify the exact value, status, organizational context and date relevance.
- quantity/date — verify the exact value, status, organizational context and date relevance.
- quotation deadline — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
Classic RFQ transactions remain available in S/4HANA, while strategic sourcing may be handled in SAP Ariba or Fiori-based sourcing processes. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Sending vendors inconsistent quantities or dates and later comparing incomparable quotations. Check the complete document flow before applying a workaround.
- Creating an RFQ when a contract/source already governs the purchase. Check the complete document flow before applying a workaround.
- Skipping output verification and assuming the supplier received the RFQ. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me41ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.