Configuring and Applying Source Determination: Source Lists, Quota Arrangements, 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.
Explanation
Moving beyond the conceptual overview, intermediate-level source determination work involves configuring how strictly the system enforces source rules and understanding the technical flow that happens when a requisition is created or processed. A key configuration decision is whether a source list is mandatory for a given material or plant. This is controlled through material master settings and plant-level purchasing configuration that determine whether the system requires an active source list entry before allowing a purchase order to be created for that material at that plant. When source list enforcement is active, creating a purchase order for a vendor not present in the source list, or attempting to bypass an existing fixed source, results in a system error or warning depending on configuration. This enforcement is a control mechanism: procurement leadership uses it to prevent maverick buying and to guarantee that negotiated contract pricing is actually used. Within the source list itself, each entry ties a vendor to a material and plant for a validity period, and may include a fixed source indicator (marking the vendor as the mandatory single source during that period), a blocked indicator (explicitly disallowing a vendor even if other master data suggests they are valid), and a reference to a relevant outline agreement or info record. When more than one valid, non-blocked source list entry exists without a fixed indicator, the system typically presents multiple options for the buyer or requisitioner to choose during assignment, rather than auto-selecting one. Quota arrangements add a further layer of automation for recurring demand. A quota arrangement record for a material-plant combination defines participating vendors along with quota percentages (or quota base quantities) and rules such as minimum quota allocation quantity. As requirement quantities are consumed against each vendor over time, the system's quota tracking evaluates which vendor is next entitled to receive the following requirement based on remaining quota share, helping automatically balance orders across multiple approved suppliers according to the negotiated split, such as a 60/40 arrangement between two approved vendors for a critical component. The requisition-to-order flow typically works like this: a purchase requisition is created (manually, via MRP planning run, or via other demand sources). At creation or during processing, the system attempts source determination by checking, in a logical sequence, whether a source list entry exists and is mandatory, whether a quota arrangement applies, and whether valid outline agreements or info records exist. If a single unambiguous source is found, the system can propose or assign it directly to the requisition line. If multiple sources are valid, the requisition may carry an indication that assignment is still needed, prompting a buyer to complete source assignment before or during conversion of the requisition into a purchase order or release against a scheduling agreement/contract. From an integration standpoint, when a purchase order is finally created referencing an outline agreement, the system copies pricing conditions, delivery terms, and other data from that agreement, ensuring commercial consistency with what was negotiated. If the assignment instead goes through an info record without an outline agreement, default pricing and vendor data come from that record, but without a legally binding agreement structure. Understanding this distinction is critical for consultants configuring procurement processes, since it determines what commercial controls and reporting (spend against contract, contract utilization) are available downstream. Troubleshooting in this space often involves determining why a requisition failed to propose a source (checking source list validity dates, checking if the vendor is blocked, verifying plant and purchasing organization consistency) or why an unexpected vendor was selected (checking quota consumption history and quota base quantities).
Real project scenario
During a rollout at a chemical manufacturing company, buyers reported that purchase requisitions for a key packaging material were repeatedly proposing an already-exhausted vendor instead of rotating to the second approved supplier as expected under a 70/30 quota arrangement. Investigation by the functional consultant revealed that the quota arrangement's validity period had lapsed and had not been renewed after a contract extension, causing the system to fall back to info record-based determination and default to the primary vendor from historical pricing data. The fix involved renewing the quota arrangement validity, documenting a renewal checklist for procurement operations, and adding a periodic governance review to catch expiring quota and source list validity periods before they caused sourcing imbalances.
Common mistakes
โข Making a source list mandatory for materials without first ensuring valid, non-expired source list entries exist, which blocks purchase order creation entirely. โข Allowing quota arrangement validity periods to lapse silently, causing unintended fallback to a single vendor and defeating multi-sourcing strategy. โข Confusing fixed source list entries (single mandatory vendor) with quota arrangements (percentage-based multi-vendor split), leading to conflicting configuration. โข Forgetting that blocked source list entries override otherwise valid outline agreements, causing confusion when a contract exists but the vendor is still rejected. โข Not validating organizational-level consistency (plant, purchasing organization) when troubleshooting why an outline agreement is not being proposed as a source.
Best practices
โข Set source list mandatory enforcement only for materials where contract compliance is a genuine business requirement, to avoid unnecessary purchase order creation blocks. โข Establish a periodic governance process to review and renew source list and quota arrangement validity periods before expiration. โข Use fixed source list indicators sparingly and only when a single supplier relationship is deliberate, since it removes buyer flexibility entirely. โข Test quota arrangement behavior with realistic demand simulation before go-live to confirm the percentage split behaves as the business expects. โข Maintain clear documentation distinguishing which materials use quota-based multi-sourcing versus fixed single-source strategies, for audit and onboarding purposes.
Interview angle
A frequent scenario-based question asks the candidate to diagnose why a requisition did not propose the expected contract or vendor. Strong candidates walk through a structured troubleshooting sequence: check source list mandatory setting and validity, check blocked indicators, check quota arrangement validity and remaining quota, then check outline agreement and info record validity and organizational assignment, demonstrating a systematic rather than guess-based diagnostic approach.