Sage 100

Client is possibly interested in serializing their products in MAS 200. However, they'd prefer not to do the full serial integration (i.e., setting items as Serial valuation). So I made the suggestion that we could probably create one or more UDF's to give them the functionality they need but I'm wondering if anyone has done anything much different than this to satisfy the client's need (e.g., 3rd party program).

To be honest I do not think that is possible. Serialized items are a strictly one to one relationship with cost, price, etc. If you receive in 10 items you would have 10 serial numbers. In all cases if you use say FIFO, you would have ONE (1) FIFO costing tier for the 10 items so how would you record the 10 different serial numbers?

Right now they're doing it manually outside of the system, so anything would likely be better. They're not concerned about checks and balances and making sure things flow and tie together properly, otherwise they'd probably just set their items as Serial valuation. For the most part they just want to be able to specify a serial # on certain transactions just like would be done with any 'ol UDF data - that can be queried and reported on after-the-fact.

Are they using a bar code solution?

No, @JeffSchwenk.

It seems like you could add a UDF to the link and flow it through. The issue is most likely going to be whether the customer expands on their need for that serial number beyond what they initially believed and toward what a true serial valuation would bring

If they are already okay with keying the serial number into a UDF, what is so much more about keying it into the standard field?

The real issues will ensue when that one person keeps forgetting to enter a serial number or types 1234 because they can't find the right one.

Do they have a bar code to scan?

@DawnAnastasi, they want the Serial # field to be optional because they don't want/need to have to specify it all the time. @JeffSchwenk, I don't believe they're currently doing anything with bar codes.

It sounds like they aren't really interested in serialization or tracking individual item costs, they just want a SO and Invoice line UDF that flows through to SO and Invoice history and is large enough to hold multiple serial numbers..

Sounds like they just want to be lazy and do the task at times when they feel like it and other times take the short cut. Hard to believe they aren't wasting boatloads of time searching for the information. Too bad you can't add some value to their organizaton by streamlining the process so that serial numbers are used ALL the time, bar code labels are printed and attached to ALL the items and that at critical data gathering workstations, they have bar code scanners for data entry. This would save them tons of time and ultimately TONS of money!!!!!!! I think BL's former organization did a lot with bar codes. Perhaps he will add his .02 worth.

Will be meeting with the client Tue so I'll know more then.

Updated info: So the client appears to want the standard Serial # functionality (i.e., having the serial # auto-increment based on the last one used, prevent from using an invalid or already-used serial #, and allow for overriding the ""next"" serial # if for example they want to skip a range of numbers) however, they ideally want the serial # field to be optional. But the other snag is that they'd like to be able to specify the serial # data during W/O Entry (similar to how you can now do that during S/O Entry). This is because they create certain work orders for work that outside vendors will perform, and they need to tell the vendor what serial #'s to assign to the manufactured product. Outside of just manually keeping track of the serial #'s they tell the vendor to use, via an Excel file or BOM/Item Memo's in MAS, is there a way to do this?