Editing BOM Attributes

If you are performing a mass change to the BOM in addition to raising a CR, the Edit Bill of Materials form opens after the Mass BOM Update so you can change the attributes of the BOM.

Notes:
  • When Engineering BOM Management is synchronized with CATIA or the Native app, the product in CATIA or the Native app is updated whenever you make a change to a level 1 part in Engineering BOM Management.
  • When Engineering BOM Management is synchronized with CATIA or the Native app, the product in CATIA or the Native app is updated whenever you make a change to a level 1 part in Engineering BOM Management.

Before you begin: See the BOM attribute descriptions at:BOM Attributes.
  1. If you want the changes to be applied to only selected assemblies, check the assemblies that you want to change.
  2. Click the Enable Edit Mode icon.
  3. Under the Mass Update drop-down list, select the name of the attribute to change.
  4. In the text field, enter the attribute value.
  5. Under Mass Update, click Apply to selected to apply changes only to checked assemblies, or click Apply to all to apply changes to all assemblies.
  6. Click Save and click the Enable Edit Mode icon.

    A BOM markup is created for each of the affected assemblies for the mass change operation and connected to the current released version of the assembly and to the CR. A markup can be saved using either a CO or CR.

    Note: ECRs created in version 14x and earlier may be used as CRs in this version.

    BOM Markups created during the Mass Change process contain concise information regarding only the modifications made, that is, only addition, deletion or replacement information. It may not contain the full BOM information of the assembly part.

    The final processing associates the selected assemblies to the newly created or existing CR with the relationship Proposed Markup. For each selected assembly, it checks whether that assembly is a part or a specification and performs the following logic:

    If the selected assembly from the Where Used page is a part, the system checks the relationship chosen from the list in the Parts section.

    • If this relationship is Request Part Revision, then the system checks whether the chosen relationship exists between the selected part and the CR. If that assembly is already connected with a Request Part Obsolescence relationship to this CR, then that assembly is ignored.
    • If the relationship Request Part Revision does not exist, then the system forms the relationships Request Part Revision and Raised Against CR between this CR and the selected assemblies. Also, the system copies the user-specified Specific Description of Change to the Specific Description of Change attribute to the corresponding attributes of each Request Part Revision connection that will be created.
    • If the relationship Request Part Revision does exist, then the system appends the user-specified Specific Description of Change to the Specific Description of Change attribute to the corresponding attributes of each Request Part Revision connection that already exists between the CR and the part.
    • If the Request Part Obsolescence relationship is chosen, then the system checks whether the chosen relationship exists between the selected part and the CR.
    • If the relationship Request Part Obsolescence does not exist, then the system forms the relationship Request Part Obsolescence and copies the user-specified Specific Description of Change to the Specific Description of Change attribute to the corresponding attributes of each Request Part Obsolescence connection that will be created.
    • If the relationship Request Part Obsolescence does exist, then the system appends the user-specified Specific Description of Change to the Specific Description of Change attribute to the corresponding attributes of each Request Part Obsolescence connection that already exists between the CR and the part.

    If the selected assembly in the Where Used page is a specification, then the system checks whether the relationship Request Specification Revision exists between the CR and the specification.

    • If the relationship Request Specification Revision does exist, the system appends the user-specified Specific Description of Change to the Specific Description of Change attribute of each Request Specification Revision connection that already exists between the CR and the specification.
    • If the relationship Request Specification Revision does not exist, the system forms the relationships Request Specification Revision and copies the user- specified Specific Description of Change to the Specific Description of Change attribute of each Request Specification Revision connection.