Introduction to Source Determination: Why the System Needs to Find a Vendor
Understand what source determination is, why it exists, and how the system decides which vendor or agreement should supply a requirement.
Explanation
Source determination answers a deceptively simple question every time a purchase requisition is created: who should supply this material, and under what commercial terms? Without this process, every requisition would require a buyer to manually search for vendors, prices, and agreements, which does not scale in an organization processing thousands of requisitions daily. Source determination automates or assists this decision by consulting existing master data: purchasing info records, outline agreements (contracts and scheduling agreements), source lists, and quota arrangements. At its core, source determination is triggered when a requisition is created or when a buyer manually invokes source assignment in transactions used for requisition processing. The system looks at the material and plant on the requisition line, then searches for valid sources. A purchasing info record tells the system what price and vendor conditions exist historically for a material-vendor combination. An outline agreement (contract) represents a longer-term commercial understanding, often with pricing conditions and a validity period, against which release orders or purchase orders can be created. A scheduling agreement is similar but is typically used for recurring deliveries with scheduled quantities. A source list is a specific master record per material-plant that explicitly lists which vendors are permitted (or blocked) sources for that material at that plant, potentially with a fixed source indicator that mandates a single preferred vendor. Quota arrangements go further by splitting future requirement quantities across multiple vendors according to defined percentages, useful when a company deliberately wants to maintain multiple suppliers for risk mitigation. Why does this matter in practice? Consider a manufacturing plant that buys a critical raw material from three approved vendors to avoid single-source risk. Without quota arrangements, buyers might inconsistently favor one vendor, defeating the risk mitigation strategy. Source determination formalizes this policy in the system so that requirement quantities are automatically apportioned according to the agreed quota percentages, and the system also considers vendor evaluation and blocked status. From a beginner's perspective, it is important to understand the difference between automatic and manual source determination. When source determination is fully automated and unambiguous (for example, only one valid contract exists), the system can directly propose or even auto-assign the source on the requisition. When multiple valid sources exist, or when no source list entry is mandatory, the system may present a list of possible sources for the buyer to choose from, or leave the assignment for manual purchase order creation. Source determination is also closely tied to organizational data: plant, purchasing organization, and purchasing group all influence which agreements and info records are considered valid, since these master data objects are typically maintained at specific organizational levels. A vendor's info record maintained for one purchasing organization will not automatically apply to another purchasing organization unless explicitly extended. Understanding source determination is foundational before moving into procurement configuration, since almost every downstream document (purchase order, goods receipt, invoice) depends on the correct source having been identified early in the process. Errors or gaps here cascade into delayed procurement, manual rework by buyers, and potential maverick buying outside negotiated agreements.
Real project scenario
A mid-size discrete manufacturing company implementing S/4HANA Private Cloud found that plant buyers were manually searching for vendor prices in spreadsheets before creating purchase orders, even though contracts existed in the system. During the design workshop, the functional consultant discovered that source lists had not been maintained for the top 200 strategic materials, so the system never proposed the existing contracts automatically. The project team prioritized building source lists and validating quota arrangements for multi-sourced materials as a prerequisite to go-live, since this directly reduced requisition processing time and enforced compliance with already-negotiated contract pricing.
Common mistakes
• Assuming outline agreements are automatically used without a source list entry or without the agreement being flagged relevant to source determination. • Confusing purchasing info records (informational pricing/vendor data) with source list entries (which govern which vendors are valid sources). • Not considering that master data is organization-level specific, so an info record or contract at one purchasing organization will not appear for another without extension. • Overlooking blocked or expired source list entries, causing the system to reject an otherwise valid vendor at requisition time. • Treating quota arrangements as static; failing to review and adjust quota percentages as vendor performance or supply risk changes over time.
Best practices
• Maintain source lists proactively for strategically sourced or single/dual-sourced materials rather than relying only on ad hoc info records. • Align quota arrangement percentages with the organization's actual sourcing strategy and review them periodically with category managers. • Ensure purchasing organization and plant assignments are correctly modeled before troubleshooting apparent 'missing vendor' issues in source determination. • Document business rules for when manual source override is permitted versus when contract compliance must be enforced. • Communicate to requisitioners and buyers how automatic source proposals work, to build trust in the system's suggestions and reduce manual bypassing.
Interview angle
Interviewers commonly ask candidates to explain the difference between a source list, an outline agreement, and a quota arrangement, and to describe what happens when a requisition is created for a material with multiple valid sources. A strong answer explains the master data hierarchy, notes the organizational-level dependency, and gives a concrete example of when automatic versus manual source assignment would occur.