Source List in SAP MM: The One Concept That Confuses Every Beginner
Summary
A source list in SAP MM (Materials Management) is a core master data record that specifies the approved, blocked, or preferred vendors for a specific material at a given plant during a designated timeframe. It automates source determination during procurement, ensures policy compliance, and seamlessly feeds into Material Requirements Planning (MRP) for efficient supply chain operations.
Picture this: You are managing the procurement team for a massive manufacturing plant. Production is running high, and suddenly, you run out of a critical raw material. A frantic junior buyer rushes to place an order, skips your certified supplier, and accidentally buys subpar inventory from an unverified vendor at double the market price. The production line stalls, costs skyrocket, and your morning goes from peaceful to chaotic.
If that factory used SAP, this nightmare would never happen. Why? Because of a small but mighty feature known as the source list in SAP MM.
If you are a student or professional staring at the vast world of Enterprise Resource Planning (ERP) wondering where to start, mastering master data concepts like the source list is your ticket to a high-paying career in supply chain consulting. Let’s break down exactly what this is, how it works, and why it matters to your future career.
Table of Contents
- What is a Source List in SAP MM?
- Why Does SAP Need a Source List? An Example
- Key Fields in a Source List
- How to Create a Source List in SAP MM (Step-by-Step)
- Source List vs Purchase Info Record vs Outline Agreement: What’s the Difference?
- When Is a Source List Mandatory in SAP MM?
- Why This Small Concept Matters for Your SAP MM Career
- Conclusion
- Frequently Asked Questions
What is a Source List in SAP MM?
In simple English, a source list is your company’s official, pre-approved directory of suppliers for a specific item.
Definition: A source list in SAP MM is a master data record that defines the allowed sources of supply (vendors, internal plants, or long-term contracts) for a specific material within a specific plant over a predefined validity period.
Think of it as SAP’s approved-supplier directory for a material. Once the check is switched on, nothing gets purchased outside this list.
A source list records:
- Which vendors are allowed to supply a material
- The plant the rule applies to
- The validity period (Valid From / Valid To)
- Whether a vendor is the fixed, preferred source
- Whether a vendor is temporarily blocked
- Whether the source feeds into the MRP (Material Requirements Planning) run
Why Does SAP Need a Source List? An Example
Let’s use one example and carry it through the rest of this guide.
Scenario: A manufacturing company procures HR Steel Sheet 2mm for its Pune plant. Three approved vendors can supply this material, but each plays a different role.
| Material | 100-320 (HR Steel Sheet 2mm) |
|---|---|
| Plant | 1100 (Pune) |
| Purchasing Organization | 1100 |
| Vendor Code | Vendor Name | Valid From | Valid To | Fixed | Blocked | MRP |
|---|---|---|---|---|---|---|
| 100234 | Tata Steel Ltd | 01.04.2026 | 30.09.2026 | X | 1 | |
| 100567 | JSW Steel Ltd | 01.04.2026 | 31.03.2027 | 1 | ||
| 100892 | SAIL | 01.04.2026 | 30.06.2026 | X |
Here’s what this entry actually does inside SAP:
- Tata Steel Ltd (100234) is marked Fixed for April to September 2026. During this window, SAP will automatically default to Tata Steel for material 100-320 at Plant 1100, unless a buyer manually overrides it.
- JSW Steel Ltd (100567) is an approved backup, valid for a full year and flagged MRP-relevant. If Tata Steel’s fixed period lapses after 30 September, MRP-driven procurement can fall back on JSW without anyone updating a single master record.
- SAIL (100892) exists in vendor master data but is blocked until 30 June 2026, likely a quality hold or a contract under renegotiation. No purchase order or requisition can be raised against SAIL for this material until the block is lifted.
Now play this forward: a buyer raises a purchase requisition for material 100-320 at Plant 1100 on 15 May 2026. Because the source list is active, SAP checks table EORD in the background, finds Tata Steel Ltd as the valid fixed source, and auto-populates it on the PO; no manual vendor search needed, and no risk of it accidentally going to SAIL.
Without this source list, none of that happens automatically:
- The buyer would have to manually recall which of the three vendors is preferred, backup, or currently on hold
- Nothing would stop a requisition from accidentally reaching SAIL mid-block
- MRP would have no rule to fall back on once Tata Steel’s window closes

