MRP says raise a PR. The planner raises it two days later — after reviewing the report manually.
MRP output tells planners which materials need to be purchased and when. But the translation from MRP output to a raised purchase requisition is a manual step — the planner reviews the MRP exception report, assesses the requirement, and creates the PR in the ERP one by one. In operations with hundreds of active materials, this process takes hours and is never fully complete before the next MRP run makes the previous output obsolete.
The delay between an MRP gap being identified and a PR being raised is where procurement lead time is consumed. A material with a 5-day supplier lead time that has its PR raised 2 days late arrives 2 days after the production line needs it. The shortage was visible from the day the MRP ran. The response was 2 days slow.
A purchase requisition is a calculation — the required quantity minus available stock minus inbound coverage equals the PR quantity, and the required date minus supplier lead time equals the PR date. This calculation runs in seconds and does not require a planner to do it manually for every material every morning. HublerX generates PRs automatically from the live MRP position — raising them the moment a material crosses the configured trigger threshold, routing them to the buyer with the correct preferred supplier and quantity, and escalating overdue approvals without a manual chase.
Live workflow view
The step-by-step sequence
- 1
Live MRP position monitored continuously
HublerX maintains a live material requirements position — demand from confirmed work orders, available stock, and inbound PO coverage — updated whenever any input changes. PR trigger thresholds are evaluated continuously against this position, not once at the end of an overnight batch run.
Continuous · real time - 2
PR trigger threshold breached
When a material's projected stock position falls below the configured PR trigger threshold — typically safety stock plus the quantity needed to cover the production plan through the supplier lead time — HublerX identifies the required PR quantity, the required delivery date, and the preferred supplier from the ERP vendor master.
On threshold breach · real time - 3
Purchase requisition generated automatically
HublerX creates the purchase requisition in the ERP automatically — with the correct material code, quantity, required delivery date, preferred supplier, and cost centre. The PR is created as a draft pending buyer review, not submitted directly to the supplier.
Immediately on threshold breach - 4
Buyer notified for review and approval
The responsible buyer receives the PR notification with the material, quantity, supplier, required date, and the MRP signal that triggered it — so the buyer understands why the PR was raised and can confirm or adjust before converting to a PO. PRs above a configured value threshold require a second approval.
On PR creation - 5
Overdue PRs escalated automatically
Where a PR has not been approved or converted to a PO within the configured time window — accounting for the supplier lead time and the production requirement date — HublerX escalates the overdue PR to the procurement manager with the number of days remaining before the production shortage becomes critical.
On approval deadline breach - 6
PR converted to PO and coverage confirmed
When the buyer approves the PR and converts it to a PO, HublerX updates the material coverage position in the live MRP — the projected stock now reflects the inbound PO. If the PO covers the requirement, the shortage alert is closed. If a partial PO is raised, the remaining gap stays open.
On PO creation
Results are directional. PR automation effectiveness depends on MRP data quality, vendor master completeness, and buyer approval responsiveness.
See how PR automation works in your operation
30 minutes. Your ERP. Your material planning process.