Part History

[NXsupport]

Hi,

NX4.0.4.2 Teamcenter engineering 2005SR1...

While import assembly through NX Manager>>import assembly... I have run into this problem quite often.. For example, If iam trying to import XYZ.prt file which is a simple part file... I get a dialogue box where I have to assign a number to ABC.prt...this ABC is found in XYZ when I do a part history query... Looks like XYZ was ABC sometime back... If I have a automated script to do this import part... the script fails as it does not see this ABC named part any where...

Is this inherent problem with UG_CLONE utility from Siemen`s?

Looks like during cloning , the utility digs into the part history of the part... I dont seem to understand this action..

Please help..
Thanks

 

[hudson888]

You're running Teamcenter I take it and how do you export the assembly? I'm familiar with Tools>NX Manager>Import Assembly/Export Assembly, from within the NX session.

The rules governing what you can and can't do can be restrictive. There isn't much scope for importing any parts that don't originate from being exported. So you cannot "save as" in native and then import that part. But I know you can add or remove components from an assembly.

If you think you may be doing some of those things that you haven't explained in your post, then they may be contributing to your problem.

As for the UG_CLONE utility we don't use it so I can't really comment.

Best regards

Hudson

 

[NXsupport]

Hi Hudson

Looks like the UG_Clone utility from UGS( now Siemen`s) goes to the information >>part history>> and scans that ..( dont know why it does this) .. Then it will pop a dialogue where I have to assign TC number for that referenced part( which is not present on the drive)... Interesting thing to note however is that , If I query this TC number.. the search returns nothing...

John does this question make any sense to you?

Iam getting frustrated with this UG_CLONE utility...

thanks

 

[hudson888]

I think that it may read something in the file header. Not sure I just know that what occurs in Teamcenter is that the item master collects records in a database containing links to files that are stored as hash names, that is to say the name of the file stored in Native on the Hard Disk is unrecognisable. This aims to provide greater security. During importing and exporting the system generally requires one way or another to know that what item master to attach the file to. If in doing so it is expected to overwrite some previous data then it needs to perform a match between the files. That matching purpose does not appear to rely on the file naming criteria alone. Since Teamcentre retains some record of the usage and dependencies between files I can only suppose that it is trying to ensure that these will be validated without having to actually open everything in NX in order to check that it works.

The only other ways that I know of to import external data are generally very manual and tedious. They override the checking criteria I guess on the basis that you're specifically foregoing some of those linkages.

I have like you perhaps often wondered that Teamcenter won't work with Native data by applying the same filename based versioning rules for substitution that assemblies use in the Native NX environment. I can only assume that from a Teamcenter point of view this would be something akin to working out of sync with the PSE.

Sorry not to have been of more help. I expect that if the UG-Clone utility does not work as it is expected to then you would do well to report it to GTAC.

Perhaps as it seems to be working from the command line you should check that none of the directory structures or file names involved contain spaces in their names. This is always good from problems in command line utilities.

Cheers

Hudson