Transfer multi level Teamcenter BOM based on data from Excel sheet using the Tc BOM Structure Synchronize Snap

This example pipeline demonstrates how to transfer a multi-level BOM from an Excel sheet into Teamcenter.

Whole pipeline starting with File Reader and ending with File Writer Snap.

It is possible to use the pipeline build in former chapter Create Teamcenter Parts and BOM based on data from Excel sheet using the Tc BOM Structure Create Snap to transer multi level BOMs. Therefore it is a prerequisite to build this pipeline first.

Pipeline version to transfer BOM level by level

Snaps will create a BOM for each level and Tc BOM Structure Synchronize Snap will process each level. Some selected points of pipeline validation show the difference. First Excel file containing four BOM line rows for head “P1” is extended with two rows for child part “P2” as head.

Excel file content with four rows describing BOM Lines for Head 'P1' and two rows for head 'P2'.

The output of the GroupByField Snap contains now two objects: one for head “P1” and one for head “P2”.

JSON document of output of Group By Fields Snap.

So next Snap creates two BOM structures objects as input for Tc BOM Structure Synchronize Snap representing the two BOM structures.

JSON document containgn two BOM structure objects.

The Tc BOM Snap shows two results.

JSON document for two result objects of BOM synchronization.

Resulting excel file contains now all information.

Excel file including column for occurrenceUID.

Now it can happen that one BOM fails and another succeeds. Since the first row send to Excel Formatter determines column head values error and success branch output has to be brought together. This is done with an additional Mapper Snap.

Pipeline with added Mapper Snap infront of Excel Formatter Snap. Settings of new Mapper Snap where existence of fields is checked and conditionally added with empty value.

Excel file now contains all columns.

Excel file content with succeed result and error result for different BOMs.

Pipeline version to transfer whole BOM structure at once

To empower the pipeline to transfer the whole BOM structure with one call to Teamcenter the pipeline has to be extended with a Script Snap.

Former pipeline extended with script snap and mapper snap which are framed.

Example input excel file will be filled with newly created Part Revision UIDs to have a fresh start.

Processing of first snaps is described in Create Teamcenter Parts and BOM based on data from Excel sheet using the Tc BOM Structure Create Snap. The output document of the already known Mapper Snap “Map BOM structure” is now the input for the new Script Snap.

The script gets multiple one level BOM structures and has the task to move children BOM structures into parent BOM.

Setting of Script Snap. Language is set to Javascript.

The script result is written into JSON object “result”. Children “P2” in “children” list object has now own list object “children” containing two objects.

Output document content of Script Snap. JSON object 'result' contains one BOM structure with two levels.

The following Mapper Snap “Map result content to top“ moves the content of “result” to the top of the document to be the input for the Tc BOM Structure Synchronize Snap.

Settings of Mapper Snap. Mapping table contains one row to map result object to top level of JSON document.

The Tc BOM Synch Snap processes the whole JSON document and has some attributes configured to be in output document.

Settings of Tc BOM Structure Synchronize Snap.

Output document of Tc BOM Structure Synchronize Snap shows BOM Synchronization result including the information about added child elements.

JSON document for result object of BOM synchronization.