Source Determination
Source Determination is the MM process by which the system identifies the most appropriate supplier or supply source (contract, scheduling agreement, info record, or quota-arranged vendor) for a material requirement raised via purchase requisition. This topic covers the business purpose, master data drivers (source list, outline agreements, info records, quota arrangements), the automated and manual determination logic, configuration settings that control it, integration with requisition and purchase order processing, common errors and troubleshooting, and differences across ECC and S/4HANA deployments including Fiori-based apps.
Overview
Source Determination is the MM process by which the system identifies the most appropriate supplier or supply source (contract, scheduling agreement, info record, or quota-arranged vendor) for a material requirement raised via purchase requisition. This topic covers the business purpose, master data drivers (source list, outline agreements, info records, quota arrangements), the automated and manual determination logic, configuration settings that control it, integration with requisition and purchase order processing, common errors and troubleshooting, and differences across ECC and S/4HANA deployments including Fiori-based apps.
Lessons in this topic
- Configuring and Applying Source Determination: Source Lists, Quota Arrangements, and Requisition AssignmentLearn how to configure source list requirements, set up quota arrangements, and understand how source assignment flows from purchase requisition through to purchase order creation.
- Introduction to Source Determination: Why the System Needs to Find a VendorUnderstand what source determination is, why it exists, and how the system decides which vendor or agreement should supply a requirement.
- Architecting Source Determination Strategy Across Global Templates and S/4HANA LandscapesArchitect-level guidance on designing a scalable, governable source determination strategy across plants, company codes, and deployment models, covering NFRs, migration, and operational governance.
- Resolving Source Determination Conflicts: Precedence Among Source List, Contracts, and Info RecordsMaster the precedence rules the system applies when multiple valid sourcing objects exist simultaneously, and build a systematic troubleshooting approach for cases where the expected source is not proposed during requisition or PO creation.
- Quota Arrangements: Configuration and Runtime Split LogicLearn 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 maintain quota arrangements correctly for realistic multi-vendor sourcing.
Interview questions covered
- A purchase order for a critical material has multiple schedule lines sourced from two vendors via source determination (source list with quotas), and GR-based invoice verification is active. Partial goods receipts arrive from both vendors against overlapping schedule lines, and FI-AP now shows invoices blocked with quantity variances that don't match either vendor's actual delivery. As the architect, how would you diagnose and resolve this?
- Design a source determination strategy for a global organization with multiple plants sourcing the same service category from regional preferred vendors, while allowing central contract compliance monitoring.
- 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.
- A plant using inbound delivery processing for scheduling agreements finds that source determination in the requisition-to-PO conversion keeps ignoring the source list entry marked as fixed, routing instead to a different vendor. How would you investigate this as an architect?
- In a global source-to-contract process, how does contract hierarchy (centrally negotiated global contracts vs. local distribution contracts) impact source determination logic when a purchase requisition is created at a plant level?
- A plant maintains a source list with three approved vendors for a material, but purchase requisitions keep converting to POs for only one vendor despite the source list allowing all three. What should you check?
- A company wants to apply a quota arrangement to distribute procurement of a material across two vendors, but the material is currently set up with a non-stock, non-valuated material type. Can quota arrangement be used in this scenario, and what material master settings must be verified?
- When designing the migration architecture for source lists in a project integrating S/4HANA with decentralized EWM, what considerations determine whether source lists should be migrated per plant or centrally, and how does this interact with EWM's own sourcing logic?
- Buyers report that certain purchase requisitions for services are not automatically picking up the negotiated contract as source of supply during source determination, forcing manual vendor selection each time. What are the likely root causes and how would you diagnose this?
- In a global template rollout, how should field selection for purchasing info records be governed to balance mandatory pricing controls against country-specific tax and condition requirements?
- A global organization needs an architecture for vendor returns where, once a quality-related return is initiated against a centrally negotiated contract, source determination must temporarily prevent that vendor's contract from being auto-sourced for replenishment purchase requisitions until the quality issue is resolved and closed in FI-AP via credit memo. How would you design this?
- In a global governance model, how should field selection for source list maintenance be controlled to prevent unauthorized changes to fixed source or MRP-relevance flags across regions, while still allowing local buyers operational flexibility?
- A purchase requisition configured for automatic source determination is proposing an unexpected vendor, or in some cases no source at all, when converting to a purchase order. Walk through your diagnostic approach across master data and configuration to isolate the root cause.
- After go-live, business reports that a critical material is being sourced entirely from a single vendor even though quota arrangement was configured to split 60/40 across two vendors. Purchase order history confirms 100% volume to one vendor over three months. How would you diagnose this?
- 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?
- A client integrating Ariba with S/4HANA is using a make-to-order production scenario where Ariba-sourced components trigger PP requisitions. During go-live, purchase requisitions generated by MRP for these PP-driven components are not flowing correctly to Ariba for sourcing. What integration points would you investigate?
- After migrating source lists to S/4HANA as part of a procurement transformation, buyers report that certain materials configured for automatic source determination are failing to find a valid source during requisition conversion, even though the source list appears populated correctly. What would you check?
- During quotation comparison, procurement leadership notices that source determination is automatically defaulting to a higher-priced vendor despite better quotes from alternate vendors on the same RFQ. What configuration and master data areas should be investigated to diagnose this?
- A client uses source lists heavily tied to PP-driven MRP scheduling agreements across plants. During S/4HANA migration, what considerations are critical for migrating source list data without disrupting production planning?
- A centrally negotiated service contract expires mid-quarter and source determination automatically re-routes new release orders to a backup vendor per the source list, but the PO output (message type NEU) is not transmitting to the new vendor, and FI-AP is now seeing GR/IR mismatches on invoices referencing the old vendor's PO numbers. As the architect, how would you diagnose and fix this?