Vault Manufacturing 2010 update 2.
Some time ago the Item was created for the particular IAM.
Later that IAM was redesigned quite a bit. Some top level components were demoted to sub-assies.
Item Update command had no desired effect on BOM (no effect to BOM at all).
I thought if all components were be removed from BOM - Vault would guess that something is wrong and finally will update it :-).
After repeating "Remove row" command the Item BOM is empty now but again update have no effect.
I don't want remove and create Item (I did it in the past - yes it helped, but I don't want - it is definitly wrong way). I want update to be working.
What might be wrong? What can i do?
Thanks in advance.
Try removing the primary link to the assembly file from the item and reassigning item to the assembly file.
Too late for that particular Item - It stopped our work thus already removed. I'll try your recommendation when situation would repeat (I'm sure it would).
BTW, now we can't create that deleted Item because of Er1404...
Item BOM issues continue in Vault Pro 2012 upd1.
Items of some components occasioanlly "jump" to the assy-Item level while updating assy-Item and disappear from BOM Item as a result.
Tech support case is open but any informal help is welcome.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!