As finished goods come off the line they're scanned; the ERP then posts the production. This screen compares scanned against posted, daily, by warehouse.
The three states, and what they mean:
- Posted — scanned and the ERP has recorded it. Done.
- Awaiting — scanned, ERP response still pending. This is normal timing, not a problem: the posting process is asynchronous and typically catches up within the shift. Awaiting items are shown neutrally — they need patience, not action.
- Failed — the ERP rejected the posting. This is the red state, the only one that needs a person, and each failure shows what was rejected so it can be fixed at the source.
If you take one thing from this screen: don't chase "awaiting". Chase red.
Reading the breakdown by production line
The full breakdown lists a row for every stock code scanned that day, grouped by item type, with a Line column beside the stock code. A stock code built on three lines appears three times, once per line, each with its own scanned, posted and awaiting figures. That is how you see which line is carrying a gap rather than only that the stock code has one.
The group lines above the rows — Mattress, Base, and so on — are subtotals across several production lines, so they show no line of their own.
Two things worth knowing when the numbers are compared:
- The day's totals do not change because work was recorded on more lines. Splitting a stock code across its lines divides the same scans; it does not add any.
- Days older than about four months show "not recorded" in the Line column. The scan detail those days were built from has aged out of the feed, so the line genuinely was not kept. It is never a guess and never hidden.
The warehouse summary counts stock codes, not rows, so it still reads as a count of items. It also says how many production lines ran in that warehouse on the day.
Top lines awaiting SYSPRO lists the eight largest gaps on the day, each named to its production line. Where one line is behind, it shows up here as a run of rows against the same line.
How fresh is it, and what "Refresh now" does
The daily figures are built by a rollup that runs every hour on the hour. The day you have open shows when its figures were last built. If the newest day is older than yesterday, the rollup has not run — that is a fault, not a quiet day, and support should be told.
Refresh now asks the rollup to run again straight away. It says plainly what happened:
- Rollup asked to run — reopen the day in a minute or two.
- That request did not reach the rollup. Nothing has been re-run. — the figures on screen are unchanged. The rollup either could not be reached or has not been set up for your company; either way it needs support, and the screen will not pretend otherwise.