How to Find Orphan Jobs with No Demand in EDGEBIC

Finding orphan jobs with no demand in EDGEBIC starts at the Unassigned group on the sales order grouped view. In EDGEBIC by User Solutions that group collects every manufacturing order with no sales order link, so it is where jobs no customer order accounts for surface. The catch is that some of those jobs belong there: builds created to satisfy stock or a build plan carry no order link by design. The real skill is telling a legitimate stock build from a job that lost its demand. This guide covers both.

For the grouped view itself, read how to link a sales order to a job. For the broader order workflow, see how to enter and manage sales orders. This is documented behavior of EDGEBIC; the full task set is in the how-to hub.

Before You Start

• You need the schedule orders view (the manufacturing order grid) open.
• Understand that a job's link to an order is a property of the job: it either references a sales order or it does not.
• Know that stock builds and MPS builds carry no link by design.

Step 1: Switch to Sales Order Group Mode

On the schedule orders view, click the sales order group view mode toggle. The flat job list regroups into a tree: each sales order becomes a parent row with its jobs nested beneath.

Step 2: Open the Unassigned Group

Scroll to the bottom of the tree for the Unassigned group. It collects every manufacturing order with no sales order link, ordered by when it was created. This is your working list of jobs with no order behind them.

Step 3: Separate the Two Populations

The Unassigned group holds two kinds of jobs, and the whole task is telling them apart.

Replenishment builds and MPS builds exist to satisfy stock or a build plan rather than a named customer line, so they legitimately carry no sales order link. They are recognizable by their source tag and job number pattern. Set them aside.

Step 4: Identify the True Orphans

What remains after filtering out the stock and plan builds are the real orphans: jobs that look like customer work but carry no order link and no stock or MPS source. For each, work out the cause:

• Lost its link. A job that should belong to an order but is not attached. Reattach it to the right order.
• Created without demand. A job entered manually with no order and no plan behind it. Decide whether it should exist at all.
• Demand since removed. The order it satisfied was closed or deleted, leaving the job behind. Decide whether the job is still wanted.

The Other Kind of Orphan: A Released Bucket with No Job

There is a mirror-image case worth knowing. On the MPS grid, a bucket you firmed shows as Released and points to the build-to-stock order it created. If that order is later deleted or cancelled, the demand plan now points at a job that no longer exists: an orphan link rather than an orphan job. EDGEBIC handles this on the grid by demoting the affected row back to Firm, with its committed quantity intact and no order attached, the next time the grid loads. The system's anomaly report also flags the state, so a Released row with a dead link does not sit unnoticed.

The fix is the reverse of finding an orphan job: instead of hunting a job with no demand, you re-firm demand that lost its job. Confirm the demoted bucket's quantity and firm it again to create a fresh order and re-establish the link. For that step, see how to firm an MPS quantity into a job.

What This Tells You

A job with genuinely no demand is producing stock nobody asked for, which ties up capacity and material. Finding these is a housekeeping discipline: the Unassigned group makes them visible, and separating the legitimate stock builds from the true orphans turns a long list into a short one worth acting on. For the demand side that these jobs are missing, see how sales orders drive demand.

Triage in Practice

When the Unassigned group is long, the fast route is to read the source of each job rather than inspect them one by one. Replenishment builds carry a source tag and a job number that marks them as stock-driven; MPS builds carry their own source tag and job number pattern. Both have a plan behind them and can be set aside in a single pass, which usually clears most of the list. What remains are jobs that look like customer work but carry neither a sales order link nor a stock or plan source. Those are the genuine orphans. For each, the decision is binary: reattach it to the order it belongs to, or, if it was created with no demand at all, cancel it. Reading source first is what turns dozens of rows into a short, actionable shortlist.

How to Check It Worked

Confirm the Unassigned group lists the jobs you expect, and that filtering out the replenishment and MPS builds by their source leaves a short review list. A known stock build should appear here (correctly), and a job you know satisfies a live customer order should not. If a genuine customer job is sitting in Unassigned, that is the finding: its link is missing and needs restoring.

Common Mistakes

• Treating the whole group as errors. Replenishment and MPS builds belong in Unassigned by design. Only jobs with no stock or plan source and no order link are true orphans.
• Deleting a stock build because it has no order. A build tagged as replenishment or MPS-sourced has demand behind it. Deleting it removes real planned supply.
• Ignoring a customer job that landed in Unassigned. That is the exact case worth acting on: a job that should be linked and is not.
• Assuming the group updates itself as you work. The grouped view reads jobs at load time. After you reattach or cancel jobs, refresh to see the group settle.

What Comes Next

Reattaching an orphan means understanding the order it belongs to, so revisit how to link a sales order to a job. If the missing demand was a closed order, see how to close a sales order for how closing removes demand. The how-to hub links every neighboring task.