Unsynchronized product structure

There are three different situations in which the product structure can become unsynchronized. A description of each situation is listed below, along with
guidance on resynchronizing. These situations can arise if you have been working with the structure update customer default turned off for load or save,
as well as when first using the new system. In either case, you can use the procedures described below to correctly synchronize your product structures.
Structure Manager BOMView Revision and NX assembly present.
This is the case where the structure information in the Structure Manager and NX do not match. Perform the following:
1. Ensure you have write access to the assembly.
2. In NX, choose Preferences→Teamcenter Integration for NX. On the Assembly page, from the Structure Update On Load list, select None.
3. Choose File tab→Preferences→Assembly Load Options. In the Scope group, from the Load list, select Structure Only.
4. Open the unsynchronized assembly.
5. Choose File tab→Save→Force Save All.
6. Exit NX.
7. Repeat for all corrupted assemblies.

If you have an assembly where the subassemblies are also corrupted and you have write access to all of those subassemblies, then you can set the
Load option to All Components in step 3 (above). If you do not have write access to any assemblies or parts in the loaded assembly, they are not
saved and the structure is not updated for those subassemblies. It is not necessary to have write access to the leaf component parts.
NX assembly, no Structure Manager BOMView Revision.
This is the common case when an earlier version of Teamcenter Integration (prior to Teamcenter V3) has been used. In this case, when the NX
assembly is loaded, no update of the NX structures takes place.
To recreate the BOMView Revision, load the assembly with structure update on load disabled, and the structure update on save enabled (go to
Product Structure Synchronization Defaults for additional information). Then save the affected assembly in NX. The save action causes a new
BOMView Revision to be created.
Structure Manager BOMView Revision, no NX assembly.
This is the common case when the old Structure Manager has been used, but NX assemblies have not been used. In this case, an NX part is
created and treated as an empty assembly, which is then updated from the Teamcenter structure. If there are transforms on the Teamcenter
components, these are used; the components are put straight into the assembly, rather than onto the pending list.
In this situation you must first confirm if there was an NX assembly matching the BOMView Revision that has been deleted.
To do this, open the BOMView Revision in Structure Manager. Change your column display preference to display the UG ENTITY HANDLE note
type. If occurrences have a value for this note type, then an NX assembly has been lost.
Ideally, you should recover the lost UGMASTER dataset from backups. If this is not possible, then you must delete the UG ENTITY HANDLE notes
and re-save the BOMView Revision before proceeding with the next step.
After removing any UG ENTITY HANDLE notes you can re-populate the NX assembly from the BOMView Revision by opening the assembly with
both structure update defaults enabled. Position any components that have been marked as Pending, then save the assembly. All mating conditions
will be lost, since these are not stored in Structure Manager.

© 2017 Siemens Product Lifecycle Management Software Inc.

1 од 1