Skip to main content

Product Archive: MRP

Purpose and prerequisites​

Product Archive: MRP adds manufacturing dependencies to Product Archive Checks. It flags a product being manufactured on an open manufacturing order, a product covered by an active bill of materials, and a component used by an active bill of materials. These findings join the base addon's preflight and retained audit.

Install matching versions of the base addon and native Manufacturing (mrp). This bridge is marked for automatic installation when its package and dependencies are present. It declares no Enterprise-only dependency and creates no standalone menu or application.

The workflow below is source-reviewed for 19.0, with selected comparisons of other versions. No manufacturing, archive, or runtime test was performed for this guide.

Access and setup​

The existing Product Archive Policies form gains three settings visible to Manufacturing managers:

  • Open Manufacturing Orders, default Block.
  • Active Bills of Materials, default Warning.
  • Active BoM Component Use, default Warning.

Each uses Ignore, Warning, or Block. Only Manufacturing managers may change these provider fields. The bridge grants them read/write access to existing policies for their manufacturing settings, but no policy-creation rights. Core policy changes and the policy configuration menu remain restricted to Inventory managers.

Have an administrator provide the appropriate roles or authorised route to an existing policy. Inventory users can run preflight; Inventory managers perform archive and unarchive actions. Manufacturing responsibility alone does not grant archive permission.

Workflow​

  1. Agree the manufacturing severities on the applicable company/category policy. Keep a block for unfinished production when the product must remain available until work is resolved.
  2. Open Archive Preflight from the finished product or component. An Open manufacturing order finding covers manufacturing orders whose state is neither done nor cancelled, including draft orders. Review its quantity and earliest start date.
  3. Review Active bill of materials findings for the product. A variant-specific BoM applies to that variant; a template-level BoM affects the template's relevant variants. Archive an obsolete BoM through the normal Manufacturing workflow only after confirming it is no longer needed.
  4. For a component, inspect Used by an active bill of materials. Replace the component in the legitimate design or archive an obsolete BoM as appropriate. The bridge does not rewrite BoMs automatically.
  5. Resolve or cancel unfinished production through normal manufacturing controls, return to preflight, and select Refresh. Base stock and reservation blockers may remain after the manufacturing finding is resolved.
  6. An Inventory manager selects Safe only or Safe and acknowledged warnings and uses Archive Eligible. Warnings require explicit acknowledgement; a manufacturing block cannot be overridden by that acknowledgement. Review Archive Audits afterward.

Practice scenario​

In an authorised test database, create fictional finished product “Cedar Display Kit” with an active BoM containing “Cedar Fastener”. Leave stock at zero and create no production order. Under the default policy, preflight on the kit should report its active BoM, and preflight on the fastener should report component use. After the obsolete test BoM is archived and preflight refreshed, these manufacturing warnings should disappear. This source-derived scenario was not executed.

Troubleshooting and limitations​

Completed or cancelled manufacturing orders are not selected by this bridge. Active BoMs can still create findings without any open production. Conversely, resolving a BoM finding does not clear physical stock, reservations, or open stock movements detected by the base addon.

An Open link is offered only for a dependency the current user may read. Summary counts can represent several records; the link opens a representative one. Restricted-company dependencies remain effective. The bridge checks finished-product manufacturing orders and active BoM component use; it does not promise a complete engineering-change or subcontracting retirement review.

Qualified catalogue versions are 15.0, 16.0, 17.0, 18.0, 19.0, and 20.0. Older releases adapt manufacturing aggregation to their native APIs. The inspected 18-to-19 provider logic is unchanged apart from packaging metadata; 20.0 migrates the bridge's access declarations. The base archive guide describes additional stock-model and UI differences. Secondary workflows remain unreviewed beyond these comparisons.

Live Test — Odoo 19 is catalogue-qualified; no demo was launched. Choose the exact version in the Corvus catalogue.

Read Product Archive Checks for policy precedence, warning acknowledgement, audit exports, and restoration.