I think I might be losing my mind….I have a scenario where an assembly includes an other charge for resale item with item source of Purchase Order because we send a part out to get machined (I know I know I should be using outsourced manufacturing but whatever). Then I create a WO which auto-generates a PO to the vendor (set as preferred on the item. I receive the PO and build the assembly, but the GL impact of the assembly build doesn’t use the price I set for the item on the PO, it ONLY uses the Purchase Price as set on the ITEM. If Purchase Price is blank, then there’s NO GL impact from the other charge item. This can’t possibly be standard behaviour…am I missing something? Some checkbox in accounting preferences called ‘make Assembly Builds work logically’? Why would it take the price from the item over the price from a PO that’s LINKED TO THE WORK ORDER?

I have experienced this as well. The same goes for special work orders. It would be nice to have the exact cost of a special work order translate to the GL impact of the item fulfillment or invoice but it doesn’t. It still issues the average cost (or standard or whatever the costing method is)

sweet mercy….did you ask NS? Defect? Enhancement? or did they just tell you ‘this is working correctly, thanks for your feedback’?

Yes they said this is “standard behavior”. However I do get different answers when I ask NS support the same question multiple times so maybe if you try again it will be different. Lol

wow