A Satisfied-From-Stock Job Still Shows a Work Center Row: Causes and Fixes

A job whose whole demand is met from inventory should carry exactly one material-shaped row: no work center, no routing step link, and no labor hours, with tracked hours shown as not applicable. EDGEBIC by User Solutions emits that row so a fully covered job stays visible in the plan without holding machine capacity, and the plant-wide anomaly scan flags any covered job that carries a real work center row instead.

The row's shape is load bearing, not cosmetic. Several other checks use it as a skip signal, so a wrongly shaped row produces false findings on every later scan. This post covers what the correct shape is, why the wrong shape spreads, and the correction, alongside the other netting symptoms in the EDGEBIC troubleshooting guide. For the netting mechanism see what is consume-from-stock netting, and for the full-coverage behavior see when an order is fully satisfied from stock.

What You Are Seeing

The job's status says the demand was satisfied from stock, so you expect no work on any machine. The schedule shows an operation anyway: a work center, a time window, and possibly hours. A plant-wide anomaly scan lists the job as critical, saying its row is not material-shaped.

Why It Happens

Cause 1: The Coverage Decision and the Emitted Row Disagree

When netting finds enough stock to cover the whole order, the engine stops scheduling work and emits the single material-shaped row. If a machine operation appears alongside the covered status, the row that was written does not match the decision that was made. Re-running scheduling re-makes the decision and emits the correct shape.

How to tell: the status says fully covered, the quantity issued from stock equals the ordered quantity, and an operation is present anyway.

Cause 2: The Coverage Was Actually Partial

Partial coverage looks similar at a glance and is completely legitimate. Stock covers part of the demand, the remainder is built, and the job shows both a stock movement and real operations. What differs is the status and the quantities.

How to tell: the quantity drawn from stock is less than the ordered quantity, and the operations correspond to the balance that had to be built.

Cause 3: The Job Mixes Completed Work With Later Coverage

Netting runs after completed steps have been preserved, so a job that already has actual work recorded keeps that work. Operations on such a job are history, not a shape error, and they are correct to be there.

How to tell: the operations carry actual start or end dates rather than being purely planned.

Why the Shape Matters Downstream

Three validators treat a row with no work center and no routing link as a stock movement and skip it: the one that looks for a missing routing link on machine work, the one that looks for operations with no assigned resources, and the one that flags a long unexplained gap between sequential steps. Give that row a real work center and none of them skip it any more, so all three start reporting on a row that was never meant to be judged by their rules.

That is the practical cost of leaving this uncorrected: not one row, but a growing set of false findings that make later scans harder to read.

How to Fix It

• Re-run scheduling for the job. The netting decision is re-made and the fully covered case emits the material-shaped row.
• Confirm the coverage quantity in the product's transaction history, filtered to the job number. If the issued quantity is less than the ordered quantity, the coverage was partial and the operations are correct.
• Leave completed work alone. Operations carrying actual dates are history and a reschedule does not move them.
• Re-scan plant-wide to confirm the row cleared and that the three related checks stopped firing on that job.

How to Diagnose It, in Order

1. Run a plant-wide anomaly scan, since this check does not appear on a job-filtered run.
2. Read the job's status and note whether it claims full coverage.
3. Compare ordered quantity against issued quantity in transaction history for the product. That comparison separates full coverage from partial coverage in one step.
4. Check whether the operation carries actual dates. If it does, it is preserved history.
5. Re-run scheduling and re-scan. A clean run clears both the shape row and the false findings it was generating.

How to Prevent It

• Re-scan after any run that involved stock netting, which is the point where shape problems appear.
• Read status and quantity together. Status alone does not tell you whether coverage was full, and the issued quantity does.
• Treat a cluster of unrelated-looking findings on one covered job as a shape symptom, rather than working each one separately. The triage habit is covered in several anomaly checks fired on one job.
• Keep the balance the netting reads honest. Coverage decisions are only as sound as the on-hand figure behind them, which is why a satisfied-from-stock job did not draw down inventory is worth clearing at the same time.