About Editing a Configured Bill of Materials

Changes you make to a configured BOM creates or modifies the applicability information on the EBOM relationships.

Configured Parts typically cannot be revised. Changes to the BOM structure are applied to the same revision using the change action process. The configured part is assigned as a proposed change with the requested change value as “For Update”. The changes are applied to the same revision when the CA is completed.

This page discusses:

See Also
Editing a Configured Part Bill of Materials

Limitations When Editing a Configured Bill of Materials

Some limitations exist when you edit a configured bill of materials.

The Resequence, Change Position with, and Copy To commands can be applied only to unconfigured parts in a configured BOM.

Add Existing

The Add Existing command creates a new markup row when a part to add is selected and submitted. The markup displays the CA under the Add column and the CA's applicability under the Proposed Applicability column. In the Proposed Applicability and Current Applicability columns, pause over the cell to display long applicability expressions.

When you select a part to add and click Save:

  • A new EBOM relationship is created using the Work Under change.
  • Proposed applicability is set on the EBOM relationship.
  • The screen is refreshed and the markup is shown as committed.

Remove

These rules apply to a Remove operation on released EBOM relationships with no other pending changes.

  • The Work Under change should have intersecting applicability with the applicability (current) of the selected row.
  • Until you release the previous change on the EBOM, subsequent changes cannot be proposed.
  • The change object used to add a part to the BOM must be in the In Work state to remove the part from the BOM.
Note: If the selected work under change CA and the CA used to add the part are the same, you can remove the added part even though adding the part has not been validated.
Note: If the selected work under change CA and CA used to add the part are different, you cannot remove the added part from the BOM until the CA that added the part is complete.

Provided the above rules are satisfied, a remove operation strikes out the selected row and the following steps are executed when you click Save:

  • Update the proposed applicability on the EBOM relationship.
  • Refresh the EBOM page to show the updated proposed applicability.

Using Remove in a Configured BOM in Development Mode

Removing a child part from a preliminary configured part disconnects the child part altogether. A CA is not required to remove the part.

Edit Usage Attributes

Editing a configured BOM works as a series of cut and constraint operations. The following rules apply to edit operations on released EBOM relationships with no other pending changes, unless the Work Under change editing the relationship is the same as the pending change that added the relationship:

Rules

  • The Work Under change should have intersecting applicability with the (current) applicability of the selected row. If there is no intersecting applicability between the Work Under change and the selected row, the operation is blocked with an error message.
  • Any pending CA can be used to edit as long as there is intersecting applicability. The resultant proposed applicability after an edit operation will be:
    • The existing current applicability minus the intersecting applicability for the old row.
    • the applicability of the work under change for the new row.

Provided the above rules are satisfied, an edit operation shows the selected row as modified and on clicking Save, the following steps are executed:

  • Update the proposed applicability on the EBOM relationship.
  • Create an EBOM relationship with updated attributes (the ones that are edited).
  • Set proposed applicability on the new EBOM relationship.
  • Refresh the EBOM page to show the updated proposed applicability.
Note: The current applicability on the modified row will display the full range of production for the assembly.

Replace

The Replace option replaces a BOM component with a new or existing part for a specific set of units and uses. The rules below apply to a replace operation on released EBOM relationships with no other pending changes, unless the context change performing the replace operation is the same as the pending change that added the relationship.

  • The context change should have intersecting applicability with the (current) applicability of the selected row. If there is no intersecting applicability between the work under change and the selected row, the operation is blocked.
  • Any pending CA can be used to replace as long as there is intersecting applicability. The resultant proposed applicability after a replace operation is:
    • the existing current applicability minus the intersecting applicability for the old row.
    • the named applicability of the work under change for the new row.

Provided the above rules are satisfied, a replace operation strikes out the selected row and on clicking Save, the following steps are executed:

  • Update proposed applicability on the replaced from EBOM relationship.
  • Create an EBOM relationship using the replacement part.
  • Set Proposed applicability on the new EBOM relationship.
  • Refresh the EBOM page to show the updated proposed applicability.
Note: The Current applicability for the replacement part displays the current applicability from the source relationship.

After you replace the BOM component with the new part, you can select the Configuration View in the EBOM Refinements window to see how the BOM appears before and after the change. If you select Official as the configuration view, the current BOM is shown. In this view, the existing component shows the current applicability and the proposed applicability is 'Invalid' since proposed change won't include the component. Conversely, when you select Projected as the configuration view, the existing component is not listed and the replacement part is shown with the proposed applicability. The current applicability in both views is the same because the range of production for the assembly hasn't changed.

Using Replace By Existing in a Configured BOM in Development Mode

Replace a part in a configured BOM that is in development phase without using a CA. By default, the current applicability of the replacement part will be the same as that of the part that you replace. However, it can be updated before applying. On saving these changes, the older EBOM relationships are disconnected, and a new EBOM relationship is established.

Proposed Evolution Effectivity

Proposed Evolution Effectivity applies only to configured parts.

Effectivity can be Unit, Date, Product Revision. See Building or Editing an Effectivity Expression. You can edit this field only when the configured part is not under change management.

Variant Effectivity

You can always edit the variant effectivity but if the parent part is change-enabled, you must first select a Work Under CA. This column will always be available with CMM has a mandatory co-reg of PDA and PDM which includes Variant Management

Evolution Effectivity

Evolution Effectivity applies only to configured parts.

Applicability Constraint

Changes you make to a configured BOM may be constrained based on the ranges in values of any current applicability that is applied to the BOM.

For example, assume that the current applicability is:

Table 1. Table 1
Part F/N Proposed Applicability Current Applicability CA Add CA Remove
Assembly1 1 ModelA[1-100] CA-000

This means that the current applicability, as indicated in change action CA-000, specifies that instances 1 through 100 of Assembly1 have the F/N "1". Now, assume that you want to change the applicability as follows:

Table 2. Table 2
Part F/N Proposed Applicability Current Applicability CA Add CA Remove
Assembly1
1 ModelA[1-49] ModelA[1-100] CA-000 CA-001
2 ModelA[50-100] ModelA[1-100] CA-001

This means that the proposed applicability, as indicated in change action CA-001, specifies that instances 1 through 49 of Assembly1 will have the F/N "1" and instances 50 through 100 will have the F/N "2". Because the ranges of the proposed applicability (1-49 and 50-100) fall within the range of the current applicability, no constraint is applied. When a proposed applicability falls outside the range, the constraint limits the proposed applicability to that of the current applicability. For example, if the proposed applicability defined in CA-001 is ModelA[50-110], the proposed applicability would be constrained to ModelA[50-100], the same as indicated in Table 2 above. The current applicability shows ModelA[1-100] because the range of production for the assembly is still 1-100, although there are modifications within that range based on the proposed effectivities as shown in the BOM.

Extended Applicability

In the example above, the current applicability constrains the build to a range of 1-100. To extend the applicability, for a particular use, the same part may be added with the same usage definition with the applicability as ModelA[101-250]. This can be done using change process where CA with applicability ModelA[101-250] be defined and performing add operation.

Remove Applicability

You can remove the applicability for a BOM component at any time using the change action that defines the applicability for that component. When the CA is released, the component is removed from the structure.