Autocreate creates 37 purchase orders for one lab fit-out
Contoso's facilities project team submits 180 requisition lines for a lab fit-out. The lines span 12 cost centers, four suppliers, and three need-by dates. All requisitions are approved. The buyer runs autocreate purchase orders using grouping by supplier and cost center, and the system creates 37 purchase orders. Nine of the POs total less than $500, and each of those suppliers charges a $75 small-order fee. Four lines fail budget check because the requested account combination is inactive; two punchout catalog lines were repriced by the supplier from $89 to $94 after requisition approval but before PO creation. The project manager wants one PO per supplier and asks why the system did not consolidate. The buyer also wants to know whether the $5 price increase requires reapproval and how to stop the small-order fees on the next wave.
1. Why did autocreate produce 37 POs instead of four? What grouping and data attributes should the buyer inspect?
Read the worked answer
Autocreate does not group only by the two attributes selected on the screen. It also respects mandatory PO header differences such as ship-to organization, bill-to, currency, payment terms, and need-by date, and it may separate lines by requisitioning business unit or document style. With four suppliers, 12 cost centers, and three need-by dates, the 37 POs are consistent with additional splits beyond supplier plus cost center. The buyer should compare the PO headers to find the attributes that actually differ, rather than assuming the grouping parameter alone controls the result.
Inspect the autocreate grouping options, the requisition line details, and the generated PO headers. If the project manager wants one PO per supplier, the requisitions must be aligned on the attributes that force splits, or the buyer must consolidate manually where policy allows. Creating the POs and then trying to merge them may not be supported; it is better to correct the requisition data or grouping before autocreate.
2. How should the buyer handle the four budget failures and the two punchout price increases?
Read the worked answer
For the budget failures, do not override the budget check blindly. Determine whether the account combination is inactive because it is obsolete or because it is valid only for a different date or business unit. Correct the requisition distribution to a valid account, or have the chart-of-accounts owner activate the account if appropriate. Budget check may pass at requisition and fail at PO because of timing, control settings, or the PO accounting date; confirm which check failed and fix the source data.
For the punchout price changes, compare the new price to the requisition price and the configured price tolerance. A $5 increase on $89 is about 5.6%, which may exceed a common 5% tolerance. If it exceeds tolerance, the requisition should be updated and reapproved, or the PO change should follow the change-order approval path. Do not silently substitute the higher price. If the buyer has authority and the change is within tolerance, document the update; otherwise return it to the requester.
3. What process and configuration controls would reduce small-order fees and PO fragmentation in the next wave?
Read the worked answer
Move repetitive low-value buys to a blanket agreement or a catalog with consolidated releases, and set supplier minimum-order expectations in the agreement or sourcing event. Before autocreate, run a consolidation review: combine requisitions by supplier, ship-to, need-by date, and cost center where policy permits, and set a minimum PO value threshold for buyer review. Use requisition templates or smart forms that guide requesters to the right supplier and agreement, reducing off-contract small orders.
Configure autocreate grouping and defaulting to match the buying pattern, and monitor the number and value of POs created per supplier. For suppliers that charge small-order fees, add a warning or approval at requisition if the projected PO value is below the fee threshold. Do not simply turn off budget check or price tolerance to speed processing; fix the data and consolidate demand.