How to find the late purchase orders that matter in Epicor

What Epicor already gives you

In Epicor Kinetic, everything you need to judge a late purchase order already exists, spread across screens and tables built for different jobs:

• Purchase order releases: each PO line is delivered through one or more releases, each with a due date and, when the supplier confirms, a promise date (table PORel).
• Part Tracker: on-hand quantity by warehouse and bin for a part.
• Time Phase: for one part, supply and demand in date order with the projected balance.
• Part transactions (table PartTran): every receipt and issue, which gives you a usage history.
• BAQs (Business Activity Queries): the tool that joins these tables into one exportable list.

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. Build a BAQ of late, open PO releases

Join PO header, PO detail and PO release, keep the open releases whose due date is before today, and show part, supplier, quantity, due date and promise date. Export it. Use the promise date when the supplier gave one and the due date otherwise, and flag the releases with no promise date: their date is still your request.

2. Get stock and usage for each part

Take on-hand quantity per part and warehouse. For usage, sum the quantities issued over a fixed window, for example the last 12 weeks, from part transactions: issues to jobs for components and shipments to customers for finished goods. Use the same window for every part.

3. Compare days of cover with the real arrival date

Days of cover = on-hand quantity / average daily usage. For each late release, take the date you now expect it to arrive. Check Time Phase for another receipt on the same part that arrives earlier. If cover runs out before any receipt, the release is a shortage risk.

4. Sort by days of cover, shortest first

Among the shortage risks, the part 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 due and promise dates and days late: when you call the supplier, you are discussing facts.

Illustrative example, not a customer result

Two releases from the same BAQ:

• Release A, machined flange: 14 days late. 900 on hand, usage of about 15 a day: 60 days of cover. Another release arrives next week.
• Release B, sensor harness: 1 day late, no promise date. 40 on hand, usage of about 10 a day: 4 days of cover. No other open release.

Sorted by days late, release A comes first. Sorted by days of cover, release B does, and release B is the one that can stop production this week.

Where the manual method breaks

• It does not scale. Opening Time Phase part by part works for ten late releases, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy parts make a 12-week average misleading. Flag them rather than trusting the number.
• Dates are only as good as their maintenance. If promise dates are not entered, the release still carries the original due date.
• Days of cover tells you when a part runs out, not which job or customer order it affects. Linking the two still needs your planners and your bill of materials.

How WERISCO does it

WERISCO automates the data work behind these steps: it reads every open release, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. With Epicor, it works from BAQ exports: on-hand quantity by part and warehouse, and open PO releases. There is no WERISCO Epicor connector today; see the Epicor integration page. The first supply chain audit needs only those two exports. WERISCO reads only; nothing is written back to Epicor, and your team decides what to chase.