Restructuring and editing the product structure

You can restructure a representation, including a BOM view, occurrence group, structure context, or composition. You must revise a frozen product structure before restructuring. Restructuring edits the product structure in downstream views (for example, manufacturing) while preserving the derived occurrence structure and data related to specific occurrences of parts and assemblies. Restructuring is disabled for product structures that contain CAD designs because it can make the CAD data invalid.

During restructuring operations, Teamcenter maintains the integrity of incremental changes, classic or modular variants, and structure relationships. Teamcenter displays warnings when it encounters absolute occurrences attributes and data.

If you have edits pending to a product structure, you must save the edits before you open the structure in another application.

In addition to restructuring, you can edit individual properties on any line, subject to the following limitations:

• Restructuring is not permitted on lines that have pending edits.

• Property edits are associated with a relative occurrence and are marked as pending until they are saved to the database.

• Property edits are highlighted only if you use the column editor. If you use other methods of changing properties (for example, the Properties dialog box), these edits are not visually highlighted in the properties table. However, Teamcenter still retains the details of such edits until you save or revert them.

• Use the PS_structure_change_condition preference to specify actions as structure edits. For example, by default, changing a reference designator is not considered as a structure edit, but you can add this action to the preference. NX requires reference designator changes to be considered as structure edits.

• If any note in the list of notes is edited, the All Notes field shows a … icon with a red strike-through. It does not show the exact original value.

• Edits to the absolute or relative transformation matrix are not highlighted.

• You cannot edit the first property column (BOM Line).

• If you cut more than one BOM line to the clipboard and then modify the BOM lines on the clipboard, this action changes the ownership of the remaining BOM lines. For example, if you cut two BOM lines and then remove one of these lines from the clipboard, the status of the remaining line changes from pending cut to pending copy. If you want to modify the BOM lines that are the subject of a cut action, repeat the cut action on the required BOM lines, rather than modifying the contents of the clipboard.

• If you remove a line that contains one or more unsaved changes to its substructure, the system does not automatically save those changes.

• By default, if you cut or copy a line and then paste it to a new location, incremental change elements (ICEs) are not copied. This may necessitate significant manual recreation of data if you are cutting or copying many lines together. To automatically copy ICEs, the administrator must set two Business Modeler IDE constants:

Fnd0EnableIceCarryOver business object constant When moving, copying, or assigning a line from one location to another, this constant determines if the ICEs are carried forward. You must set this constant to true on both the source location’s parent and the target location’s parent.

Fnd0AttrICEsToExclude property constant Defines the occurrence attributes that Teamcenter does not copy to the target location for occurrence attribute changes.

These settings apply to in-context changes made to structure lines, their attachments, and their occurrence attributes.

Note

Restructuring primitive actions include:

• Removing a level (removing a line and keeping child lines)

• Inserting a level (including pasting a line as a parent of selected lines)

• Moving a line to a new location (for example, cut and paste actions)

• Splitting an occurrence

• Replacing data in context

Only the last two actions make copies of the absolute occurrence data; the other actions share the existing absolute occurrence data.

In certain cases, restructuring may cause valid reports of broken links, as shown in the following examples:

Example 1:

Copy

A
+-----------B
            +-----------C (APN1 in context of A)
                        +-------------D

If you remove level C, the structure becomes:

Copy

A
+-----------B
            +-----------D

The link to C is lost. This is correctly reported as a broken link.

Example 2:

Copy

A
+---------E
+---------B
          +---------C
                    +-----------D(APN1 in context of B)

If you move D to E, it is outside of the context of B and APN1 is lost. This is correctly reported as a broken link.

Example 3:

Copy

A
+-----------B
|           +-----------C
|                       +-------------D(APN2 in context of A)
+-----------B
|           +-----------C 
|                       +-------------D(APN1 in context of A)
+-----------D
+-----------D

If you move C to D, the system cannot determine which D to move the APN to without user interaction. It skips the APN and logs an error message.

Example 4:

Copy

A
+-----------B
            +-----------C 
                        +-------------D(APN1 in context of B)

If you remove level B, it becomes:

Copy

A
+-----------C
            +-----------D

The link to D is lost. This is correctly reported as a broken link.