How does revision control work in netsuite?
We are working on implementing NetSuite, so we are still learning our way around. Our business has no physical manufacturing, all of the fab work is subbed out. We do the designing/engineering of many of our products though. When we update a product, we want to be able to control the revision in NetSuite to match what’s on the engineering print. What’s the best practice in NetSuite to handle this? An example would be we changed a hole size, or added a hole. So nothing would change BOM wise, we just want to have some idea when something changed on an inventory item. Is this something that exists already? Or would we have to make something custom for that? The only thing that I’ve been able to find so far on revisions is in the advanced BOM module, but these items wouldn’t have a BOM to speak of, so I don’t think that’s the right place to be looking. We don’t really want control as tight as actual LOT tracking, but something that gives us a general idea.
thanks in advance.
The most official way to do this is using Advanced BOMs. You could use the BOM and the revision of it but the BOM might only have a single item in it.
Depending on the type of reporting you want to do… you could create your own methodology of this creating a new item for each revision, with its own name, but assigning each of the revisions the same parent item. Then you can report on all of them with the use of the parent items.
So do most people just make most of their items assembly items, then allow purchase of it if you are usually buying it? This whole item type is messing with my head. I don’t like the idea of not being able to go from a “built” (assembly) item to a plain on inventory item as needed. Probably just something I need to get used to.
You can set an assembly to be able to be built or purchased, yes.
You could manage revision of a standard item with a naming convention or a custom field. You could also create a new item for each revision and group them with a parent item. Like with so many things in NS, there are several ways to do it, you just have to choose which is best for you. Unfortunately, for your given case, there might not be a perfect solution.
Yeah, making new items for revisions will be difficult since we will have connectors in place for web sales, so I don’t want to mess any of that up.
You can also use effective/obsolete dates on the components. That method bypasses the need for Advanced BOMs.
You could manage the revision with a single component but add the drawing as a file in the related records of the revision to show the changes using the anming convention to make it easy to identify