Editing Structure
- 1Teamcenter Validation to Edit Structure Lines
- 2Edits to Structure
- 2.1Adding Components
- 2.2Restructuring Structure
- 2.3Adding Parts to NX
- 2.4Editing Quantity-Unit of Measures
- 2.5Editing BOM View Revision-Save As
- 3Saving & Refreshing the edits
- 3.1Saving
- 3.2Refreshing
- 4Tracking Edits
- 4.1Highlighting Edits to Structure
- 4.2Markup to Structure
-
Tracking Edits
-
Highlighting Edits to Structure
-
This feature of pending edits (PSE_Display_Pending_Edits preference is set to true) should be used when user want to track changes by editing BOM directly. With no intention to track, highlights to edits everywhere can get difficult to interpret .This feature is incompatible with BOM Markup feature and both cannot be used simultaneously .Highlighting edits cannot be used with incremental changes as well .Structures with pending edits cannot be compared with BOM Compare.
Pending edits are indicated as follows:
| Additions | Green Italic font |
| Removal | Red strikethrough line |
| Property Edits | Red strikethrough line on original values |
-
-
Markup to Structure
-
With Fnd0BOMMarkupAllowed global constant set to true in the Business Modeler IDE, Markup can be turned on in Structure Manager .It is not available in any other product structure application .Markup is used to propose changes and is saved in workspace object and send for review before applying the changes to assembly .Markup is related to BOM View Revision or any of its child lines.
More proposed changes can be added to existing markup object .There can be several markup changes to a markup object with one of the changes being active.
- Type of Proposed changes:
- Addition/Removal of Occurrence
- Addition/Removal of Substitute for line
- Replacement of a line
- Changes to value of Occurrence properties including notes ,quantity and other properties listed in Fnd0BOMMarkupSupportedProperties global constant in the Business Modeler IDE
- Display of Markup actions can be controlled by preferences.
- Not supported list for Markup
| Editing action menus | NOT All supported |
| Tracking Pending edits | Markup mode not available |
| Absolute Occurrence markup change | NOT Supported |
- Creation to deletion of Markups in Markup mode
- Workflows to manage review and approval of active markup object
|
When to use this workflow |
Workflow |
|
|
1 |
Markup Object to BVR=1 & Markup Object = Active |
Workflow routes this markup object for review. Item revision or BVR is sent to this workflow.
|
|
2 |
Markup Object to BVR>1 & 1 Markup Object = Active & Active Markup object is added as target |
Do not add the EPM-attach-related-objects handler to the Start task because the active markup object is copied and pasted as target of the workflow.
|
|
3 |
Markup Object to BVR>1 & 1 Markup Object = Active & Revise to carry forward active markup object |
Same as 1.On revise only active markup is carried forward. |
|
4 |
Markup Object to BVR>1 & 1 Markup Object = Active & Item Revision or BVR is added as target to workflow |
Workflow filters active markup object for review. Item Revision or BVR is added as target to workflow
In the sub-process task:
|
|
4.1 |
BOMMarkup_SplitTargets:
Multiple target query:
In the multiple target task:
|
|
|
4.2 |
BOMMarkup_AddStatus
|
How do you change/correct the ‘Number of occurrences’ of an existing item?
Do you have to delete it from the BOM and then add it back in, in order to correct the number of occurrences and ultimately the quantity of the item?
If the component has no unit of measure,for eg. spokes and you want to create 20 spokes, then aggregate occurrence(it is single occurrence) can be created that represents 20 spokes. Aggregate Occurrence for 20 spokes can be created in Add dialog box,by defining quantity per occurrence as 20.
For existing component, quantity attribute can be modified to change number of occurrences for this component.
But, if component has unit of measures, for e.g. 1.5 kg, then aggregate occurrence cannot be created, hence conventional method of add/pack/remove has to be adopted.