If you work with BOMs in Teamcenter you have probably seen the terms Precise and Imprecise BOM structure. Even if you only use one type of BOM you need to understand the difference between them.
Previously when I discussed creating a custom autotranslate function to assist in NX data migrations, I recommended that you should unit test the function with an external program and I mentioned that I wrote my test harnesses in Python. Today I thought I’d show some examples of what that looks like.
If you’re going to migrate very much NX CAD data into Teamcenter, even if you’re going to do it
manually by using NX’x File → Import Assembly into Teamcenter… there’s one customization you should very seriously consider: a custom Autotranslate function.
A custom Autotranslate will give you the the ability to automate how native file names are translated into Teamcenter IDs, alleviating the need to have users manually enter them in. It can be used whether you’re importing data using NX’s dialogs or their command line utility, or if you’re developing your own program to handle the migration for you.