How to Report a Sub-Assembly as Received in EDGEBIC

To report a sub-assembly as received in EDGEBIC by User Solutions, open the job's Scheduled Job BOR, switch to Actual Live, double-click the Sub-Assembly node, choose the received-quantity option when prompted, enter the finished components, and re-schedule. The branch then explodes only the shortfall into work center steps.

This is a stock statement, not a yield statement, and it works through machinery that already existed. For the end-product version see how to report produced quantity on a job; the whole task library is at the EDGEBIC how-to hub.

Before You Start

• The components are finished. A sub-assembly halfway through its own routing is not received stock, and reporting it as such will short the parent.
• You know the good quantity. Scrap and rework are not received units.
• You understand this does not reduce the parent's order quantity. Final assembly still runs for the full order. Only the branch shrinks.
• You are ready to re-schedule. The receipt posts immediately; the branch is re-evaluated on the next run.

The Steps

1. Open the job's Scheduled Job BOR and switch to Actual Live, the routing diagram with a status card per node.
2. Find the Sub-Assembly node. It is the component card that has its own routing beneath it. How the designer shows sub-assembly branches explains the shape.
3. Double-click it. You are asked whether you want to report a received quantity for the sub-assembly, so that the next reschedule builds only the shortfall, or log per-operation actuals instead.
4. Choose the received-quantity option. Choosing the other option takes you to the usual step picker for logging hours or pieces at one of the sub-assembly's machines.
5. Enter the received quantity and read the remaining line before committing.
6. Press Report. A receipt posts for the sub product and its on-hand rises.
7. Re-schedule the job using how to reschedule only the jobs that changed.

How to Check It Worked

The component's on-hand. Open the sub-assembly product's transaction history and confirm a receipt pegged to the job for your quantity. Use how to audit the inventory ledger for a part.

The branch. After the re-run, look at the sub-assembly branch on the diagram or the operations list. With full cover the branch carries no work center steps at all. With partial cover it carries steps for the shortfall only. With no cover, nothing changed, which usually means the on-hand you expected is not there.

The parent. Final assembly should still be sized for the full order quantity. If it shrank, the entry landed on the End Product node instead, which is a different statement. See confirming a sub-assembly versus the end product.

What the Branch Does Next

The received units are ordinary stock of that component from the moment they post, indistinguishable from the same part arriving by any other route. Before exploding a sub-assembly branch, the engine asks whether on-hand covers the requirement, and there are three outcomes.

A parent for 50 with 20 components received manufactures 30 sub-assemblies and assembles 50 parents. That third row of arithmetic is the one worth memorizing.

The mechanics are covered in EDGEBIC sub-assembly scheduling explained and how a sub-assembly feeds its parent job.

Common Mistakes

Reporting a part-finished sub-assembly. If the component still has operations to run, it is not received stock. Reporting it that way tells the engine to skip building units that do not exist, and the parent will be short at assembly.

Expecting the parent quantity to fall. It will not, and it must not. The customer is owed the full order. If the finished items themselves exist, that is an end-product confirmation on a different node.

Choosing per-operation actuals by reflex. The prompt appears because the two are easy to confuse. Received quantity is about inventory. Operation actuals are about a machine step. Answer it deliberately.

Reporting components that belong to another order. Once received, the units are free stock that netting can allocate to whichever job reaches them first. If those parts are committed elsewhere, resolve the allocation before reporting.

Expecting no issue to ever post. One will, when the parent build draws the component. That is ordinary bill-of-material consumption and is exactly what should happen. It is the visible difference between this path and an end-product confirmation, which never issues anything.

Reporting and not re-running. The receipt posts immediately, but the branch is only re-evaluated by a scheduling run.

Next Steps

If the same shop routinely carries finished components in stock, the branch behavior you have just triggered manually is what happens automatically every run. How build-to-stock and consume-from-stock work together covers both directions, and how to let a job consume from stock is the setup side.

If you reported the wrong quantity, how to correct an over-reported production quantity applies to sub-assembly entries as well as end-product ones.

The takeaway

Reporting a sub-assembly as received is a statement about the shelf, not about the order. It raises the component's on-hand, and the existing netting then covers what it can and builds only the shortfall. The parent keeps its full quantity throughout, which is the detail that separates this from an end-product confirmation and the one to check first when the numbers look off. See the platform at EDGEBIC, and read production confirmation explained for the wider feature.