Sage 100

Serialized Kit? Workaround? (figured I'd start a new thread; cont'd from https://90minds-com.socialcast.com/messages/17283738?ref=stream) I have a client using B/M and W/O. They have Serial valuation BOM's (currently set as Standard type bills) which consist of multiple Serial valuation subassemblies. They want to have the S/O Packing List print the upper-level BOM with serial # (which it is doing) but they also want the other Serial subassemblies to print as well, with the serial #'s. At first it sounded like we just needed to change those upper-level BOM's to Kit type bills, but doing that prevents us from using Serial valuation. Is there a workaround for this? Also, how do I determine where a serialized subassembly went? I can see it coming into inventory, as well as being issued to W/O but I'm having trouble seeing any other specifics (e.g., where it went, i.e., which W/O serial completion it was used on). Similar to the upper-level BOM that was sold to the customer, I need to be able to have traceability of the serialized subassemblies. Also looking to have the W/O Pick Sheet print the allocated subassembly serial #'s, but not sure if that's possible.

This is a good one Brett. Unless @BethBowers or @DebThomas know something that I do not, it is very difficult to track serial numbers through WO. Beth? Deb?

ACS has an enhancement called Vendor Lot Traceability. It tracks vendor lot codes from receipt through manufacturing to the finished good. I'm not sure if it works for serialized inventory but it may be worth a look.

Have you looked at the IM_LotSerialTransactionHistory file? Do you have the primary vendor on the items assigned? , (i.e., ABC Dist makes ABC Dist sub, component from XYZ vendor)? You can tie back s/n through the vendor using this file and filter on in house vs. outside vendor serial numbers.

WOEP (from ACS) at least gives you the WO number in the IM_TransactionHIstory file. BTW - ACS has changed their pricing for WOEP, so make sure you get the new pricing before quoting it. (As of Sage 100 2013)

Thanks for the feedback. This is apparently a known shortcoming of Sage 100 - that there's no traceability of BOM component serial #'s. So we're switching to Kit type Bills because the client is actually more interested in the components' serial # traceability - plus that gives us the ability to easily have the components and their serial #'s print on the pack list and invoice.