Sage 100

Have a client exploring converting one of their divisions who uses Epicor Vantage as their MFG system to Sage 100. In the process of doing the demo the topic of item codes and revisions came up. They all fell out of their chairs when I explained that Sage does not have revisions at the item level but only at the BOM level. They use revisions everywhere; every component on every bom and every item on every purchase order includes a revision code. Are there any add-ons out there that add a comprehensive ability to add a revision code everywhere and item code is used in the system? Does Job Ops add this ability? Appreciate any recommendations you may have.

@MarkChinsky ???

I guess it begs the question of what does a revision represent to them? Do the component items have BOMs for each revision? If there are no BOMs for the component items you might use Lot numbers as the revisions . If there is information stored with each revision, then you can add UDF's to the Lot/Serial table and the UDF's can be updated during ROG and those UDFs flow well from there out to BOM and Sales order. Another (possibly less palatable) option might be to user a different item code for each revision? Maybe use the expanded item number with the revision code as part of the item number? I don't know if Job ops has that functionality; I've not seen it in Job ops, but there are a lot of things in Job ops that I have not explored. Hopefully someone with more Job ops knowledge will chime in.

What are they looking to achieve by migrating from Epicor Vantage? Because if it is better MFG you are bringing a knife to a gun fight.

@JobOps

A plastic knife....

@DavidOverholt The revision is throughout the system, no item code is entered anywhere without the revision being identified. It is much more than a UDF, a complete change control tracking system. Duplicate items and BOMs for all items are not options. @WayneSchulz All the other divisions are have been transitioned to Sage 100, problem is they were coming from systems like Quickbooks. This was an exploratory call to find the land mines and make a decision to either stay on Vantage or migrate to Sage for system consolidation.

This may not answer exactly what you need but might help @GregStiles. I had the same issue, the customer needed item level revision tracking. We had these options - only track the current revision using a UDF on the CI_Item file (and add it to BoM details and anywhere else you need it). Create a UDT with item reivison, release date, and current revision (as y/n). Or, make the revision part of the item number (which is easier now that we have expanded item numbers). They choose option one as they'd always kept a componenet revision history in an outside system with their notes, specs, etc. Adding the one UDF for the item revision to BoM details and anytime a component revision changed, in their world, the bill revision changed too. If it was temporary we'd use engineering control in BoM.

Thanks @MoiraGoggin that may be the solution, I need to gather more info on their current system and see if it can be duplicated with UDTs and such.

JobOps would not help with this.

yup, figured that out @JohnHoyt thanks.