How to Find Which Products Have No Routing in EDGEBIC

To find which products have no routing in EDGEBIC by User Solutions, open the Product tab and group or filter the grid on the BOR status column. That column sorts the entire catalog into three buckets: products with a routing, products with none, and products carrying the red legacy multiple-routings warning. One click tells you which products will fail the moment somebody orders them. For the wider list of catalog faults and their symptoms, read product setup mistakes in EDGEBIC.

Before you start

• You can see the Product tab and its grid.
• You understand what a missing routing costs: a product with no operations cannot be scheduled, so any order raised against it fails rather than queuing.
• You have time to act on the result. This audit is worth running right after a bulk import and before any major scheduling run.
• Know the two possible fixes in advance. Either build the routing, or retire the product if it is genuinely obsolete.

Steps

1. Open the Product tab from the main navigation.
2. Find the BOR column in the grid. It shows one of three values per row.
3. Group by that column, or use its filter, to bucket the catalog by routing readiness. The three values are:

4. Work the No BOR bucket first. For each product, decide whether it needs a routing built or whether it is obsolete.
5. Build the routing for products that need one. See how to build a routing step by step.
6. Retire the obsolete ones rather than deleting them. See how to deactivate a product without losing history.
7. Then work the legacy multiple-routings bucket. Filter the BOR column to that value to find them all at once, open the routing module, keep the correct routing, and remove the others.

There is a compressed version of the same signal in the grid: a checkmark beside the product identifier means it has a routing, and a circle means it does not.

What changes when you fix the gaps

Nothing changes from running the audit itself. It is a read-only view of the catalog.

What changes is what happens on the next scheduling run. Products that had no operations now have them, so orders raised against those products can be placed on work centers instead of failing. Products carrying the ambiguous multiple-routings condition now resolve to one known routing, so what gets scheduled and what gets quoted stop depending on which routing happened to be picked.

Retired products stop appearing in the dropdowns that create new orders, which removes the source of the next round of unschedulable jobs.

How to check it worked

1. Re-group the grid on the BOR column. The No BOR bucket should now contain only products you deliberately left without a routing, typically purchased materials that appear inside other routings.
2. Confirm the red multiple-routings bucket is empty.
3. Open one of the routings you built and confirm it has steps in it. A routing that exists with no steps passes the column's check and still cannot be scheduled.
4. Run the anomaly checks and confirm they come back clean. See how to run and read the anomaly report.
5. Run the scheduler and confirm no job fails for a missing routing.

Common mistakes

Stopping at the column. A routing with zero steps reads as present and still gives the engine nothing to place. Open the ones you are unsure about.

Treating every no-routing row as a fault. Purchased materials and components that only appear inside other products' routings correctly have none of their own. Filter those out mentally before you start building.

Ignoring the legacy warning because nothing has broken. Multiple routings on one product do not error. They quietly make scheduling and quoting ambiguous, which is worse than a clean failure.

Renaming a work center without updating the routings. Routing steps carry the work center's name alongside its reference. When the name goes stale, the step resolves to no work center, books no capacity, and shows up in the anomaly checks rather than in the routing column.

All the single-task recipes are indexed in the EDGEBIC how-to library. To see how routing readiness feeds a finite capacity plan, visit the EDGEBIC product page.