ME03 — Display Source List
ME03 is used to display source-list entries for a material and plant without changing them. It is most useful when troubleshooting source determination, procurement blocks or why MRP/purchasing selected or rejected a supplier. 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 ME03 — Display Source List. 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· 590 words
Purpose
display source-list entries for a material and plant without changing them. Treat ME03 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
ME03 is typically used when troubleshooting source determination, procurement blocks or why MRP/purchasing selected or rejected a supplier. 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 material and plant from the failing requisition or PO.
- Check the document date against source-list validity.
- Review fixed-source and block indicators.
- Compare listed vendor/agreement with info record, contract and quota arrangement.
- Use the result to explain source determination before changing master data.
Key data objects
These are the fields and business objects that most often explain the result in ME03. Record them in support evidence so the next person can reproduce the same outcome.
- material/plant — verify the exact value, validity/date context and relationship to the source document.
- validity — verify the exact value, validity/date context and relationship to the source document.
- vendor/agreement — verify the exact value, validity/date context and relationship to the source document.
- fixed source — verify the exact value, validity/date context and relationship to the source document.
- MRP/block indicators — 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 ME03 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 ME03 as Display Source List in current S/4HANA purchasing documentation. 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
- Looking at today's validity when the purchase requisition uses another date. Reconcile the exact business document and date before applying a workaround.
- Ignoring a source-list block. Reconcile the exact business document and date before applying a workaround.
- Assuming source list alone determines the source when quota or contracts also participate. 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/me03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.