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, when updates are allowed for the selected target.
The comparison supports:
- BOM structure (Document BOM lines and sub-lines).
- Manufacturing data (e.g., dimensions, attributes, quality, tools, personnel, and skill sets).
- 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
- Service BOM
- Service BOM Archive
A common scenario is Document BOM ↔ Document BOM. The same compare mechanism also supports master data → Document BOM, Document BOM ↔ Construction Order/archive combinations, and archive ↔ archive for historical version comparison.
Important
Changes are applied only when the selected target supports updates.
If the selected target is an archive (Document BOM Archive, Construction Order Archive, or Service BOM Archive), comparison runs in compare-only mode. In this mode, no changes are written to the archived document and update actions (such as Apply Changes, Move, Skip Modify, etc.) are not available. When comparing two archived versions, both are in compare-only mode.
The scope and usage model of the Document 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 differences into the Document BOM.
- Move usage: Movement (re‑parenting) is user‑initiated through Auto Move or Move. Only uniquely matchable "Insert"/"Delete" pairs are converted; ambiguous cases remain "Insert"/"Delete" for user decision.
- Archive target behavior: If the selected target is an archive, compare-only mode applies and no changes can be applied.
- 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
Senden Sie Feedback für diese Seite . (Beachten Sie, dass diese Umfrage auf Englisch ist.)