We are a manufacturing company. We are small (so RootStock is not a viable solution) in size, yet our business requirements are complex. We were thrilled when NS came out with Work Orders since our assembly builds are comprised of layers of sub-assemblies. Below is a snippet from a build. A typical build may have 3 sub-assemblies that in turn have 1 or 2 sub-assemblies each.
However with WOs, NS assumes that ALL of the sub-assemblies (if you check the box) are in their raw state, so even though the Build Work Order form shows the name of the sub-assembly below and a place to put a number, you can’t indicate to NS that that particular sub-assembly is already built. I've requested this enhancement from NS, but don't think it's ever going to happen since it's now been over 2 years. The problem that this creates is that if we use WOs our inventory counts are unusable since it can’t really reflect the true state of our inventory since what shows as raw materials is really partially built. (note: we use the same raw materials in several different products.)
The alternative is to do each build separately and do a Build WO not using the sub-assemblies, but this would take several iterations to build just one product. The problem is you can't mix it up (it's either all or nothing). So for now we have been using it to drill down to the sub-assembly level. The result is that it looks like we have more of the raw material components than we really have to use in other assemblies.
My goal is to have a SuiteScript that can run when we do a build that will allow me to indicate to use the sub-assembly level, rather than the raw materials. That way we could build the board levels and keep them in stock and our inventory counts would be correct.
Has anyone written a SuiteScript like this? Can this even be done with SuiteScript? We are willing to pay for this SuiteScript to be written. We can probably simplify the requirements too if this seems too complex.
Thank you.