Resolving Source Determination Conflicts: Precedence Among Source List, 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 expected source is not proposed during requisition or PO creation.
Explanation
In mature procurement organizations it is common for a single material/plant combination to have several sourcing objects active at once: a fixed source list entry, one or more purchasing info records, a central contract, and possibly a scheduling agreement, sometimes alongside a quota arrangement. When automatic source determination runs—triggered from a purchase requisition, from MRP-generated planned orders, or from manual 'assign source of supply' actions in requisition or purchase order transactions—the system must resolve conflicts among these objects deterministically, and understanding that resolution order is essential for advanced troubleshooting. The general precedence logic, at a functional level, works roughly as follows. First, the source list is checked, if maintained and marked as relevant/required for the material/plant: any source list entry flagged as blocked removes that vendor from consideration entirely, and any entry flagged as fixed forces that vendor to be used for the period covered, overriding price or quota logic. If a source list exists but no entry is fixed for the current date, the list still acts as an eligibility filter—only vendors present in a valid, non-blocked entry may be proposed. Second, within the eligible set, if a quota arrangement exists and is valid, quota rating determines which specific source among the eligible list receives the requirement, as covered in quota logic. Third, if no source list and no quota arrangement apply, the system falls back to looking for valid outline agreements (contracts or scheduling agreements) and purchasing info records, generally preferring an outline agreement over a plain info record when both exist and are valid for the requirement date and quantity, because outline agreements represent a negotiated commercial commitment. Fourth, when several info records exist without any list, quota, or contract, and the requisition is being manually sourced, the system typically presents the lowest net price info record as the default suggestion, but this is a proposal, not a rule—buyers can override manually unless a fixed source list entry mandates otherwise. Common production issues arise from interactions among these layers. A frequent case: procurement negotiates a new contract with better pricing, but the source list still marks the old vendor as fixed, so purchase requisitions keep proposing the old vendor despite the new contract having lower net price—because a fixed source list entry overrides price comparison entirely. Another case: a quota arrangement is correctly configured, but a blocked source list entry for one of the quota vendors silently removes that vendor from the eligible pool, so all volume goes to the remaining vendor and the intended split never materializes; the quota configuration itself is not wrong, the eligibility filter upstream is. A systematic troubleshooting approach for 'wrong or missing source proposed' issues should proceed in this order: (1) confirm whether a source list exists for the material/plant and check for fixed or blocked entries and their validity dates; (2) confirm whether the material is flagged for quota arrangement usage and, if so, review the quota items, their block status, and validity periods; (3) verify that the expected outline agreement or info record is valid (not expired, not blocked, correct plant, correct purchasing organization) for the requirement date and quantity; (4) check for plant-specific versus purchasing-organization-level info records if the client uses cross-plant or central purchasing organizations, since a source valid at one org level may not automatically be visible to a requisition created in a different plant's purchasing area; (5) review requisition or purchase order release strategy and any account assignment restrictions that might filter out otherwise valid sources. This layered diagnostic habit prevents consultants from jumping straight to 'the info record is missing' when the real blocker is a fixed source list entry two layers upstream. In S/4HANA, the underlying precedence concepts remain functionally similar to ECC, though Fiona apps for managing source lists and quota arrangements provide more consolidated visibility, and some clients extend or automate sourcing decisions using additional cloud procurement capabilities layered on top of core ERP source determination; behavior of any such extensions is deployment-specific and should be validated against the client's actual configuration rather than assumed.
Real project scenario
During a contract renegotiation project, a procurement team signed a new corporate contract offering a five percent price reduction versus the incumbent vendor. After go-live of the new pricing condition, purchase requisitions in the affected plant continued proposing the old vendor at the old price. The consultant traced the issue by first checking the source list, where a fixed entry for the old vendor with no end date was still active from an earlier sourcing decision two years prior. Because a fixed source list entry overrides price-based selection entirely, the new contract was never even evaluated as a candidate source. The resolution was to end-date the old fixed entry and create a new fixed (or non-fixed, per policy) entry pointing to the new contract, after which subsequent requisitions correctly proposed the negotiated pricing.
Common mistakes
• Assuming the system always picks the lowest-price source, without checking for a fixed source list entry that overrides price comparison. • Troubleshooting quota arrangement configuration first when the actual root cause is an eligibility filter (blocked or missing source list entry) upstream. • Overlooking validity date gaps or overlaps across source list entries, contracts, and info records when a requirement's date falls in an unmaintained window. • Not accounting for purchasing organization or cross-plant sourcing scope, leading to 'missing' sources that are actually valid but not visible to the requisition's purchasing context. • Failing to communicate to business users that manual override at the requisition or PO level is possible even when automatic determination proposes an undesired source, unless policy explicitly restricts overrides.
Best practices
• Maintain end dates on fixed source list entries whenever a sourcing decision is time-bound, to avoid stale overrides after contract renegotiations. • Document the precedence hierarchy (source list eligibility, then quota, then contract/info record) in project runbooks for support teams. • When introducing a new contract, proactively review and update related source list entries in the same change, not as an afterthought. • Use a standard diagnostic checklist for sourcing issues that checks eligibility filters before ranking logic before pricing. • Validate purchasing organization and plant scope explicitly when a source appears missing, especially in centralized or cross-plant purchasing structures.
Interview angle
Advanced interview questions in this area probe whether a candidate can articulate the precedence order among source list, quota arrangement, and outline agreements/info records, and whether they follow a structured, layered troubleshooting method rather than guessing. Strong candidates emphasize checking eligibility filters (source list fixed/blocked status and validity dates) before diagnosing quota or pricing logic, and can give a concrete example of a fixed source list entry silently overriding a better-priced contract.