Materials

What APS knows about materials

For every manufacturing order, APS reads its Bill of Materials (BOM) from Odoo and computes the components and quantities needed. It also reads:

• Stock on hand — available quantity at this moment
• Incoming POs — quantities arriving on a confirmed date
• Already-allocated quantities — what other in-progress MOs already claim

These come from the same sync that pulls MOs and work centers — no extra setup needed once the connector is configured.

Material-aware scheduling

In the scheduler modal, switch on Respect material availability. Every MO is then delayed until all its BOM components are available.

Available means: in stock or arriving on a PO before the MO needs it. APS computes a per-MO “material floor” date and prevents any operation of that MO from starting earlier.

FIFO supply allocation (priority decides)

When two MOs need the same component and there's not enough to go around, the higher-priority order claims first. Within the same priority, the earlier due date wins. This mirrors the scheduler's sort order — the order you see on screen is the order APS hands out parts.

Concretely: APS walks every MO in scheduling order. For each component it consumes from the supply ledger in PO-arrival order (first-in-first-out). If existing stock fills it, no waiting. If only future POs cover it, the MO's material floor is the latest PO arrival date.

Conflicts

APS flags two material conflict types on operations:

• MATERIAL_SHORTAGE — existing supply records don't cover demand. Surfaced by both Forward (when delaying isn't enough) and Backward post-validation. The MO can't be planned until a PO is added.
• MATERIAL_LATE — supply arrives after the requested start. Surfaced by Backward (just-in-time) runs to highlight orders that can't finish on time without expediting purchasing.

Both surface in the conflict list above the Gantt. Click the operation to see which component is the bottleneck and what date is needed.

The Materials page

Open Materials from the sidebar to see every BOM component across the dataset. Columns:

• Code — internal product code
• Material — product name
• On Hand — current stock
• Reserved — quantity allocated to scheduled MOs
• Available — On Hand minus Reserved
• Shortage — how much you're short, if any
• Status — OK or SHORTAGE

Filter by Status (All / Shortage / OK) or use the search box to match by code or material name. This is the fastest way to spot the part that's holding up your plan.

A part with nothing behind it is a shortage

If a component has no stock and nothing on order, the order that needs it is reported as a shortage. It used to be treated as unconstrained, which meant the worst case — nothing on hand, nothing coming — was the one case that raised no warning at all, while a part you were merely short of did.

One exception: a component that another manufacturing order in the same plan produces is not a shortage. The sub-assembly is sequenced ahead of the order that consumes it, so the part arrives from your own shop floor rather than from stock.

Shortages are shown for the dataset you are looking at. A scenario reports its own, and Live reports Live's.

By default a shortage does not stop the order being scheduled — it is placed and flagged, so production has a date and purchasing can see what to chase. On the scheduler's Custom tab you can ask for the opposite, and have orders with no supply left out of the plan entirely. That withholds the orders above them too: an end item whose sub-assembly has nothing to make it from cannot be finished either, and giving it a date only fills the floor with work that cannot become a finished product. When you publish, the Unplan what this plan leaves out option carries the same decision into Odoo, so those work orders lose their dates there too rather than keeping a start nothing supports.

Pushing an MO ahead of others

To get a specific MO first pick of parts:

1. Raise its priority in Odoo (lower number = higher priority).
2. Or change priority temporarily in an APS scenario, run the scheduler, and observe the new allocation.
3. Or pull in its due date — same priority, earlier date wins the tiebreaker.

Run the scheduler after changes and you'll see other MOs absorb the downstream impact (waiting longer, or hitting MATERIAL_SHORTAGE).