Hi Aman
>Where is the location in CWC UI where we can see the bill of material.
There's no screen just for BOMs. But in CWC, if you create a Work Instruction that has a Part Validation step, then inside the Route you will see the Parts Validation tab and in the right panel there is an Add Items button, it will open a popup containing the list of BOMs that the Route's product is associated with.
>the service ImportBOM_END on the thing PTC.FSU.CORE.Product.EndPoint_TG in CWC shows success message. But I am unable to see the BOM. Also, in the route manager, I get the message that no Bill of material is assigned for the product.
So when the import service executes, it actually just puts the data in a list that the next process can read. Success means it's in the list to process. This list is the ProcessRunning table in SQL. Records in this list should be processed within moments, but sometimes people don't have the process Timer activated so nothing gets done. Please go in Composer, on Timer PTC.FSU.CORE.Process.ProcessQueue_TM, make sure it's enabled, but above all : its 4 subscriptions should be active. I think the first one (TriggerUpdateQueueConfiguration_PRC) is the one responsible for processing the BOM import list. Once this is done you can try the Route configuration again, see if you can access the BOM.
Note that on a BOM, there's a main product which is the "result". This is the one that the Route should be producing. And inside the BOM you can specify 1 or more Items, those are the inputs. So for example if you make cars, then the Route's product could be a Car, the BOM's main product should be that same Car, and the Items will be tires (4), engine, doors, etc.
If despite this you still get the error in the Route configuration saying that there's no BOM for your product, then I encourage you to open a support ticket and we can look into your data. One big suspect is the next step of the import (the one that transforms ProcessRunning into BillOfMaterial & BillOfMaterialItem) may have failed, so we would need to look at the error messages & your specific data.
