Re: Serial number tracking in MAPICS

All of our product must have a VIN (government mandated and format).   Also
a large number of our components (stoves, furnaces, refrigerators,
microwaves, tires, axles, etc) must have serial numbers stored - again,
government requirements.  Also, internally required as all key components
of our trailers are covered under a lifetime warranty, with various other
warranties on assorted component parts.

We used to key them in, then we put a barcoded serial number tag on the
frame of each unit.  We scan the tag and print a duplicate label for each
unit at the beginning of the ass'y line, then log all the component serial
numbers on a card that follows the unit down the line.  At the end of the
ass'y line, I put a thin client with an inexpensive CCD scanner (attached
via a keyboard wedge through the keyboard).  I have a small app that has
the buyout tech at the end of the line scan the MO#, the VIN#, and the
component part serial#s.  This does the RM transaction, and also writes out
records to a database.

The database has two basic files:  COMPMAS and COMPDTL. COMPMAS has the
VIN, the item#, the MO#, date and time RM'd.  (We also store date shipped,
customer#, retail date to provide a full follow through capability for
recalls and such in the same record).  COMPDTL has multiple records for
each VIN, one per serialized component (holds a code for the type of
component and the component serial number).

We've been doing this since 1986, when we went to MAPICS.  It never has had
adequate serial number capablilites.  I think that's on their "wish list"
for this year......

Tracking is really easy nowadays though, since we integrated the serial
number entry/logging along with the RM process.

Dale Gindlesperger
IT Manager/Special Projects Leader
Fleetwood Folding Trailers, Inc.
258 Beacon Street
Somerset, PA  15501