Key Fields in a Source List
| Field | What It Means |
|---|---|
| Valid From / Valid To | Time window during which the vendor is approved |
| Vendor | The supplier’s vendor code |
| Purchasing Org | The purchasing organization linked to the plant |
| Fixed Indicator | Marks this vendor as the default, preferred source |
| Blocked Indicator | Temporarily excludes this vendor from procurement |
| MRP Indicator | Decides whether this source feeds into planning-driven procurement |
| Agreement & Item | Links the source to a contract or scheduling agreement, if one exists |
How to Create a Source List in SAP MM (Step-by-Step)
- Go to Logistics → Materials Management → Purchasing → Master Data → Source List → Maintain, or simply enter transaction code ME01.
- Enter the Material Number and Plant on the initial screen.
- On the overview screen, add the Vendor code and Purchasing Organization.
- Set the Valid From and Valid To dates for that vendor’s approval window.
- Tick Fixed if this vendor should be the automatic default. Tick Blocked if the vendor should be excluded for now.
- Set the MRP field to “1” if this source should be picked up automatically during planning runs.
- Save. You’ve just created your first source list entry.
Repeat this for every vendor approved to supply that material to that plant.
Handy tip: Use ME03 to display an existing source list, ME04 to change it, and ME06 to analyze and generate reports across materials.
Source List vs Purchase Info Record vs Outline Agreement: What’s the Difference?
This is probably the most-asked doubt among learners, and it makes sense all three deal with vendors and materials. Here’s the plain-English breakdown:
| Source List | Purchase Info Record (PIR) | Outline Agreement | |
|---|---|---|---|
| Answers | “Who is allowed to supply this?” | “At what price and terms?” | “What’s the long-term deal?” |
| Created with | ME01 | ME11 | ME31K (contract) / ME31L (scheduling agreement) |
| Stores pricing? | No | Yes | Yes |
| Purpose | Vendor approval and source determination | Price, delivery time, vendor terms | Long-term quantity or value commitment |
Easy way to remember it: the source list decides who can sell you the material, the PIR tells you how much it costs, and the outline agreement locks in the long-term deal.
When Is a Source List Mandatory in SAP MM?
It isn’t mandatory by default. SAP forces the check only when:
- The “Source List Required” indicator is switched on in the material master’s Purchasing view, or
- It’s activated at the plant level in customizing (SPRO)
Once switched on, the system blocks a purchase order or requisition if the vendor isn’t listed as a valid source for that material and plant, even if that same vendor exists elsewhere in vendor master data.
Skill Up, Stand Out: Professional SAP Training |
|||
| SAP Certification Courses | |||
| Explore All SAP Courses SAP FICO Course online | SAP MM Course Online | SAP PP Course Online | SAP SD Course Online |
|||
Why This Small Concept Matters for Your SAP MM Career
It’s easy to skim past the source list as just another master data topic. It shouldn’t be, for a few reasons:
- It’s one of the first things interviewers probe, because it shows whether you actually understand source determination logic, not just data entry
- MM consultants use source lists daily on live projects, especially in multi-vendor procurement setups in manufacturing, automotive, and pharma
- It connects directly to MRP, which sits at the core of almost every SAP MM implementation
And the career upside behind learning this properly is real. Salary trackers like PayScale put the average pay for SAP MM-skilled professionals in India at roughly ₹6–6.5 lakh a year in 2026, with freshers typically starting around ₹3.5–6 LPA and experienced consultants crossing ₹15–20 LPA within a few years of solid, hands-on project work. Senior consultants in sectors like automotive and manufacturing often earn well beyond that.
Demand isn’t slowing down either. A large share of enterprises are still midway through their shift to SAP S/4HANA ahead of the ECC support deadline in December 2027, per industry research from Global Growth Insights (2026), which means companies keep hiring MM professionals who understand procurement fundamentals like this one, not just screen navigation.
Take the case of a B.Com graduate who struggled to land a role with just a general commerce degree until he enrolled in a short, project-based online SAP MM course. In his very first interview, he was asked to explain the difference between a source list and a PIR. Because he’d actually practiced creating one using ME01, and not just read the definition, he answered with a real example instead of a memorized line. That one answer moved him to the next round.
That’s the difference hands-on practice makes. If you’re learning SAP MM through a structured, project-based online SAP MM course, like the SAP MM training path at ICA Online, you typically get guided practice on exactly this kind of transaction, so concepts like the source list stop feeling like theory and start feeling like something you’ve actually done.
Conclusion
The source list isn’t complicated once you see it for what it is: an approved-vendor list with a handful of extra rules attached. Get comfortable with ME01, understand how a source list differs from a PIR and an outline agreement, and you’ll have cleared one of the biggest early speed bumps in SAP MM.
If you’re serious about turning this into a real, well-paying career and not just exam-ready theory, practicing these transactions hands-on in a guided environment is where the learning actually sticks. It’s worth exploring a structured SAP MM program, like the one at ICA Online, if you want that practical push forward.
Few related topics for your knowledge
- SAP FICO Vs SAP HANA: Which Is Better
- Analyzing The Procure To Pay Process: A Comprehensive Overview
- How SAP FICO Works In Manufacturing Industry
- SAP FICO Transaction Codes: List Of T-Codes To Remember
- Why Smart Finance Pros Are Rushing To Learn SAP FICO
- 50+ SAP MM Interview Questions and Answers Revealed
Frequently Asked Questions
1. What is a source list in SAP MM?
A source list in SAP MM is a master record showing which vendors are approved to supply a specific material to a plant, within a set time period. Maintained via transaction code ME01, it helps SAP automatically pick the right vendor during purchasing or MRP runs, cutting manual vendor-selection errors.
2. What is the T-code to create a source list in SAP MM?
The main code is ME01 (Create). Related codes: ME03 (Display), ME04 (Change), ME05 (Auto-generate), ME06 (Analyze/Report), ME08 (Send). All source list entries are stored in the background table EORD, which links material, plant, vendor, and validity data together.
3. What is the difference between a source list and a purchase info record (PIR)?
A source list decides which vendors are allowed to supply a material; it’s about approval. A Purchase Info Record (PIR) stores the price, delivery time, and terms for a specific vendor-material pair. Simple way to remember it: source list = who can sell it, PIR = at what price.
4. Is maintaining a source list mandatory in SAP MM?
No, not by default. It becomes mandatory only when the “Source List Required” indicator is switched on in the material master’s Purchasing view, or set at the plant level in customizing (SPRO). Otherwise, it stays optional and is used mainly to streamline vendor selection.
5. Which SAP table stores source list data?
Source list records are stored in table EORD in the SAP database. This table links the material, plant, vendor, validity dates, and indicators such as fixed source or MRP relevance, useful to know for reporting, debugging, or SAP MM interview questions.