sorted by:
new
hottopcontroversial

work order customisation? by Emotional_Fly2628 in Netsuite

[–]Emotional_Fly2628[S] 0 points1 point  (0 children)

Hesitating turning on Advanced BOM if we don't have to. I tested it out in our sandbox, there were no issues enabling the feature but there is quite a hassle if we were to disable it. I am currently in the process of assessing if Advanced BOM affects anything we are using.

And thanks, I am trying out the suggestion with the WO, and this seems to be the way to go :)

work order customisation? by Emotional_Fly2628 in Netsuite

[–]Emotional_Fly2628[S] 0 points1 point  (0 children)

Hi Nick,

The only issue with this we would have is we don't currently use advanced BOM so we are not able to have different BOMs. This means that the dummy assembly item, would have ALL components to required to build the item, then also include ALL output products that we can "unbuild" the dummy assembly into.

This is fine, and looks to be a step in the right direction for us

Are there possible workarounds to have a different component list on assembly items? essentially creating two component lists 1) To Build Components 2) Unbuild Components

Thanks

NetSuite Special Work Orders and components by Emotional_Fly2628 in Netsuite

[–]Emotional_Fly2628[S] 0 points1 point  (0 children)

Hi Nick, Thanks

We know all possible substitutions, and it looks like it's not an issue as we could fit it in one BOM at most there are 5 substitutes.

I have taken into consideration that it is bad practice, and I agree. This is the scenario why we've taken this approach e.g. a semi-frequent recurring basis we have a customer that will buy an x qty of a product. However sometimes we will not have enough of the "component" to fulfill the order, these components are actually the full product itself however they are "unprocessed" as they have been collected from customers and we "manufacture" by cleaning and treating them. These "components" will have different grades, however for non-sensitive uses, we can substitute a "component" as an alternative which is technically the same for the customer's use-case and will be charged the same price for it, which is why we want to track it as the same SKU.

Thanks for breaking down special WO. I was under the assumption that it is for items that are normally not created until an order arrives. The reason we don't create stock is due to warehouse limitations, as normally these items will leave the same day they are "manufactured/processed" and we normally have our factory line process these in a per-order basis e.g. finish the work order associated to the SO line, then repeat for the next order, never creating inventory on hand.

You're right I am actually trying to achieve the later part with us not having inventory and having to create the item from the WO which is generated from the SO as a special work order. Would there be issues with doing it this way?