Teamcenter SOA Client : Use case for BOM creation

最新推荐文章于 2025-07-28 13:34:08 发布

转载最新推荐文章于 2025-07-28 13:34:08 发布 · 562 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：https://Teamcenter.Open.Gate

文章标签：

#java

Teamcenter SOA Service 专栏收录该内容

32 篇文章

订阅专栏

本文探讨了在Teamcenter环境下，尝试使用StructureManagementService API在多个已存在的部件修订版下创建BOM结构时遇到的问题。详细介绍了如何避免重复创建BOM视图，以及通过使用'add' API或在创建BOM窗口时添加现有BOM视图对象的解决方案。

Scenario : Create a BoM structure under multiple part revisions already existing in Teamcenter.(eg: Revision A and B already exist in Teamcneter and now creating bom under Revision A and then under revision B and so on )

Details :
We were trying to use the com.teamcenter.services.strong.bom.StructureManagementService API named addOrUpdateChildrenToParentLine.
This API tries to create the BOMView object per revision and hence worked for the first revision however failed for the next revision since the BOMView already existed.

This scenario was working fine in Teamcenter and we figured out that Teamcenter was calling a different API to create the BOM structure.
In the communication monitor we found the api named 'add' under class com.teamcenter.services.strong.structuremanagement.StructureService.

Other Way to handle scenario is to add the existing item bomview object to the CreateBOMWindowsInfo object when you create the BOMWindow. Then it will not try to create another BOMView at the item level but just use the one provided.