IF THEN statements SW2005 BOM Table

[automationbabe]

I'm not able to get the IF THEN statement to work properly in 2005 BOM. Our UOM is driven by another system that assigns a numeric value as shown.

IF UOM=1 THEN "ASSY"
IF UOM=2 THEN "EA"
IF UOM=3 THEN "IN"
IF UOM=4 THEN "mm"

We set up a formula for the Excel based BOM that works great (=IF(G2=1,"ASSY",IF(G2=2,"EA",IF(G2=10,"IN")))) but I can't get a similar format for the table. Any ideas??? Is this even possible to do?

Thanks a bunch!

 

[SBaugh]

I don't think this is possible to do in the SW BOM only, the Excel based BOM.

Regards,

Scott Baugh, CSWP

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376

 

[automationbabe]

Thanks for response Scott. Appreciate it.

Do you know the extent of the IF THEN statements in SW2005 BOM table?

Do you know why UOM are not part of the BOM table?

Wonder if there's a workaround out there somewhere...

 

[Standing]

automationbabe,
I could not get the SolidWorks BOM to put in formulas either. So I put in an enhancement request with SolidWorks. We are still using the excel BOM. Every time we change quantities we have to double click the BOM and exit out of the BOM. On large assemblies that takes a long time.

=IF(H4="EA",B4,IF(H4="FT",TEXT(I4/12,".0 FT"),IF(H4="NA",TEXT(,"0"),IF(H4="QTY",TEXT(J4,"0"),IF(H4="%",TEXT(J4,".00"),B4)))))

Bradley

 

[automationbabe]

Darn...and I was all excited about finally being able to use the SW BOM.

We have to do the same thing as you, Bradley. It's a pain and usually leads to crashes for me.

 

[Standing]

automationbabe,
The SolidWorks BOM table will do the math now in SolidWorks 2005 Sp3.1. I added two properties called Total_Length and UoM, to my part configuration.

The SolidWorks BOM equation is:

IF(`UoM`="FT";`Total_Length`" FT"{2};'QTY')

Now the problem I have is creating a BOM for 300 part assembly. I would have items 1 thru 30 on the right then items 31 thru 60 in the center and items 61 up on the left of my D size sheet. Getting this to happen using split is not easy for our drafters.

Calls for an enhancement request.


Bradley

 

[CorBlimeyLimey]

automationbabe ... why not just assign the UOM in the part/assy Custom Props (as text ... ASSY, EA, IN, mm), create a SW BOM template with a UOM column so that it "reads" directly from the model?


Making the best use of this Forum. faq559-716
How to get answers to your SW questions. faq559-1091
Helpful SW websites every user should be aware of. faq559-520

 

[automationbabe]

We could do that, but we are trying to eliminate duplicate entries for our data to avoid potential discrepencies, and to minimize the amount of work. The data is already there and works great with Excel BOM, but we'd like to use the SW BOM table. Why isn't UOM part of the SW table anyway? I have never seen a BOM without UOM.

Thanks for responses,
automationbabe

 

[CorBlimeyLimey]

I'm guessing that because it is so easy to create alternate BOM templates, SW decided that both BOM templates should be shown in their most basic form (Item, Qty, Part No, Description) and allow users to add to it to suit their specific needs.

BTW, the UOM wasn't in the Excel BOM either!

Our UOM is driven by another system

Just curious! When you create new models, how is the information being entered into the other system? If it was entered into the models properties, then wherever that part was used, the data would be accessible from it.

I realize your hands are probably tied, & that you are having to work with what you have, but, If you don't enter the required data into the custom properties of the SW model you will always be reliant on the other software.


Making the best use of this Forum. faq559-716
How to get answers to your SW questions. faq559-1091
Helpful SW websites every user should be aware of. faq559-520

 

[automationbabe]

The information is added to the Custom Properties via a third party add-in (Questica). The information remains with the model at all times. The add-in is not required to enter this information, but the information is required for export to Questica.

Thanks again for all your input.

automationbabe