Bill of materials: revisions that preserve work already underway

What identifies a materials revision?

A bill needs a product, revision, base quantity, components, units and consumption per unit. Include operations, authorized substitutions and relevant documents when they are part of manufacturing. The design file must relate to the recipe; a new PDF with the same filename cannot explain which part was used. Retain who proposed and approved the change, when it takes effect and which orders are affected.

Business Central documents versions whose starting dates define validity, with certification before activation. Production bill of materials versions. This is a configuration reference. Protection of an already released order still needs testing: an effective date alone does not establish that nobody can modify its recipe.

Does publishing a recipe change work in progress?

Define three cases: an order still being planned, a released order without consumption, and an order with materials already used. A reasonable policy may allow recalculation of the first and require review for the others. If you authorize migration of an order, retain its previous version, new version, differences and treatment of prior consumption. Do not erase movements or retrospectively turn a used component into another that never left the warehouse.

Example: two orders with explainable recipes

O20 is released at 10:00. V2 becomes effective at 11:00, and O10 is released at 12:00. Under this exercise's policy, publishing V2 does not transform O20 into a requirement for 120 screws and 0.80 kg. If changing it is authorized, the difference must remain an explicit approved change. Retrying publication E02 neither creates V3 nor reapplies an adjustment to the same orders.

How do you resolve overlapping changes?

Two people may start from V1: one changes screws and another changes adhesive. Before publishing, compare against the currently effective revision. A last-save-wins combination can lose a necessary change. Show the conflict to its decision owner and preserve both proposals. For an urgent substitution, record its scope: one order, one lot or a validity period; avoid accidentally making it the permanent recipe.

Odoo PLM describes past, current and future versions through engineering change orders, with history and related design files. Version control. Modules and configuration require verification. Available history helps investigation; it does not replace the technical decision about a safe change or prove an implementation delivered by Nightly.

What should the supplier demonstrate?

• Normal: O20 retains V1 and O10 uses V2; quantities, units and effectivity are available for review.
• Exception: a concurrent proposal detects that its base changed; it cannot overwrite the effective recipe without review.
• Started work: migrating an order explains prior consumption and pending changes, with the authorizer's identity.
• Retry: repeating E02 keeps one publication and one application per authorized order.
• Documents: the recipe retrieves its corresponding design and distinguishes it from a later revision's file.

What should you bring to a diagnosis?

Complete the materials revision worksheet with a real recipe and change. The production tracking guide covers progress; footwear size runs test consumption by size. To scope manufacturing software, also bring an order that had already consumed material when its recipe changed. That exception clarifies requirements better than an empty revisions screen.