"UNSET" BOM Component Revisions

We are currently set up so that new revisions of parts that have BOMs are uploaded with “unset” revisions on those parts’ components. This is so that the latest revision of each component is always used. However, when a build order is created for that part the Master part record changes from “unset” to whatever the latest version of each component is. Ideally, the Master part record would always have the “unset” revision for components. Is there a config setting that controls this?

Thanks,
Paul

Hey Paul,

Can you send me a link where you noticed this happen?

Thanks

Cetec ERP Support

this is the link to the part ASY002502-001 REV 05 in our beta site.
https://cetecerp-beta.ad.attolloengineering.com/part/2374/component_list
The BOM components were all listed as (unset) until I cut order 7743.1 (PO 8071.1).
https://cetecerp-beta.ad.attolloengineering.com/order/AE7743.1/view
Then, as you can see, all of the revisions changed to their current latest revisions.

Thanks!
Paul

Hey Paul,

Usually links work great, but I had to send in a ticket to your company’s support because I can not access your site due to some privacy settings, I am waiting on a response. If you would like to send some screenshots, I can try testing in one of our environments, I tested it once and could not recreate the issue. Did you just have a multi level bom, with unset revs on the subs, then once you made a build order (or was it stock) it set the master bom subs all to defined revs? Sorry I just want to make sure I am understanding.

Thanks!

Cetec ERP Support

Hey Paul,

I made it into your beta, did you set revs for the order specific bom when you made the quote? If so what were your steps?

Thanks

Cetec ERP Support

Hey Paul,

A coworker pointed out this really cool button to me on the quote bom worksheet:


(click this to get to the bom worksheet)

There is also a config to default that to yes so it does not update the master bom:

Thanks

Cetec ERP Support

Hi, you had it right. the (unset) revision status is set for each BOM revision using an import BOM api and leaving the rev blank. I knew there was a setting! I will work on testing this to make sure it works but this is exactly what I was looking for.

Thank you!
Paul