Sage 100

Hey all your manufacturing Guru's out there, I have a question about the 'Current Revision' field in Bill of Materials Maintenance. I understand this to indicate which revision of a Bill is the current, default revision to be used in other BOM's. If a manufactured item is used as a component in the BOM for another manufactured item, you either reference a specific revision or enter an * to use the 'Current Revision' of that item. The Current Revision is defined in each BOM/Revision record in the BM_BillHeader file. Based upon this, if I have 4 different revisions of a bill, I assume that they should all point to the same revision as the current revision. Otherwise, how does a parent BOM know which to use when referencing 'Current'? (I guess it uses the current from the first record it finds for that item) Sage 100 does not prevent referencing multiple revisions as current for a particular BOM. I have a client with over 750 instances of multiple revisions referenced as the 'Current Revision'. I have some that reference as many as 4 different revisions as 'Current'. While the system may not prevent this, am I confused in that this should be avoided where possible?

Correction, I modified my query in Access and reduced the number of instances to 11. The issue is now about what I expected. However, still have the question, is my understanding correct? Shouldn't all records point to the same revision as current?

I'm not sure how this is happening. When you create a new bill, the current revision defaults to 000. If you create a second revision, say 001, it keeps the current revision at 000. If you try and change it to the new revision, it says, ""Do you want to update all revisions of this bill with the current revision?"" If you say yes, then all revisions of that bill will now reflect 001 as the current revision. If you say no, it goes back to the original or 000. Have they imported bills?

@ThereseLogeais thanks for the response. My concern was greatly reduced when I found the error in my query and the occurrences dropped from 700+ to 11. I don't know how the instances are occurring as my understanding of functionality are the same. The system should prevent these from happening. I have provided a list of BOM's with conflicts to the customer as well as BOM's with recursive item references (they had four of these where an item that is a child of a parent BOM uses it's parent BOM as a component.) Regardless, you have confirmed my understanding and we are moving forward. Thank you so much for your confirmation.

Did you run the bill validation report to uncover any other discrepancies?

Not yet. Found the above issues trying to pull data from BOM and inventory through Access. I will run the validation report to confirm.