Update and Compare Document BOMs

The Document BOM represents a resolved configuration coming from a checklist. It is the finalized structure that can be produced or purchased; it is not a growing "engineering workbench". The Document BOM Compare & Update feature lets you bring a changed configuration into an existing Document BOM with full user control over differences.

With this feature, you can:

  • Detect insertions, deletions, modifications, and movements based on configured fields and hierarchy context.
  • Review all changes in a structured page with clear visual indicators.
  • Apply selected changes to the target while retaining full control over each step.

The comparison logic supports:

  • BOM structure (Document BOM lines and sub‑lines).
  • Manufacturing data (dimensions, attributes, quality, tools, personnel).
  • Field‑level differences based on BOM Compare Fields configuration.
  • Recursive comparison for nested lines (via the Belongs to Entry No. field).
  • Movement consolidation: uniquely detectable parent changes are shown as "Move" (instead of "Insert" and "Delete").
  • User‑confirmed updates for full control.

Comparison can be initiated from several sources and applied to the selected target:

  • Master data (Production BOM and Routing / Master BOM)
  • Document BOM
  • Document BOM Archive
  • Construction Order
  • Construction Order Archive
Note

The same compare mechanism supports master data → Document BOM and Document BOM ↔ Construction Order/archive combinations. Changes are always applied to the document you select as the target during compare.

The intended usage model and scope of the Compare BOM Compare & Update feature includes:

  • Purpose: Resolve and maintain a producible/purchasable configuration; not an engineering backlog. Document BOMs do not "grow" over time like Construction Orders.
  • Change process: When the configuration changes (via checklist), run the Update BOM action (Compare & Update) to adopt the differences into the Document BOM.
  • Move usage: Movement (re‑parenting) is user‑initiated (Auto Move or Move). Only uniquely matchable "Insert"/"Delete" pairs are converted; ambiguous cases remain "Insert"/"Delete".
  • Out of scope: Generic auto‑adoption across many live configurations and continuous growth management are not part of Document BOM compare; use master data for structural modeling.

The following table outlines related tasks, with links to the topics that describe them.

To See
Configure the fields to be included in the compare and update process. BOM Compare Field Configuration
Learn how the Insert, Delete, Modify, and Move actions are determined and applied during BOM compare and update. Action Types in BOM Compare
Use the Document BOM Compare & Update feature. Compare and Update Document BOMs

Feedback
Submit feedback for this page .