Unfortunately, the revision and change control "features" in Sage 100's BOM module leave a lot to be desired. If its a common need to trace an assembled item backwards to see what rev and components were used, I would recommend creating production entries at a point within the manufacturing or packaging process so you can generate product labels off of the production entry data files. That way you can print the revision code and the trans # on your label. As long as you have production history tracking enabled in BOM, that would allow you to quickly see exactly what went into each item and what rev was used. You won't be able to restrict changes to component lines in Production Entry without some customizations (custom programming or possibly scripting). That can probably be a process-based control. While process-based means it relies on humans (who make mistakes), on the positive side there's usually only a few people who are creating the entries so it makes it pretty easy (and low cost) to implement. A couple of ideas on this... (1) you could designate a unique rev code (like ZZZ or 999) to use for every BOM where components get "customized". That would provide an instant identifier of a deviation from the current rev. To go along with that, you could create a user-defined field where they could input the rev code the build was based on, which would then provide a BOM reference point to compare against to see what was done differently on that build. (2) use KnowledgeSync or Business Alerts to run a daily process to compare the production history data to the current BOM's and alert you to any entries that have components that aren't on the rev of the BOM used on the entry. That info could also be written to a table for future reporting and lookups. You are correct regarding inactivating a BOM. The "Inactive" designation applies to all revisions of the bill. And, the Change Control functionality won't help. While SOP in mfg is to increment the revision when making a design change or component change, in Sage 100 change control just implements on a specific date changes to components within a specific rev of the bill. Basically, it's just focused on when a change is implemented without addressing the rest of the process that is critical to actually controlling changes...ECN's, reviews, approvals, logs, enforcing a change in revision code, etc. You could use a UDF and scripting to create an alternate BOM inactivation process that could apply to a specific revision and prevent that rev from being used in a production entry. I think the bad news is that the BOM module isn't going to provide the controls you (and most manufacturers) need without some customization. The good news is that there are pretty decent customization tools built into Sage 100 (or integrating with it) that can help you accomplish a lot of what you need, without having to get major custom programming done. Your reseller should be able to help you make use of those tools.
↧