Source Determination
MM / P2Pbeginner

MM Source Determination Part 1: How SAP Finds the Right Supplier

Key takeaway

Source determination proposes suppliers for requisitions and POs automatically. Learn the sources — info records, contracts, scheduling agreements, source lists, quota arrangements — and the basic logic that decides which one wins.

What this complete series covers

Learn Source Determination in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for
Best for SAP consultants, developers, and learners who want a practical understanding of Source Determination.
Prerequisites
Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome
By the end, you should be able to explain Source Determination clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: MM Source Determination Part 1: How SAP Finds the Right Supplier

    Understand what source determination is, why it exists, and how the system decides which vendor or agreement should supply a requirement.

  2. Part 2: MM Source Determination Part 2: Source Lists and Requisition Assignment

    Learn how to configure source list requirements, set up quota arrangements, and understand how source assignment flows from purchase requisition through to purchase order creation.

  3. Part 3: MM Source Determination Part 3: Quota Arrangements — Configuration and Split Logic

    Learn how quota arrangements distribute procurement quantities across multiple sources of supply, how the quota rating is calculated at each requirement, and how to configure and m

  4. Part 4: MM Source Determination Part 4: Architecting Source Determination for Global Templates

    Architect-level guidance on designing a scalable, governable source determination strategy across plants, company codes, and deployment models, covering NFRs, migration, and operational governance.

  5. Part 5: MM Source Determination Part 5: Resolving Conflicts Between Source Lists, Contracts and Info Records

    Master the precedence rules the system applies when multiple valid sourcing objects exist simultaneously, and build a systematic troubleshooting approach for cases where the expect

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ Possible sources: info records, contracts, scheduling agreements, source lists, quota arrangements.

✅ Precedence: quota arrangement → source list (fixed source) → outline agreements → info records.

✅ A unique source is assigned automatically; several sources leave the choice to the buyer.

✅ Source lists can be mandatory and can block suppliers.

⚠️ Without maintained sources, every PR needs manual buyer work.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: How SAP finds the right supplier

Part 2: Source lists and requisition assignment

Part 3: Quota arrangements

Part 4: Architecting source determination for global templates

Part 5: Resolving source determination conflicts

━━━━━━━━━━━━━━━━━━━━
▶ 1. SOURCES

  • Info record: supplier price per material.
  • Contract / scheduling agreement: negotiated long-term terms.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SOURCE LISTS

  • Allowed suppliers per material/plant/period; fixed or blocked.

━━━━━━━━━━━━━━━━━━━━
▶ 3. QUOTA ARRANGEMENTS

  • Split requirements by percentages.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PRECEDENCE

  • Quota → source list → agreements → info records.

━━━━━━━━━━━━━━━━━━━━
▶ 5. AUTOMATION

  • Automatic source determination in PRs/MRP; auto PO.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Maintain an info record and a contract.
  2. Create a source list with the contract as fixed source.
  3. Create a PR with automatic source determination.

✅ CHECKPOINT: the PR is assigned to the contract.

Code example

ABAP Code
===== STEP 1: sources =====ME11 info record | ME31K contract | ME31L scheduling agreement | ME01 source list | MEQ1 quota arrangement ===== STEP 2: precedence =====Quota arrangement → source list (fixed) → outline agreements → info records (regular supplier) ===== STEP 3: automation =====PR automatic source determination → ME59N automatic PO

Real project scenario

A mid-size manufacturer implemented S/4HANA without source lists or quotas; buyers assigned suppliers to 3,000 PRs monthly. Maintaining contracts, source lists with fixed sources for single-sourced materials and quotas for dual-sourced ones automated 70% of assignments.

Common mistakes

  • No sources maintained.
  • Conflicting fixed sources.
  • Expired contracts still in source lists.
  • Ignoring quotas.
  • Manual assignment as default.

Best practices

  • Maintain sources for regular buys.
  • One fixed source per period.
  • Align source lists with contracts.
  • Use quotas for multi-sourcing.
  • Monitor unsourced PRs.

Interview angle

Questions: "What is source determination?", "Which sources exist?", "What is the precedence?"
Strong answer: info records, agreements, source lists, quotas; precedence; automatic assignment; mandatory source lists.

Practice this lesson

Quick check

1. Buyers assign suppliers to thousands of PRs manually each month. What reduces this most?

2. Which sources can source determination propose?

3. What is the usual precedence of source determination?

Interview questions

1. What is Source Determination in the context of Service Procurement, and how does it differ when applied to material versus service line items in a purchase requisition?

Answer it in your own words first, then compare.

2. A buyer notices that the price shown on the purchasing info record does not match the last PO price for a material-vendor combination. Walk through how you would investigate this discrepancy.

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics