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.
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.
Maybe,You can add bomline after remove all.
ReplyDeleteSorry buddy ,I think you missed to understand the problem statement .Revisions didn't had any bomline.
Delete