Skip to main content
Dale_Rosema
23-Emerald III
23-Emerald III
May 21, 2012
Solved

Regenerate for correct BOM, even after save, close and reopen.

  • May 21, 2012
  • 2 replies
  • 16814 views

I have BOM's that are automatically generated within drawings. There are times when I'll open a drawing and one of the rows are blank. When I regenerate, the proper data fills in the lines, but why is this necessary when opening a save drawing?

Thanks,

Dale


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by Dale_Rosema

While talking with a rep, after getting some new licenses installed, I was showing him this problem.

I noticed that the UM (unit of measure) had propagated, but not the description nor the PN (part number) parameters. (See WW_BOM_7)

I also noticed that UM was the only parameter filed in on the generic part even though the parameters had been filled in on the instances needed.

I quickly tested that discovery by adding values for the parameters of the generic. (See WW_BOM_8)

I saved the generic, the instance and regenerated the assembly and save it and then even closed out of Pro-E.

When I open the assembly, the values for the BOM table were in place and intact. (See WW_BOM_9).

The explanation that I received is that the null values in the generic are triggering the part to not regenerate the parameters of the instance into the BOM table. Once these values were no longer a null value, they will automatically propagate the table.

I forgot to add:

WOOOOO HOOOO!

2 replies

13-Aquamarine
May 22, 2012

Hi Dale...

I'd check that component. Go into the component that's appearing BLANK. Make sure there are no problems with it. It seems like all the other components are reporting correctly but that ONE is not- until a regeneration occurs. The regenerate command is probably updating the component... not necessarily the drawing.

What I'm saying is... I'm not sure the culprit is the drawing... maybe it's the component itself. Check there and let us know what you find.

Thanks!

-Brian

Dale_Rosema
23-Emerald III
23-Emerald III
May 23, 2012

Brian,

I opened up a part today and replaced one component, 1120 with 1120CTN. It. #1 which I have used before, dissappeared on the BOM (as far as description and part #) when I came back into the drawing.bom2.jpg

After regenerating, it shows back up as It. #2 - foam pad.

bom3.jpg

Thanks,

Dale

13-Aquamarine
May 23, 2012

Hi Dale...

Take a look inside that 9770.prt file. THAT is the object which disappeared. The shifting of the item numbers occurs because Creo is sorting on the part number string. When 9770 isn't reporting, (as in your top image), it goes at the bottom because "nothing" comes first in the list. Later once 9770 DOES report, it belongs after 9711 and 9687 in the sorting order.

So I wouldn't worry about the reordering. I would still take a look inside the part that disappears, though. What parameters are there. What relations are in this part (Tools->Relation)? Are there any relations set for your BOM table that could be complication the matter (Repeat Region->Relations)?

And does this BOM update after you Update the sheet... or after your Regenerate the model. That's a big clue.

Thanks!

-Brian

Patriot_1776
22-Sapphire II
June 15, 2012

Yeah, what Brian said!

"Wild West Mode".....AWESOME!

Dale_Rosema
23-Emerald III
23-Emerald III
July 16, 2012

I just wanted to thank all that replied to the various threads that I had on this issue. I posted the correct answer in each for those that follow.

Brian - I unmarked yours as correct, but was very thankful for all the help that you were able to give in helping me learn about family tables and their instances. - THANKS!

Dale Rosema

13-Aquamarine
July 16, 2012

No problem Dale...

I'm really glad you finally got this resolved. This was one of those things that would've been easier to diagnose with an actual model to work with. Working online is an imperfect medium. What counts is- the problem is solved and if anyone ever expereinces it again, the solution has been well documented!

Take care...

-Brian