If I were to load a bom/assy using tcexcel_import to create the items and then loaded the assembly using add to teamcenter, what would happen if the 2 didn't quite match the same assembly/subassembly structure?
Would the SE assy structure override the BOM structure, vice versa or just bring up an error?
What version of SE and TC are you using?
What is your use case that has you want to create the items first and not just use Add To Teamcenter (AtT) to create the items & boms?
Solid Edge ST10 and TcRS 11.2
The BOM has more in it than the solid edge assy, so thought it better to bring that in first? Do you think it would work better the other way round? If we bring in the SE assy first, what is the implication of using the tcexcel_import if the parts/items already exist?
Solid Edge needs its own BOM in Teamcenter. This BOM should not be modified by users in Teamcenter. This will cause issues with the integration. Whatever you see in your SE assembly structure should be what you will see in the BOM in Teamcenter. The SE BOM is usually never a match for your eBOM/mBOM. You may either need to do a CAD-PART alignment where you have 2 Item types with the same Item ID (using MFK) and one holds the SE BOM and datasets and the other holds the eBOM/mBOM. Or have 2 BOM's under a single item (not my preference).
Add to Teamcenter is the tool that is supported to create Items/BOM's/Relations for SE integration to work properly. It creates the correct information in the BOM and the correct relationships between all the Items. If you preload TC with the Items/BOM's then AtT will be slower as it needs to validate that existing data before it can load. It may work but it could also fail depending on what it finds in TC. It may not be able to resolve itself to load the mismatch. Are you using the SE Data Migration tools to prep the files before importing them into TC?
I guess to better help, what are you trying to do ultimately? Are you trying to do a bulk migration? Or is this a on-demand load of vendor/supplier items? Are you needing to do the tcexcel_import after the SE load to add the additional items to the BOM? Anytime the items/boms exist and you try to do any import function, it will have an impact to that tool. I think if you have the need for 2 different BOM structures, you need to work through how you want that data model, because sharing a single BOM will not work for SE.
Mercury PLM Services
Thanks for the reply Jamie.
This is a first load. Ultimately, we want the BOM from the assy and then load the additional items from the parts and vendors list (which contains a list of CAD items and non-CAD items). Should this not be in the same BOM?
I really think from what you are saying, you will need to use 2 BOM's. Process your SE assemblies with the Data Prep tools, import using AtT first. Use the supplied tools to create and mantain everything needed for the SE assemblies. After they are existing, decide how you will create that 2nd BOM in your data model because you do not want to modify the SE BOM in Teamcenter . The preference SEEC_Default_View_Type should be set to specifiy which BOM will be used for SEEC to load to cache for the assembly.
Mercury PLM Services
OK. So assume we use 2 BOM's. If changes are made to the SE BOM, how do you ensure the Parts and Vendors BOM stays in sync with what has happened in the SE BOM?
What you're talking about is Part Design Alignment. One Item has the Part BOM (CAD and non-CAD) while a separate Item has the Design BOM (CAD).
Here's some reading to get you going:
Note: You should also have Commercial Parts (Vendor Management).
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3