We create JT data on monopart level (i.c.w. Teamcenter), and not on assembly level because this isn't necessary in hardly any situation. When applying the deformable parts functionality in NX, this approach gives us troubles. JT isn't created of the deformed part, but only of the none deformed part. The question would also be on what level the JT data should be created. Is there a way, or multiple ways, to make this work?
At this point all JT data of deformable parts is incorrect. in our TC environment.
Solution
Deformable parts can be deformed within an assembly. The configuration is saved into the assembly.
within the window shown above is is possible to choose at which assembly level is possible to save the deformation
Using the same deformable part in many assemblies, each of them has inside itself the information of the deformation.
About the same happens in Teamcenter.
The jt of an undeformed part is a dataset attached to the item revision of the component itself.
Visualizing the single component, this is the jt that is shown.
Loading the assembly, in the "structure Manager" then a different jt is collected to show the deformable part.
There can be as many jts as many assembly you have.
These jts are not belonging to an item or item revision, but are belonging to the BOM Line and they are attached as Absolute Occurence Data.
They are not possible to be visualized into MyTeamcenter as an attachment to the item revision, not even inside a BOM.
the item, item revision or BOM of the assembly do not contain contain jt
The way to find them is to make a search for Datasets having the same name as the assembly they refer to.
The management of these jt datasets is completely automatic and it is performed by teamcenter.
By selecting each one of them it is possible to see what is the deformed shape in the "jt Preview" or the "viewer" windows
Hardware/Software Configuration
Platform: all
OS: n/a
OS Version: n/a
Product: NX
Application: NXMANAGER
Function: TC_PORTAL
Ref: 002-8015003