BOM Compare Field Configuration

The comparison behavior for Construction Order lines is managed in the BOM Compare Fields page, which is accessible from the Configure to Order Setup page by choosing Related > BOM Compare Fields.

Each entry references a field from the CCS DM Construction Line table and defines how the field behaves during comparison and update operations. Only the fields explicitly listed here will be processed by the BOM Compare & Update logic.

The comparison fields are described in the following table.

Field	Description	Usage
Include in Insert	Specifies whether the field is included when inserting new lines. This setting determines if the field's value will be copied from source to target if a Construction Order line is newly inserted.	If a line from the "source" is not found in the "target", a new (empty) entry is created in the "target" and all fields marked as Include in Insert are copied from "source" to "target".
Validate in Insert	Specifies whether the information in a field is to be validated when inserting new lines.	Validation is triggered when new lines are inserted.
Include in Modify	Specifies whether the field is included when modifying existing lines. This setting determines if the field is used when comparing lines as well as if the field's value will be updated in the target if the user confirms the change.	When a matching line is found, all fields marked as Include in Modify are compared and only if they are different (and if the user doesn't skip these changes), will they be written to the "target".
Validate in Modify	Specifies whether the information in a field is to be validated when modifying existing lines.	Validation is triggered when existing lines are modified.

This setup allows selective control over which fields in the Construction Order line are:

• Shown in the comparison dialog
• Included in the difference check
• Updated during synchronization

Note

The configuration can be adapted per customer or scenario, making the comparison process flexible and aligned with industry-specific needs.

Example

To ensure that only relevant and intentional data is included in the comparison and update process, system fields might be excluded from the compare and update process while other fields might have all or only some of the options set. For example:

• A field like Description might have:

  • Include in Insert = true
  • Validate in Insert = true
  • Include in Modify = true
  • Validate in Modify = true

• A field like Variant Code might have:

  • Include in Insert = true
  • Validate in Insert = true
  • Include in Modify = false
  • Validate in Modify = false

• A system field like Last Modified Date might have:

  • Include in Insert = false
  • Validate in Insert = false
  • Include in Modify = false
  • Validate in Modify = false

By tracking only certain field changes, settings such as these provide high transparency and reduce the risk of overwriting important changes.

Feedback
Submit feedback for this page .