How to Report Produced Quantity on a Job in EDGEBIC

To report produced quantity in EDGEBIC by User Solutions, open the job's Scheduled Job BOR, switch to Actual Live, double-click the End Product node, enter the good units already made, press Report, then re-schedule the job. The order keeps its original quantity and the plan covers only the remainder.

This is the fix for a job whose schedule still reserves capacity for work that is physically finished. The concept behind it is in production confirmation explained; the full task library is at the EDGEBIC how-to hub.

Before You Start

• You know the good quantity that physically exists. Scrap and rework are not produced units, and reporting them inflates stock and under-plans the job.
• You are reporting on the end product, the item the order is for. For a finished component, use how to report a sub-assembly as received instead.
• You accept that on-hand for the finished product will rise by the quantity you report. That is correct: those units are in the plant.
• You are prepared to re-schedule afterwards. Reporting records the fact; the run is what changes the plan.

The Steps

1. Open the job's Scheduled Job BOR. Reach it from the job on the Schedule View or from the Job View cockpit.
2. Switch to Actual Live. The routing renders as a diagram with a status card per node. See the Actual Live screen explained.
3. Double-click the End Product node, the card at the top of the diagram. It represents the item the order is for, and it is the only node that reduces the job's build quantity.
4. Read the header. It names the product, the job, and the order quantity, and it adds the quantity already reported when earlier confirmations exist. Confirm you are on the right job before typing anything.
5. Enter the produced quantity. Good units only, and only what is not already reported, because entries accumulate.
6. Check the remaining line. The dialog shows how much will be left to build after this entry, against the order quantity. That figure is what the scheduler will plan for.
7. Press Report. A confirmation entry posts to the inventory ledger, pegged to the job and the product, and on-hand rises.
8. Re-schedule the job. Use the targeted route in how to reschedule only the jobs that changed.

How to Check It Worked

Three checks, in order.

The ledger. Open the product's transaction history and look for a production confirmation entry pegged to the job, with your quantity and a comment naming the node type. Use how to audit the inventory ledger for a part. On-hand should have risen by exactly the reported quantity, with nothing issued back out.

The hours. After the re-run, the job's planned hours should have fallen in proportion. An order for 100 that needed 300 hours and now carries 50 confirmed should schedule about 150 hours. Read the totals on the Job View header.

The order. The order quantity should be unchanged. If it moved, something edited the order rather than reporting production, and the two are not interchangeable.

Common Mistakes

Editing the order quantity instead. It produces the same hours today and costs you the record of what the customer ordered, every margin comparison against it, and the ability to explain a shipment of 100 against an order that now reads 50. Report the production and leave the order alone.

Reporting gross instead of good. Scrap and rework are not produced units. Reporting them puts stock on the books that does not exist and shrinks the build below what the job still owes.

Reporting a cumulative total on top of earlier entries. Confirmations add up. If 20 is already reported and 35 units now exist, report 15, not 35. The header shows the already-reported figure precisely so this is visible before you type.

Double-clicking a work center step. That opens the per-operation actuals flow, which records hours or pieces at one machine. Useful, and a completely different statement. Only the End Product node reduces the build.

Reporting and not re-running. The confirmation is recorded the moment you press Report, but the plan is what the last scheduling run produced. Until you re-run, the Gantt still shows the full job.

Assuming stock will not move. On a stocked finished product the new on-hand is ordinary stock, and the next run can allocate it back to the same order through normal netting. The arithmetic still lands correctly, but the ledger will show an issue you did not personally enter.

When the Whole Order Is Produced

Report the full order quantity and the job schedules no work center operations at all. It still appears in the plan carrying a single row that reserves no machine time, because a job that disappears entirely from a run is indistinguishable from one that failed to schedule.

Over-reporting is allowed. The dialog warns and lets you proceed, and the remaining build is held at zero rather than going negative. Nothing flags the excess afterwards, so the on-hand figure will simply be high by the amount over-reported. If that happens, see how to correct an over-reported production quantity.

Next Steps

Marking the job complete after partial confirmations is safe: completion posts only the unconfirmed remainder, so the totals reconcile without a manual adjustment. See how to complete an operation for the operation-level step.

If the job also has finished units of the same part sitting in stock from another source, the two compose in a fixed order, described in consume from stock netting: confirmed subtracts first, then stock, then what is left gets built.

The takeaway

Reporting produced quantity is the honest way to release capacity that was reserved for finished work. One number, one node, one re-run, and the order keeps saying what the customer asked for. Keep the entries to good units, add rather than restate, and always re-schedule so the plan catches up with the pallet. See where this sits in the platform at EDGEBIC, and read why an end-product confirmation does not consume stock for the rule that governs its inventory effect.