How to find the late purchase orders that matter in Infor
Purchase order lines tell you which orders are late. Item availability tells you whether that hurts. How to put the two together in Infor CloudSuite Industrial.
What Infor already gives you
In Infor CloudSuite Industrial (also known as SyteLine), everything you need to judge a late purchase order already exists, spread across forms built for different jobs:
- Purchase order lines: each line carries a due date and, when the vendor confirms, a promise date.
- Item availability: on-hand, allocated and incoming quantities for an item, by warehouse.
- Material transactions: every issue and receipt, which gives you a usage history.
- Reports and exports to Excel: the usual way to put these lists side by side.
Each one answers part of the question. None of them ranks your late orders by the stock risk behind them. A past-due purchase order list sorted by date tells you who is late, not who to call first.
If you run another Infor ERP (M3, LN, Visual), the screen names differ but the method is the same: open purchase order lines with dates, stock by item, and a usage history.
The method, step by step
1. List the open lines past their due or promise date
Export open purchase order lines with item, vendor, quantity still to receive, due date and promise date. Keep the lines whose promise date (or due date, when the vendor never confirmed) is before today, and flag the lines never confirmed.
2. Get stock and usage for each item
Take on-hand quantity per item and warehouse. For usage, sum issues over a fixed window, for example the last 12 weeks, from material transactions: issues to jobs and shipments to customers. Use the same window for every item.
3. Compare days of cover with the real arrival date
Days of cover = available quantity / average daily usage. For each late line, take the date you now expect it, and check for another open line on the same item that arrives earlier. If cover runs out before any receipt, the line is a shortage risk.
4. Sort by days of cover, shortest first
Among the shortage risks, the item with the fewest days of cover goes to the top. That is your chase list for today. For each line, write down stock, usage, cover, the promised date and days late: when you call the supplier, you are discussing facts.
Illustrative example, not a customer result
Two lines from the same export:
- Line A, steel tube: 15 days late. 2,000 on hand, usage of about 40 a day: 50 days of cover. Another line arrives next week.
- Line B, gear motor: 2 days late, no promise date. 30 on hand, usage of about 10 a day: 3 days of cover. No other open line.
Sorted by days late, line A comes first. Sorted by days of cover, line B does, and line B is the one that can stop production this week.
Where the manual method breaks
- It does not scale. Checking cover item by item works for ten late lines, not for two hundred every Monday.
- Usage needs care. New, seasonal or lumpy items make a 12-week average misleading. Flag them rather than trusting the number.
- Dates are only as good as their maintenance. If supplier confirmations are not entered, the line still carries your requested date.
- Days of cover tells you when a item runs out, not which job or customer order it affects. Linking the two still needs your planners and your bill of materials.
Questions people ask
Does this work in Infor M3 or LN?
Yes. The screens differ, but every Infor ERP holds open purchase order lines with dates, on-hand stock and transaction history, which is all the method needs.
Which date should I trust?
The vendor's latest promise date when there is one. A line with only your due date has no vendor commitment behind it.
How WERISCO does it
WERISCO automates the data work behind these steps: it reads every open line, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. With Infor, it works from structured exports: on-hand quantity by item and warehouse, and open purchase order lines. There is no WERISCO Infor connector today; see the Infor integration page. The first supply chain audit needs only those two exports. WERISCO reads only; nothing is written back to Infor, and your team decides what to chase.
One supply-chain shock, decoded in numbers, and what a data-driven plant does about it.
