|
This is different from standard inventory control where we can have a large quantity of same item, and all we track is how many we have. In the manufacturing software (usually called ERP) the normal way to track individual items is through lot or container control. In this case, your lot consists of one item, and the lot # is the serial #. With lot control, every time you move one item, it has to be identified by its serial #. If you only want to do this on these other manufacturer items, and not on your regular stuff, this is doable. Most ERP will let you pick and choose which categories of items are subject to lot control.
If the serial # needs to be assigned by your outfit, then standard application design can have a field in a control file some place that has the last one assigned, or the next one, then every time software needs to identify another of those units, it increments the control field place by one. Your application design has to avoid the Y2K syndrome of running out of numbers.
Typical application design let's us reuse the same item #s, order#s, RMA#s, lot#s etc. after their usefulness to us for one purpose has ended, but serial#s need to climb forever. You may wish to look into managing non-numeric components of the serial # accumulation logic so the size of the field not grow so fast.
Then there is the archive responsibility. Do you need to keep a record in your computer system for perpetuity on where each serial # went? Does it matter if the returned serial # whatever comes back to you from a customer other than the one you sent it to? Which is a problem I had at a former employer partly because, where the data met the people, they were not religiously keying in the right stuff.
The issue is that we would be selling a different manufacturer's product, as a bonus to ours. In our warehouse, we have to seal this product to ours. but keep their serial number visible and a record of it, even tho it will not appear in any of our edi.We need to keep track of this serial number in case of recall. "Kruse, Kat" <kkruse@xxxxxxxxxxxx> wrote: Need to know a little more about your application in order to make suggestions. Kat Kruse IT Engineer Qualcomm, Inc. kkruse@xxxxxxxxxxxx (858) 845-0014 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Berman Sent: Thursday, June 08, 2006 14:50 To: midrange-l@xxxxxxxxxxxx Subject: serial # we market a sat. radio. xfm said we should offer a free antena,as promo.this has serial#.how to get this #to our iseries? we must keep trk cuz of fcc. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
