How to find the late purchase orders that matter in SYSPRO

What SYSPRO already gives you

In SYSPRO, everything you need to judge a late purchase order already exists, spread across programs built for different jobs:

• Purchase Order Query: open purchase orders and their lines, with the due date of each line.
• Inventory Query: on-hand, allocated and on-order quantities for a stock code, by warehouse.
• Inventory movements: the issues and receipts that give you a usage history.
• Reports and SYSPRO's export 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.

The method, step by step

1. List the open lines past their due date

Export open purchase order lines with stock code, supplier, quantity outstanding and due date. Keep the lines whose due date is before today. If you record supplier confirmations, use the latest confirmed date and flag the lines never confirmed.

2. Get stock and usage for each stock code

Take available quantity per stock code and warehouse. For usage, sum issues over a fixed window, for example the last 12 weeks, from inventory movements: issues to jobs and sales. Use the same window for every stock code.

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 stock code 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 stock code 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, fastener kit: 9 days late. 6,000 available, usage of about 100 a day: 60 days of cover. Another line arrives next week.
• Line B, hydraulic pump: 3 days late, never confirmed. 8 available, usage of about 2 a day: 4 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 stock code by stock code works for ten late lines, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy stock codes 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 stock code 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

Can I do this without custom reports?

Yes, if you can export open purchase order lines and stock by warehouse to Excel. A simple spreadsheet then computes cover and sorts the lines.

What about multiple warehouses?

Compute cover per stock code and warehouse, and check whether another warehouse could cover the gap before you call the supplier.

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 SYSPRO, it works from structured exports: available quantity by stock code and warehouse, and open purchase order lines. There is no WERISCO SYSPRO connector today. The first supply chain audit needs only those two exports. WERISCO reads only; nothing is written back to SYSPRO, and your team decides what to chase.