About BOM Markups

When you add or delete components of a BOM or change the attributes on the BOM relationship, the changes are listed as BOM markups. The Responsible Design Engineer or any assignees to a change object can create a BOM or item markup. The assignee of the proposed change becomes the markup owner. To view the BOM markups for a part, open the part and select the Engineering BOM category. BOM markups for the part are listed in the Markup tab.

BOM markups apply to the assembly and are saved as separate entities until they are applied.

Note: Parts that you add or move using drag and drop are saved without markup.

This page discusses:

See Also
Markups Related to a Part
Creating a BOM Markup
Applying a BOM Markup

Multi-Level BOM Edit Functional Summary

The following summarizes the multilevel BOM markup edit functionality:

  • You can toggle into edit mode with the as-stored or latest child components displayed in the BOM and edit the BOM at any displayed BOM level. For example, if the current BOM view is expanded six levels, then you can edit the BOM within six levels. These editing functions are captured as a number of single-level BOM edits with parents that can be at different levels in the BOM.
    Note: The expand toolbar commands are not functional on in-process markups. Once the markup has been saved and committed to the database, then the expand commands will work as expected.
  • Multiple BOM markups can be saved from the multilevel view. The system tracks N-number of single level BOM markups for N-number of affected parents.
  • For a part with the development release phase, you can save a markup or directly apply the markup.
  • For production parts, the markup must be saved in the context of the affected parent and an associated change process. The context of the change process is automatic if you open the part from a proposed change page of a change process. The context must be selected if you open a part from a search or other app page such as the Collections page. A page opens that lets you choose the change process for each production part for which a markup is created.
  • The Markups page can be used to manage development part markups, or to open or delete production part markups. Additional functionality for production part markups is available from a change process Proposed Changes page. Multiple markups for multiple parts can be opened from the Part or proposed changes page. Opening multiple markups will result in opening a BOM in the structure browser to whatever levels are required to display the set of BOM markups that have been requested. In this case, the affected parts must be contained in the same BOM for this to be valid.

Save Markup Command

You can changes one level at a time since there may be different change objects associated at different levels. When you save changes, each markup is created and connected to the parent part that is affected as well as any associated change object.

Note: To save changes to a markup, you must have check in access for the markup. To save markup for a part that another user created, you must be an Assignee for the change action.

The Save Markup command saves the current changes in the edit session under the same markup. The Save Markup command is available if:

  • A single BOM markup is opened. The BOM markup is already attached to a proposed change, so it is just saved.
  • A BOM is opened in Edit mode. A new markup is created and the markup is attached to the proposed change.

The Merge command deletes all the markups that were opened and saves the markup obtained by combining all the opened markups into a new markup.

  • If the session is initiated by opening a single BOM markup, then the Save Markup command updates the BOM markup to reflect the current session changes.
  • If the session is initiated by opening multiple BOM markups, then the Save Markup command is dimmed. Use the Merge command instead to save changes when multiple BOM markups are opened and edited.
  • If the session is initiated without opening existing BOM markups, the system creates the BOM markup and connects it to the affected part as well as the change object in context. The markup is auto-named but its name can later be changed.

Save Markup As Command

The Save Markup As command is similar to the Save Markup command but saves the markup as a separate file and lets you provide a name for the markup other than the auto-generated name.

Note: To save changes to a markup, you must have check in access for the markup. To save markup for a part that another user created, you must be an Assignee for the change action.

When using the Save Markup As command:

  • When one BOM markup is open, Save Markup As saves the changes made in the session into a new markup.
  • When multiple markups are opened, the Save Markup As command saves the new copy of the markup into a separate file and the original files opened are left untouched. The new file is a combination of all selected markups and the session-specific changes made to these markups.
  • If no markups are opened, the Save Markup As command behaves the same as the Save Markup command but allows you to name the markup when saving it.

Merge Command

The Merge command is enabled only when you select multiple markups from the Proposed Changes page. When you use the Merge command, existing markups are deleted.