Skip to main content
R
RWL1-Visitor
1-Visitor
January 9, 2018
Solved

Alpha Numeric BOM Table - 1st Row empty and 1st part starts in Row 2

  • January 9, 2018
  • 1 reply
  • 5874 views

I am using CREO 2, and am having an issue with a repeat region BOM Table in an older drawing.

The drawing used to contain a BOM Table that controlled the item numbers by through "BOM Index" column in the model.

We now have a MapKey that creates an Automatic Alpha Numeric BOM Table, which has worked perfectly for hundreds of drawings, both old and new.

I have replaced the old table with one of these new MapKey created, alpha numeric table, but it is manifesting a strange phenomenon.

The issue is that this new table comes in with Row (Item) 1 empty except for the quantity which is "1", indicating that it sees "1 each" of something but can't display it.

The actual first part now shows up in Row (Item) 2, and all other required parts are displayed in the proper quantities, such that this BOM is one item longer than the old one.

This MapKey has always works well, until this drawing, and according to the other engineer and designer, here, they have never witnessed this behavior before.

I have gone through the assembly tree, and the workspace to see if there is a part without a name or something, but have found nothing out of the ordinary.

Any ideas what might be causing this?

Thanks,

Best answer by RWL

We figured it out.

 

I turns out that the relation "pnreport=extract(asm_mbr_name,1,6)" absolutely requires a minimum of 6 characters, and there is a "TOOL" part in this assembly that has only a 5 digit number/name, and hence could not show the Name, and because of that, it could also not show the Short Description.

 

My manager came in and set the Dwg_Vis column to show the base Common Name and boom, there it was, "T1046", and I new instantly what the problem was.

 

All of our component numbers have a minimun of 6 characters, i.e. "TR0146", and the tool is only there to show the assemblers how to use it, and is not to show up in the BOM at all.

 

I have now filtered out this part and all is well with the world again.

 

So, how do I mark this as SOLVED?

1 reply

StephenW
StephenW23-Emerald III
23-Emerald III
January 9, 2018

Does your mapkey "convert" and existing table or does it bring in a new table? If converting an existing table, maybe there are relations or something causing the issue.

R
RWL1-VisitorAuthor
1-Visitor
January 9, 2018

The old table is deleted, which takes all of the balloons away as well.

The mapkey then makes a brand new table, and we generate all new component balloons.

D
dschenken1-Visitor
1-Visitor
January 9, 2018

It seems like the columns may be displaying a parameter name and one of the parts is missing a value.  Add a column that shows the filename. Other than that there are too many combinations of repeat region relations and repeat region filters to be sure.

Terms & ConditionsAccessibility statement