cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

BOM Import

Highlighted
Participant

BOM Import

I am working on a large assembly where i want to use a BOM from my lead assembly page on several following pages so my balloons can be driven by the lead page. Does anyone know a way in which this can be done? Im not using sheets so the BOM info would need to be imported but i dont want it to show on the pages where the balloons need to be driven.  Any help would be appreciated.

Tags (2)
13 REPLIES 13

Re: BOM Import

You can not natively drive balloons from one drawing to another separate drawing file and maintain parametric relationships.

You can fix the indexes on multiple repeat regions so the numbers are the same. If you don't want the repeat regions to show up then you can just layer them off. Unless you are manually creating balloons as individual symbols, balloons need to be driven by repeat regions (they can't be an import of some other repeat region).


Hope this is a helpful step in the right direction.

Re: BOM Import

As long as your only using one assembly and one simplified rep, you can show BOM balloons on any sheet of the drawing even though the BOM table (repeat region) is just on the first page.

Not too sure what you mean by "not using sheets" and "bom info would need to be imported".

Maybe you can clarify?


Steve Williams
Pro/E Version 15/16 (Circa 1995/1996)

Re: BOM Import

I think he has multiple separate drawing files (Not multiple sheets).

Re: BOM Import

I am using a single assembly in several drawings but not using sheets. What I mean by this is that we typically use separate drawings for each page of a book of drawings instead of using a book of sheets. We always have sheet 1 of 1 instead of an assembly where you may see sheet 1 of 15.

Re: BOM Import

Well, you can move your BOM table outside of your format so it won't show on the drawing but the BOM tables won't be connected other than by the assembly driving them.  You can use fix index to control balloon #'s or you could possibly use component parameters to drive balloon #'s instead if you don't want to use fix index but that's not an easy solution to implement.

Sorry I don't have a good solution.


Steve Williams
Pro/E Version 15/16 (Circa 1995/1996)

Re: BOM Import

We typically use fix index for components as is but i couldnt help but wonder if there was a better way of handling this so that there is a link between the original bom so when updates are handled theres less chance of error on other drawings.

I appreciate the info either way.

Re: BOM Import

Just out of curiousity, why are you doing the single sheet drawings instead of multi sheet drawings? I have a feeling I know why, I too deal with large assemblies....


Steve Williams
Pro/E Version 15/16 (Circa 1995/1996)

Re: BOM Import

We like to keep things independent so there is better traceability to individual items in the rare instance that we need to revert back to something previously done. We always revise when checking out so we have new instances each time something gets worked on.

Re: BOM Import

Ok - and yes there is, if you want to do so. As pointed out by Tom Uminn recently I can create an assembly-level parameter that is unique to each component, and display (under the Features selection) in the Model Tree Columns the values. Further, this value is a candidate for adding to BOM tables, and BOM tables can be set to use this parameter as the driver for BOM balloons.

This allows the BOM/Repeat Region to have the same basis no matter where the assembly is used at the cost of indicating the correct item number for each component. Since the alternative is an endless (seemingly) Fixing and changing Repeat Region rpt.index values, this seems like a fair trade.

The main thing that makes it possible is that only one component needs to be identified at the outset and the column of the Model tree showing that value, and then one can march down the Model Tree being prompted for Type and Value for that parameter at each component.