I'm trying to use auto-translate to import fairly large assemblies into teamcenter. But the problem is, the default revision teamcenter imports as is A. however our teamcenter only allows revision AA to be used. Is there a way to change this? I've tried setting the DB_part_rev to AA in NX before importing the assembly into teamcenter, but this doesn't seem to fix the problem.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Setting default revision when importing an assembly into teamcenter.
- Thread starter Isobar
- Start date
- Thread starter
- #2
You may have a better answer if you ask this question in the PLM world and or GTAC Forums. There are some very good teamcenter experts that may be able to help you out. There is also a teamcenter forum on ENGtips but it does not get much traffic.
- Thread starter
- #4
Normally Teamcenter should be setup with "numbering rules" (and optionally a "number generator"). If this is done, you should get the correct rev when importing as long as you get the correct "part type" in the import dialog ( Numbering tab)
In "my site" the part type defaults to an incorrect type which has to be changed on every import. But then the rev indicator becomes correct.
regards,
Tomas
In "my site" the part type defaults to an incorrect type which has to be changed on every import. But then the rev indicator becomes correct.
regards,
Tomas
- Thread starter
- #6
I know when I bring it in, I've made sure the default type was set to CAD. When I do a dry run of any import assembly, this is the code I get
&LOG Cloning_Action: DEFAULT_DISP Naming_Technique: DEFAULT_NAMING Clone_Name: @DB/importtest1/A
the problem I believe I'm running into, is I need it to be
&LOG Cloning_Action: DEFAULT_DISP Naming_Technique: DEFAULT_NAMING Clone_Name: @DB/importtest1/AA
as my site only accepts the revision AA. From there, we use AA.001, AA.002 etc.
This error only occurs using the Auto Translate. If I do auto generate, it will bring it in with no issues, however when you have hundreds of files already named, it is a huge time sink to have to go through and rename and renumber them. Basically, I'm looking for any way for me to be able to use Auto-Translate to keep my part names and numbers, but have teamcenter set the revision to AA instead of A. I'm using NX 7.5 and TC8 if that makes a difference.
&LOG Cloning_Action: DEFAULT_DISP Naming_Technique: DEFAULT_NAMING Clone_Name: @DB/importtest1/A
the problem I believe I'm running into, is I need it to be
&LOG Cloning_Action: DEFAULT_DISP Naming_Technique: DEFAULT_NAMING Clone_Name: @DB/importtest1/AA
as my site only accepts the revision AA. From there, we use AA.001, AA.002 etc.
This error only occurs using the Auto Translate. If I do auto generate, it will bring it in with no issues, however when you have hundreds of files already named, it is a huge time sink to have to go through and rename and renumber them. Basically, I'm looking for any way for me to be able to use Auto-Translate to keep my part names and numbers, but have teamcenter set the revision to AA instead of A. I'm using NX 7.5 and TC8 if that makes a difference.
Hi,
there is also an option to use ug_import routine that uses correctly named
files like codeno_rev and feed that to teamcenter. you can run it in teamcenter 2tier from command prompt. could be a little hardcore for just couple of parts. Handy when lots need to be imported or they are already assembled in nx.
For this you also need tc dba access. if I remember correctly
That code can be found from gtac download area somewhere. But not 100% sure about this.
This is more of a data migration utility and does not respect any naming or revision rules in Teamcenter. therefore the dba needed plus a warning not to mess up existing data without testing properly in a non production system first.
NH
there is also an option to use ug_import routine that uses correctly named
files like codeno_rev and feed that to teamcenter. you can run it in teamcenter 2tier from command prompt. could be a little hardcore for just couple of parts. Handy when lots need to be imported or they are already assembled in nx.
For this you also need tc dba access. if I remember correctly
That code can be found from gtac download area somewhere. But not 100% sure about this.
This is more of a data migration utility and does not respect any naming or revision rules in Teamcenter. therefore the dba needed plus a warning not to mess up existing data without testing properly in a non production system first.
NH
- Thread starter
- #8
I would love to get into the GTAC and take a look around, but I don't have access and my IT don't exactly like doing that kind of work. I have a lot of assemblies of 300+ parts to translate from native into Teamcenter, so it's definitely not just a handful of parts.
- Thread starter
- #10
If all the files to be imported "happens" to have a consistent naming convention, and also happens to be revision /A
you can use the naming rule and replace /A with /AA
In some cases it's easier to manipulate the native filenames before the import into TC...
When importing, NX "thinks" that if there is a "_" ( Underscore) in the filename, then whatever comes after is the revision,
i.e if one has a file named pin_A it will be translated into pin/A but if the filename is "square_pin_A" NX will translate it into square/pin_A.
Then the Name rule replace "_" with "_" will fix the problem.
After i have run the dry run, i change the "Report to information window option" to "Full" and check the resulting names, ( Better overview than what the dry run produces) if i then spot something of which the naming rule didn't handle, i go back to the naming tab and in the Exceptions dialog change to "User Name" ( I don't have a NX/TC session so the correct name of the button might be wrong but i think you understand what i mean.)
Regards,
Tomas
you can use the naming rule and replace /A with /AA
In some cases it's easier to manipulate the native filenames before the import into TC...
When importing, NX "thinks" that if there is a "_" ( Underscore) in the filename, then whatever comes after is the revision,
i.e if one has a file named pin_A it will be translated into pin/A but if the filename is "square_pin_A" NX will translate it into square/pin_A.
Then the Name rule replace "_" with "_" will fix the problem.
After i have run the dry run, i change the "Report to information window option" to "Full" and check the resulting names, ( Better overview than what the dry run produces) if i then spot something of which the naming rule didn't handle, i go back to the naming tab and in the Exceptions dialog change to "User Name" ( I don't have a NX/TC session so the correct name of the button might be wrong but i think you understand what i mean.)
Regards,
Tomas
- Thread starter
- #12
Well that's unfortunate, as all are part names come from I-deas where you weren't allowed to use spaces, so they are named with underscores to replace spaces. So all the part names would baasically are Item_Name_Blah_blah.prt
Is there an option inside of native NX to select a bunch of parts and assign a revision?
Is there an option inside of native NX to select a bunch of parts and assign a revision?
- Thread starter
- #15
Are you telling me to try and auto-replace an underscore with an underscore? Or am I misunderstanding something there.
I have been messing around with a small test assembly, in which I have 3 components, one named importtest1, one named importtest2_AA and one named import_test_AA.
I am able to import the importtest2_AA by itself, but the importtest1 tries to import it as revision A, and the import_test_AA does it as revision test_AA. So you are correct on that, the problem is now I need a way to do both replacing all of the underscores with a space, and add _AA at the end so it reads it as revision AA.
I can't believe something as simple as mass editing the import revision is this difficult. Seems like my company can't be the only one using a revision that isn't the Teamcenter default "A".
I have been messing around with a small test assembly, in which I have 3 components, one named importtest1, one named importtest2_AA and one named import_test_AA.
I am able to import the importtest2_AA by itself, but the importtest1 tries to import it as revision A, and the import_test_AA does it as revision test_AA. So you are correct on that, the problem is now I need a way to do both replacing all of the underscores with a space, and add _AA at the end so it reads it as revision AA.
I can't believe something as simple as mass editing the import revision is this difficult. Seems like my company can't be the only one using a revision that isn't the Teamcenter default "A".
If you do a dryrun you should get a report window pop up with loads of lines starting with &LOG. This lists each part to be imported, look for the Clone_Name which will be in the format @DB/part_number/rev. In a text editor you can replace all the /A" with /AA" and save the file as import.clone.
Run the import again as usual but on the Log Files tab, select Load and Apply Existing Log File. Select your modified import.clone file and the files will be imported with the correct revision.
Run the import again as usual but on the Log Files tab, select Load and Apply Existing Log File. Select your modified import.clone file and the files will be imported with the correct revision.
- Thread starter
- #17
- Status
Similar threads
- Locked
- Question
